Labs/Bespin/Roadmap/Reboot: Difference between revisions
Jump to navigation
Jump to search
(Created page with '= Bespin Reboot 2009 = We have a new project to reboot Bespin, building on the knowledge that we have gained from the experiment so far. The goal is to allow us to build a solid…') |
No edit summary |
||
| Line 23: | Line 23: | ||
* Provide a UI toolkit | * Provide a UI toolkit | ||
== What are tactical things we want to fix? == | |||
What have we learned from Bespin that we don't want to mimic: | |||
* Use a framework | |||
* Events are great, but not too many | |||
* One system for keyboard handling | |||
* Embedded component must be a first class citizen else it gets left behind | |||
* Tests, tests, tests | |||
* Prototypes, prototypes, prototypes | |||
Revision as of 16:34, 1 September 2009
Bespin Reboot 2009
We have a new project to reboot Bespin, building on the knowledge that we have gained from the experiment so far. The goal is to allow us to build a solid foundation for the community at large to build on.
We have a different schedule for the reboot, which is:
- Weekly meetings, building to in person week
- September 4th; flushing out the high level goals
- September 11th
- September 18th
- September 25th
- In person: Week of Sept 28th
High level principles for Bespin
What are the guiding principles for Bespin?
- Platform for developer tools
- Embedded component is a first class citizen
- Provide a fantastic editor user experience
What are un-goals?
- Provide a UI toolkit
What are tactical things we want to fix?
What have we learned from Bespin that we don't want to mimic:
- Use a framework
- Events are great, but not too many
- One system for keyboard handling
- Embedded component must be a first class citizen else it gets left behind
- Tests, tests, tests
- Prototypes, prototypes, prototypes