Reusable, Editable, Referenced Controls

smcady shared this idea 6 years ago
Under Consideration

I may be just missing this, but there does not appear to be a way to define a "composite control" for lack of a better term, that is "referenced". Widgets get you part of the way there, with a couple of important exceptions:


1. If you use a widget in your project, and then update the widget, it doesn't cause the instances of the widget to be updated. For example, if I want to use the same date control on multiple screens, I can simply define the date control once and save it as a widget and then reuse it across as many screens as I need to - excellent. Unfortunately, if we decide at some point that we want to change the base definition of the date control, I cant just update the widget and have the app automatically update all instances of the widget for me - not excellent.


2. Widgets show up in the hierarchy (in outline view) of elements on a given screen with all of their internal complexity exposed, making a screen's hierarchy navigation unnecessarily complex and slow - a widget should be defined with a single row in the screen's hierarchy, perhaps with an option to jump to an edit screen to modify the widget instead of duplicating all of the potential complexity that a single widget might encapsulate across all of the screens in a prototype.


Are there any plans to modify the app to work in this way? I feel like this is a major roadblock to using this tool for large requirements projects across multiple applications / company divisions / etc.


Thanks,


Shawn

Comments (3)

photo
1

You can try using masters http://www.justinmind.com/tutorials/m...

photo
1

Um, ok, now I feel like an idiot. Guess I should RTFM before I assume I know how to use the tool!


Excellent - thanks!


Shawn

photo
1

Haha don't worry! Come on, let's be honest, nobody reads manuals these days.