My initial impression was that it would be very difficult to comprehend and distinguish such a breadth of icons if they are all the same shape and color scheme, and differ only in the interior graphics which are pretty tiny in all cases.
So +1 to a limited number of categories to help classify different basic types, and representing them in different colors and/or shapes. Also, for the complexity of these icons, why are we trying to squeeze them into such a tiny space? Can you really tell at a glance what each of these steps and the whole sequence are trying to accomplish? There are some other very cool ways we could push this to the next level, for instance place the icons on a isometric 3d (ala sim-city) type grid, or have the flows represented by arcs instead of simple linear arrows, or adding steps causes an animated restructuring of the flow similar to what you see in https://code.google.com/p/gource/, or having icons grow as you hover over them like the mac launcher bar… -Jonathan *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Srinath Perera *Sent:* Monday, August 05, 2013 3:37 AM *To:* architecture *Subject:* Re: [Architecture] Developer-Studio Icons I prefer Concept 4, basically to draw the idea in EIP icon style (simple lines, but too detail picture). Kasun, Chanaka and myself was chatting. I think we need to group icons by type (e.g. filters, conditions, transform, do external call ). We can use the same grouping we have in palettes, and then all icons have same look and feel. Some thoughts on concepts Log, BAM - stethoscope Aggregation, Clone, Iterate - EIP aggregator Icon, EIP splitter Icon, EIP splitter Icon, Event - EIP pub/sub icon Drop, router - EIP routing diagram Filter - funnel Header, Property OAuth, Entitlement XSLT, PayloadFactory, Smook Class, Command - "{java}" Call, Callout - EIP request, replay Icon router - EIP Icon
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
