1. The Evolution of Redwood Brian Westphal

2. Overview Motivation Multiphase Design Results Lessons Future Work

3. Motivation A development environment that supports the tasks of programmers should support the following: Hierarchical design Parallelism Direct manipulation Algorithmic independence Object-oriented design Open/shared-source Commenting and design principles

4. Multiphase Design Prior research Initial design document Prototype Beta I release Beta II (internal) release Beta III release

5. Prior Research Publication Graphical Programming: A Vehicle for Teaching Computer Based Problem Solving (November 2003) Prior research Initial design document Prototype Beta I release Beta II (internal) release Beta III release

6. Initial Design Document Prior research Initial design document Prototype Beta I release Beta II (internal) release Beta III release April 2003

7. Prototype A “here’s what I’m thinking” demo for Dr. Harris and Dr. Dascalu (May 2003) Prior research Initial design document Prototype Beta I release Beta II (internal) release Beta III release

9. Beta I Release Publications Redwood: A Visual Environment for Software Design and Implementation (December 2003) Snippets: Support for Drag-and- Drop Programming in the Redwood Environment (May 2004) Prior research Initial design document Prototype Beta I release Beta II (internal) release Beta III release

11. Beta II (internal) Release Publication The Redwood Programming Environment (August 2004) Prior research Initial design document Prototype Beta I release Beta II (internal) release Beta III release

12. Beta III Release Publication (submitted for review) The Redwood Programming Environment (March 2005) Beta III will be published online in April 2005 Prior research Initial design document Prototype Beta I release Beta II (internal) release Beta III release

13. Results Redwood Beta III is the next release to be published online in April 2005 Hosted on CSE web server Listed on freshmeat.net

15. Lessons The following pages contain a few of the “big picture” lessons I learned throughout developing Redwood

16. Lessons Spending time to well-design your product will save countless hours when it comes to implementing (and re- implementing) a project. Simplify, simplify, simplify - a little smart code makes up for a lot of dumb code. If a smaller part of a project can be made into a subproject, encapsulate it, unit test it, and remove it from the main project code.

17. If you’re unsure of how to use a key piece of technology required to implement your project, learn it ahead of time and work with it as a separate project for a while. Always think of better ways to do things, but evaluate the amount of resources it will take to implement any changes - it might not be worth implementing a “better way” if a working solution already exists.

18. Future Work Online snippet browser integration Internationalization Increased platform and compiler compatibility GUI editor for developing snippets Expanded set of core snippets Security

19. Thank You! Questions, Comments, and Concerns