Tonny Kohar wrote:
Regarding envisage, I think boxed/stacked graph support is finished. So what's is left are (the trivial part) - do I remove the mind map graph or just leave it as it is
I actually prefer the mind map, so keep it.
- do I need to put the boxed/stack graph into pdf print as well ? How about the mind map printing (do I remove it or keep it) ?
Good question. I'm not sure which one is best for printing actually. The mindmap has some advantages (such as not requiring a pancake mentality). It would perhaps be best to have an options dialog for export, where you can select which one you want.
- color scheme, if you have better/any graphics person could come up with better color scheme ?
Thien? :-)
And something a bit more complex, regarding the selection item synchronization. For the moment, if you click on the item on the stacked graph is synchronized with the rest (mind map graph and detail tab pane). However the opposite is not. So any item selection from either Detailed/Tree (Swing) or mind map does not update the Boxed/stacked graph because the stacked graph by behaviour is a bit different. Because, the stacked graph can be viewed as collaped or expanded (zoom in or zoom out) So when the user select an item eg: PersonEntity using Swing Tree and the current zoom level of stacked graph is top level (the PersonEntitiy is in collapsed state) what behaviour you expected ? Do you want the stacked to auto expand ? or something else
Autoexpand and select seems reasonable, yes.
When anyone have time please take a look at envisage, and what is your suggestion ?
Currently pretty much nothing happens when you select a layer or module. It would be good if a module selection showed some relevant information about the module, such as API and SPI.
API would be defined as "All service interfaces which are visible for layer or application" and SPI would be defined as "All service dependencies which are not satisfied from within the module". And then similar for Layer. This way you can select a Module/Layer and immediately see what it produces as output and requires as input. This is also very very nice for documentation purposes.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
