Screen mock-ups ideas/suggestions/questions

[slavko]

We are using EA to do screen mock-ups and use the Custom Toolkit with mostly the UI Control and Screen elements.  I’m interested in other people’s usage of this.  Below I’ve listed some aspects of how we use it.  Some items are things that we find difficult to achieve.

1)UI Control can be sub elements of the Screen but not of other UI Control.  This makes a bit of a mess in the project view when for example I show a grid control with columns.  I’d like the columns to be in the grid control.  I guess I can make the grid a Screen and alter the screen image to look more like a grid.
2)Labels?  We have been putting a UI Control as an text field and just calling the control what we want the label to say.  Is there anyway to do labels better.  Also we would want the label to appear either to the left of the field or above it.  Is this 2 UI Controls or 1?
3)Screen decomposition.  We are trying to figure the best way to show complex screens/tabs/large grids via decomposition.  We are using a combination of aggregate relationship, the composite element, and diagram reference via drag and drop.  How are others doing this?
4)How are people denoting required fields, read only fields? Our choice is to show this visually (different color of element) or tags.  
5)We don’t like to print the UI elements due to the mess it creates so we print with don’t print note-less elements.  This is why we would not like to use tags.
6)Do Tagged elements print even if there is no value?
7)We have been asked by the user community to make the screen look as read as possible, we are planning on using the stereotype with alt image.  What are your experiences with this?
8)We are also going to be taking use of Profiles for the UI elements so that people don’t have to stereotype and provide tag values or color.  Any experience with this and profiles?
9)It would also be nice to drag and drop domain object attributes onto a diagram stereotyped as <screen>> or something like that.  The dropped element would be a UI control with some embedded tags like class.attribute designation.  Currently a dragged attribute produces an object element.

Thanks for your thoughts
-Slavko

[David]

Slavko

Did you ever get answers to these questions.

(Since this is an old post) Do you have any additional info/comments on how to overcome these issues.

TIA

David