| Lines 32-35 were replaced by lines 32-37 |
| - *Need to finish updating section 5.3 Director and Actor Icons with most recent icon family categories for the Beta3 release |
| - **sam used the 3 "all-the-actors actor in workflows" directory that Matt made and went back to svg and made some adaptations) |
| - **Laura needs to be reviewed and make suggestion |
| - *Need to finish the screenshots in the GSG.Working with Monica from UCSB people on creating screenshots. Will work with Monica on making sure the GSG images are the same as the Kepler interface -- go over images with Laura |
| + *Need to finish updating section 5.3 Director and Actor Icons with most recent icon family categories for the Beta3 release. Sam used the 3 "all-the-actors actor in workflows" directory that Matt made and went back to svg and made some adaptation to create an initial list. __Laura needs to be reviewed and make suggestion__ |
| + *Need to finish the screenshots in the GSG. __Need to go over the graphic designers images with Laura__ |
| + *Need to change the default parameter in Lotka-Volterra model for the GSG and the saved workflows |
| + *Need to identify channels in the images -- make sure this is reflected in the document and that we adequately describe channel and this idea. |
| + *Need to add a list in the GSG about the complete list of workflows that are shipped with the release |
| + |
| At line 36 added 2 lines. |
| + |
| + |
| Lines 42-45 were replaced by lines 46-47 |
| - **Incorporating documentation into application -- working with Chad on the strategy mentioned below |
| - Strategy: Use the Actor right-click menu to update the individual documentation screens (i.e., update the actor's MOML files). Use HTML <p>, <i>, and <tt> tags to preserve formatting. Save the updated actor files as KAR file and then overwrite the existing files in the /Kepler/src/actors directory in CVS. |
| - In the current system, the application will display the Java doc, unless there is doc info in the corresponding MOML file, which will override the Java doc. The system also examines the class and displays that name. An example of an actor with a MOML doc is the Scatterplot actor. |
| - Documentation about ports and parameters should only be pasted into the actor if it differs from its base class. Will this work? Now that I'm writing this up, I'm a bit confused. We're updating the MOML file, right? Will the class MOML file overwrite a child's Java docs? |
| + **Incorporating documentation into application -- working with Chad on an alternative strategy to the "cut and paste method." |
| + |
