This conversation was archived and is no longer visible to community members. The community moderator provided the following reason for archiving: implemented with Symbols: http://support.balsamiq.com/customer/portal/articles/110439
I would love to see a feature to "Insert a Mockup" - an external mockup as a reference. Changes to the original mockup would be reflected in any mockups that use it.
I realize this is a complicated feature with many implications such as an ability to orphan the inserted mockup; handle cases where the mockup is missing or renamed; not allowing circular references, etc. This feature would be made possible by a storyboard mode or project manager feature.
Still I wonder what others think of this idea? I
1.create the master mockup
2.export the png
3.import the png as an image for other mockups, place it at the back and maybe even lock it
4.if you want to update the master, just update its bmml file and export the image again with the same name...the change will be reflected everywhere since images are linked and not embedded.
I'm not saying this is a great solution, but it might save you time until we come up with something better.
If this is not the right place to discuss this, do let me know :)
'Insert mockup view' to browse and select an existing mockup which grabs a bitmapdata of the selected mockup and inserts it onto the page.
Then you monitor the source mockup file (either datemodified if that's avialable or file size) and if that ever changes simply grab another bitmapdata. That way you don't need to worry about deleted files or dependencies etc.
Still not the easiest thing in the world to do but thought I'd add another vote for it and another idea :)
Currently, I manually cut and paste to keep the core common aspects of the page in synch as it goes through design variations.
It would be more efficient to have the ability to designate a "parent" mockup(s) as a base layer. For example, the parent mockup might contain the outer frame, some standard buttons, etc.
* Changes to the parent propagate to the children
* Edit a parent within a child? My gut says to just allow it, and have it auto-update the parent mockup. (The alternative would be small workflow to require acknowledging you want to edit parent, if not, do you want to merge parent into child and edit? Meh! I think this makes it too complicated to start.)
Implementation might be as simple as considering the inclusion of a parent bmml file (amost like an include).
This reply was created from a merged topic originally titled
I was thinking about something along those lines:
- Add a new element you can paste into any mockup, which is called "component"
- This component may contain any bmml-code, but is not directly editable.
- So if you want to change this component, you select it somehow, you are sent to the code of this element as a separate mockup, where you can change everything.
I guess, this way you can build in a very modular way, without affecting the general workflow of the application too much.
any sort of ETA on this? I've just done an excercise on a huge project and things started to get wildly out of control as I had so many similar views that all ended up slightly different which has led to a lot of confusion.
Other than that tho mockups has been an absolutely amazing tool for us on a number of projects now.
Can't wait for this to be implemented!
This is obviously somewhat lazy on my part and now you've prompted me and i've experienced the pain of not doing it I'll be more strict on this.
But I guess the rest of Mockups just lets me be lazy and just get on with it! ;)
in the top, you have categories like "All", "Big", "Buttons" etc. The last one could be "My Components", where you have your components.
By default it is empty, but when you are working on any mockup, you could "Save As Component", and it then shows up in that category. And then you can just drag things from My Components onto canvas as you normally would, but can't edit them. If you want to edit, you have to open the component by super-triple-doubleclicking or doing some other special action on it, and then you edit it on the canvas.
On the disk, all the components are just normal bmml files in some special location (App Support etc on Mac).
If the linked mockup is missing, don't ask, just show the last inserted. No change of size, no links from the original mockup. Keep it plain and simple and we might get this feature.
- In Progress