- What do you want to see in Hype?
I’d love to see Hype have components. After my experience writing extensions so far I’d like to be able to bundle stuff into a container… I’d consider that a component. Basically this would be a new type of symbol in the resource library. It would be much like an app on Mac OS meaning a “folder” in disguise. This wouldn’t mean actually revamping the resource panel by introducing some folder structure … rather it would be like a regular symbol with benefits.
For example double clicking it shows a filtered resource panel with the resources and functions that are associated with it. These in turn don’t show up in the regular resource panel view making that view cleaner and only project specific. There are some edge cases to consider like duplicating a component much like a symbol… that’s why I consider resources associated with a component. double clicking the duplicated component would reveal the same resources! Meaning there is probably some component identifier that can be set and is inherited by the associated resources. In the UI this could be set on the lower end of the resource panel and additionally be automatically set to the component on currently is inside (like view package contents on Mac OS).
Installing components would be like dropping a symbol on stage and updating it would be like copy and pasting it from another document or loading it from a new file format called XYZ.hypeComponent. Imports would also overwrites the associated resources and remove the old ones.
Components could be UI elements or any other type of helper that get’s active when it’s dragged to the scene. The settings for the component could be made through dataset and wouldn’t be reseted when updating the component. The settings would be considered something exterior as they are attached from the “outside” when users is using the component.
For document level components/extensions they are currently hooked up to “document load” and “prepare for display” and mainly only a function. This could be another kind of component hiding the associated functions inside but as this isn’t a full analogy to the symbol based approach described above that part is still food for though.
- Have you found a workaround for this problem?
Yes and I find designers are intimidated if they se the inner complexity of current extensions. Meaning if this is hidden like the runtime itself it would become more like a tool.
- Are there examples of other apps with this feature? Or, have you seen examples of this elsewhere on the web? (Please include a URL)
As mentioned Mac OS with it’s app packages as an analogy.
- How high of a priority is this for you?
[ ] Nice to Have
[ ] Can’t use Hype without it