| Line 1 was replaced by lines 1-3 |
| - This is the place to discuss kepler symbology during the re-design process. I've laid the foundation for reducing the number of vastly different symbols into a more unified, easier to remember and easier to recognize set. However, this is a minimal set and will need to be expanded but the goal is still to keep to a small set of simple symbols that use the proposed (limited) color set. |
| + This document is intended for __Kepler designers and developers__. It is part of a proposed re-design and does not reflect visual design and functionality as it currently exists in Kepler. Comments and feedback are appreciated. |
| + ---- |
| + This is the place to discuss kepler symbology. I've laid the foundation for reducing the number of vastly different symbols into a more unified, easier to remember and easier to recognize set. However, this is a minimal set and will need to be expanded, but the goal is still to keep to a small set of simple symbols that use the proposed (limited) color set. |
| Line 3 was replaced by line 5 |
| - Please see the recent [proposed Kepler redesign|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler/docs/dev/usability/Proposed Kepler Re-Design.ppt]. |
| + Please see the recent [proposed Kepler redesign|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler-docs/dev/usability/Proposed Kepler Re-Design.ppt]. |
| Lines 5-9 were replaced by line 7 |
| - For background information on usability in general and Kepler usability reports see: |
| - *[General Usability Presentation at KU/November 2004|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler/docs/dev/usability/All-Hands-KU-11-2004-usability-intro.ppt] |
| - *[Presentation on Initial Kepler Usability Issues (mostly visual issues) at KU/November 2004|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler/docs/dev/usability/All-Hands-KU-11-2004-usability-discussion.ppt] |
| - *[December 2004 Kepler Usability Report|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler/docs/dev/usability/Dec2004-usability-report.doc]- report on Kepler usability issues from user feedback and group testing of basic operations during BEAM/ENM workshop |
| - *[January 2005 Kepler Usability Report|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler/docs/dev/usability/Jan2005-usability-report.doc] - report on Kepler usability issues from user feedback and group testintg of basic operations during SEEK Ecoinformatics workshop |
| + For background information on usability in general and Kepler usability, see [Kepler Usability|http://kepler-project.org/Wiki.jsp?page=KeplerUsability] |
| Line 12 was replaced by line 10 |
| - The usability objectives regarding symbology as listed in the proposed re-design are: |
| + The design rationale regarding symbology as listed in the proposed re-design are: |
| Line 24 was replaced by line 22 |
| - *consider defining small set of atomic actors that go across ontologies and small set of icons for ecology domain -- LLD> issue here would still be that some kind of functions might be represented differently across ontologies |
| + *consider defining small set of atomic actors that go across ontologies and small set of icons for ecology domain -- LLD> issue here would still be that same kind of functions might be represented differently across ontologies |
| At line 26 added 2 lines. |
| + *web service (gear) seems to be based on "plumbing" rather than function so this was somewhat confusing. Gear will be reserved to possibly represent specifically some kind of low level grid service. |
| + *some discussion on whether director should even be shown and whether is should be differentiated even further visually from an actor -- one idea was to consider just using the megaphone without the teal square as a background. |
| Line 28 was replaced by line 28 |
| - All feedback is welcome and encouraged, but what I need foremost are suggestions for expanding the computation category to cover several top level types of computation such as integrals, summations etc. We will definitely add an "R" represention which will just be an R. I would also like to add "statistics" as a high level category. |
| + __All feedback is welcome and encouraged, but what is needed foremost are suggestions for expanding the computation category to cover several top level types of computation such as integrals, summations etc. We will definitely add an "R" represention which will just be an "R" since that is the current and known symbol. I would also like to add "statistics" as a high level category. |
| Line 30 was replaced by line 30 |
| - What other types of high level computations do you think need to be included? Remember we are trying to keep to a small set of symbols that specific actors can be categorized to. |
| + What other types of high level categories of computation do you think need to be included? Remember we are trying to keep to a small set of symbols that specific actors can be categorized to.__ |
| At line 31 added 14 lines. |
| + For reference, here are the current symbols and the proposed symbols: |
| + |
| + Director, File, and Display Actors |
| + \\ |
| + \\ |
| + [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler-docs/dev/usability/curr-prop1.gif] |
| + \\ |
| + \\ |
| + All other actors |
| + \\ |
| + \\ |
| + [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler-docs/dev/usability/curr-prop2.gif] |
| + \\ |
| + \\ |
| Line 39 was replaced by lines 53-56 |
| - |
| + *DDP>Equation |
| + *DDP>Model (Statistical, mathematical, mechanistic, simulation, cellular automata, etc.) |
| + *DDP>SpatialProcessing |
| + *DDP>SignalProcessing |
