Loading Profile...
User defined layers
Give layer support, so you can mock-up a full screen and then show expanded combo boxes, markup, expanded menus, alternate views, etc. on these user defined layers.
I’m excited
7
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
-
Inappropriate?This is a great idea. I know Peldi wants to keep Mockups simple as a design goal, I agree that should be the first and highest priority.
I believe this could be implemented in a very simple way. On the Properties panel, have a Layer number control. By default it is always 1, but if needed a user can change it. In full screen mode, simple arrow up and down would allow you to move between layers. On export, a simple addition of what layer to export could be added, exporting a single simply exports whatever is visible at the moment.1 Comment
Add a comment
This is one of the best points
-
You make two good points that I didn't originally highlight:
1. This would help for taking the mock ups to presentation.
2. This should be a simple feature without complexity. -
Inappropriate?Phew guys...this is advanced stuff! Sounds like a v.3 kind of feature to me...
I’m going to think about it
1 Comment Add a comment
This is one of the best points
-
Hopefully it can be a simple feature that is really powerful! v.3 huh? Hopefully that is not ages away :-)
-
Inappropriate?You did linking, you can do anything!!!
-
Inappropriate?I really want this!!
1 person thinks
this is one of the best points
-
Inappropriate?Agreed that this would be super helpful in terms of showing multiple states of the same basic screen. In today's version, you have to do a lot of work to duplicate the screen and then make lots of small adjustments to show the states. If you then need to make adjustments to any of the those states, you have to go back to edit all of the files that make up the interaction you are trying to depict. Layers would really help to simplify this problem. -
Inappropriate?C'mon Peldi...your loyal fans are speaking!!
Surely you can add it to the scribble on the roadmap!!
Kidding aside, this really would be fantastic, especially in A-B type situations. -
Inappropriate?I think, this could be solved with "references to other mockups"
http://www.getsatisfaction.com/balsam...
So, instead of layers, one has different files. On file for the basic stuff, one file for expanded UI elements, and one file for the markup. Each file references the previous.
One can edit them independently, save the mockup and it is updated automatically in the linked document. And we could make snapshots without markups to use in documentation (some other feature request http://www.getsatisfaction.com/balsam...).
Looks like this reference would solve some of the requests :-)
1 person thinks
this is one of the best points
-
Inappropriate?Different views/states/versions and layers should be treated differently I feel as they are not the same thing.
When it comes to layers all I really need is 2 layers, background and foreground as I often find that I have several controls that just mock the basic UI interface that every page has.
This background I then group and lock to move it out the way, which is fine until I want to resize, then I have to move all the content out the way, unlock it, un-group, change the size, group, send to back, lock then move the content back.
I would rather be able to work on a foreground layer, at which point the background acts like its locked (and always displays behind the foreground). When I switch to the background the foreground acts like it is locked.5 Comments Add a comment
This is one of the best points
-
Chris, as Andi mentioned earlier, what you're asking for could probably be better achieved through the implementation of "included" mockups - that is, allowing the user to create one mockup and then reference it from within another mockup where it becomes a read-only view. Then, whenever you update the first mockup the changes automatically propogate to the second mockup.
-
Except if you need the background at different sizes etc, ie its not a common shared background.
-
Ah, but if the ability to import a mockup also let you resize the imported view then it would! This would be very similar to Photoshop's "Smart Object" functionality (http://www.creativepro.com/article/ph...).
-
Now that would make it useful, so long as I can define how elements are anchored and which ones scale.
-
Ah, and now we're asking for very complex behaviour. You can achieve something like what you're requesting in Visio - so long as you're a wizard with Visual Basic for Applications. Otherwise, everything tends to scale equally and I can see how that wouldn't necessarily work in many cases.
EMPLOYEE
