Masters need override capability

Jason Fults shared this question 6 years ago
Answered

We are looking for a tool to use across a large organization. Because of this, masters will be very important (and widgets almost useless). We need the ability to push a new master to a project and across projects, but we also should be able to change styling at the instance level, or even to override master dimensions. For example, I may have a master that is 120x80 pixels and colored blue. I might want to make 5 copies, color 3 of them pink and stretch 2 of them in one direction. Changing the master color should update all blue instances, and changing the master size should update all of the non-stretched instances. Going to the instance I should be able to remove the overrides easily. Balsamiq does this, but lacks any animation, so we are still looking for a solution.


Thx,


Jason

Comments (7)

photo
1

A couple additional problems related to this.


1) organization - we are probably looking at hundreds of masters, and need the ability to catagorize, manage and find them. Any thoughts?


2) color highlighting - I don't want to have to guess what color something really is. This makes using masters problematic. Can we disable highlighting?


2a) It is valuable to see what on the screen is tied to a master. Can another model be used?

photo
1

We hope next year we'll include an option in Prototyper to define something like 'css styles'. That would solve the thing about Masters.

photo
1

1) I'm afraid there is no way to organize Masters now. But it's a great suggestion.


2) Not now, but already, another great suggestion


2a) I'm sorry but I don't get it.

photo
1

Thanks for your reply Victor. 2 & 2a mean I want to have my cake (realistic representation of colors) and eat it too (easily see what is tied to a master). The requirement would be to remove master highlighting and replace it with a new mechanism.

photo
1

Thanks again. CSS3 support will be very important to us.

photo
1

Another request for this feature!


Styling 'instances' of widgets or buttons is one of the first things I looked for when trying the demo.


A CSS style of defining classes for a variety of buttons or text fields would be amazing for high-fidelity prototypes.

photo
1

We plan to have that option implemented the 1st Quarter of 2013