I'm +1 for using text below icons, because these are not like standard
icons that people are used to. Maybe you can let the user toggle the text
on/off using a shortcut key. Also, because the size of these icons are
small, they should not have any complex designs. You can have a look at
Entypo[1] or Fontawesome[2] icon fonts for some inspiration.

Regarding the color scheme, I think it'd be better if you can follow a
pastel-like color scheme. Diagrams would look easy on the eye when there
are so many different kinds of elements in them. For this you can try
Kuler[3] to find one of your choice.

[1] http://www.entypo.com/
[2] http://fortawesome.github.com/Font-Awesome/
[3] https://kuler.adobe.com/pastel-art-colors/



On Mon, Aug 5, 2013 at 2:33 PM, Chanaka Jayasena <[email protected]> wrote:

> We had an internal discussion about the icons and designs. Plan is to get
> the line art representation of the 1st and 4th concepts and draw the icons,
> rather than using complex artwork. The icons will be grouped according to
> what is used in ESB web console. These grouped icons will be differentiated
> by the shape of the icon container, and the color of the icon.The text in
> the icons will be kept since the repeating text below the icons should be
> the description that the user is adding. Unfortunately my previous images
> does not represent that idea. I am in the process of creating a  new screen
> to visualize the proposed concept.
>
> thanks,
> Chanaka
>
>
> On Mon, Aug 5, 2013 at 10:21 AM, Samisa Abeysinghe <[email protected]>wrote:
>
>> So different colors is a good point as far as picking the difference
>> goes. But they got to be noticeably different.
>>
>> The good thing about concept one is the clear imaging in there. So we
>> need a combination of concept one and three where we could have clear
>> imaging and clear color based differentiation to help pick the right one to
>> match the need from the bunch of options available, while you are at the
>> task of developing.
>>
>>
>> On Mon, Aug 5, 2013 at 9:43 AM, Kasun Indrasiri <[email protected]> wrote:
>>
>>> - We thought of including the text along with the icon, because all
>>> mediators cannot be represented with just an icon. EIPs can be used for few
>>> mediators, but not all mediators cannot be represented with EIP icons. And
>>> the text below the icon can be anything (such as a comment) that user wants
>>> to add (which will be saved as the sequence/mediation description in the
>>> config).
>>> - I prefer the icon shape as with concept-3 with a different color
>>> scheme (and with out fancy colored icons inside)
>>>
>>>
>>>
>>> On Mon, Aug 5, 2013 at 5:34 AM, Chanaka Jayasena <[email protected]>wrote:
>>>
>>>> Designing meaningful Icons for "Fault mediator" , "Aggregate Mediator"
>>>> can be easy enough, but for complex synarios it will be hard to represent
>>>> the idea and grasp the idea from the icon as well. From the users
>>>> perspective when user tries to read a flow of elements, it will be easy for
>>>> the user if there is a word attached to it where he can read it on the spot
>>>> rather than try to find it by going through a documentation. I personally
>>>> like the first one but the third one is more color contrasting, which adds
>>>> one more plus point for the users to bind memories to associated color
>>>> patterns of icons. One minus point in the third one I see is that, the text
>>>> representation is bit inconsistent compared to the first one.
>>>>
>>>> thanks,
>>>> Chanaka
>>>>
>>>> On Sat, Aug 3, 2013 at 8:54 PM, Isuru Perera <[email protected]> wrote:
>>>>
>>>>>
>>>>> On Sat, Aug 3, 2013 at 8:31 PM, Sanjiva Weerawarana 
>>>>> <[email protected]>wrote:
>>>>>
>>>>>> Personally I don't like them .. they're going to be too complicated
>>>>>> at the 50x50 type size they're in reality. Second, the words in the icons
>>>>>> don't make sense IMO.
>>>>>
>>>>> Yes.
>>>>> I think the words are not needed on icons. We just have to make sure
>>>>> the icon is meaningful.
>>>>>
>>>>>> Third the colors seem too strong? Of course I'm color blind so my
>>>>>> color choices are not one to bet on.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Isuru Perera
>>>>>
>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>> Twitter: http://twitter.com/chrishantha | LinkedIn:
>>>>> http://lk.linkedin.com/in/chrishantha/
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> [email protected]
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Chanaka Jayasena
>>>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>>>> email: [email protected]; cell: +94 77 785 5565
>>>> blog: http://chanaka3d.blogspot.com
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Chanaka Jayasena
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> email: [email protected]; cell: +94 77 785 5565
> blog: http://chanaka3d.blogspot.com
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Best regards,
*
*
*Praveena Sarathchandra,*

Software Engineer,
WSO2, Inc.
lean . enterprise . middleware

praveena.me | +94718732203
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to