Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Orion/Planning Meeting/Target Users"
< Orion | Planning Meeting
Line 26: | Line 26: | ||
* Edit/Test/Run/Debug (no build/compression) | * Edit/Test/Run/Debug (no build/compression) | ||
* Package/deploy/Debug again (debugging deployed, packaged app) | * Package/deploy/Debug again (debugging deployed, packaged app) | ||
+ | * Wireframe/Mockup/Design | ||
+ | * Collaboration between designers and developers | ||
+ | ** Mockingbird | ||
+ | ** Balsamiq | ||
+ | * Declarative programming with code generation: | ||
+ | ** Mainly HTML generation |
Revision as of 12:45, 18 March 2011
Who is Orion's target user?
- CSS users are very important. Many developers spending a lot of time doing CSS development and are not well served by existing tools.
- Have a need for immediate feedback - tight edit/refresh cycle
- Embed Orion in the site being built to allow in-situ development (mod_orion)
- Server needs to be very easy to install
- Use server locally for offline support
What do small web developers use today?
- TextMate/Notepad
- JQuery/PHP
- Browser developer tools / Firebug
- Various lint tools
Developers of Giant Apps
- Need to be able to work on the site back end functionality as well as web front end
- Develop/debug cycle flows through client and server code
- HAML/SASS/LESS for build-time
- Compression/Closure
- JS Debuggers
Typical workflow:
- Edit/Test/Run/Debug (no build/compression)
- Package/deploy/Debug again (debugging deployed, packaged app)
- Wireframe/Mockup/Design
- Collaboration between designers and developers
- Mockingbird
- Balsamiq
- Declarative programming with code generation:
- Mainly HTML generation