On 5/7/07, Quentin Mathé <[EMAIL PROTECTED]> wrote: > Hi all, > > To summarize the current situation… we should release: > - Étoilé LiveCD 0.2 in next two weeks > - Étoilé release 0.2 in the week following the LiveCD probably > > After that I would like to have an extra release between 0.2 and 0.3, > this intermediate release would be numbered 0.2.5. > The aims of this release would be bug fixes and refined UI for the > whole environment as it is now. > Why? Mostly because we won't have a radically new desktop environment > anytime soon and we should provide a basic desktop environment > environment quite usable and rather polished. This involves some time/ > work spent on UI improvements now. Even if they are further reshaped > or time to time discarded when we will move away from monolithic > applications to document-centric interaction, I'm strongly in favor > of doing these improvements now rather than continuing development of > a collection of application that behave and look differently and > evolve in their own way at UI level. Making the demo really nice > could help to attract more developers and/or potential users. By the > way, the most compelling reason may just hold in the fact that being > "shiny" is our real goal ;-) > > Main tasks would be: > - polished UI for all applications > - cleaned WildMenus (menu support should be perfect at this time) > - stable Io + Spot reintroduced > - standard UI control size and layout size > - new UI font > - preferences applications (Hardware + Look & Behavior even if they > are partially implemented) > - SystemConfig (related to the previous one) > - both UI and API consistency for menulets by finishing ServicesBarKit > - fully working IconKit > - better website > - better framework documentation
I agree with you mostly. Instead of introducing more features, I rather spend time to improve current ones. Progress may be slower than adding new features, but for users, stable applications are better for day-to-day use. A plan I have is to merge CollectionKit and BookmarkKit. Since we probably won't need to maintain AddressKit in the future, CollectionKit/BookmarkKit can be more flexible. > > Optional stuff: > - cleaned Camaelon > - really basic project support (mostly done at System level) > - tabbed document support in PaneKit (this means all applications > that use NSDocument would automatically benefit from PaneKit features > for combining/displaying several documents in one window) I am not sure PaneKit can fit with NSDocument well. An assumption of NSDocument is that a document can have one or more windows. When tab is involved, the relationship is reverse. A window can have one or more documents. It is still doable, but probably parallel with NSDocument instead of subclass. It might make things easier. > - web browser prototype based on SimpleWebKit (may be a fork of > Mantella) Well, Mantella is so experimental that you may want to start from scratch instead of fighting it. :D > > The target release date would be sometimes around July, August or > September depending on the feature set finally choosen. LiveCD would > be updated to match this release. > > I think release 0.3 will probably happen later this fall and will > include new stuff like: > - preliminary Project support > - CoreObject prototype > - etc. It takes us more than one year from 0.1 to 0.2, I am not sure half year will bring us to 0.3. But it depends on the features we want to have. More features, slower release. Yen-Ju > > Feel free to comment, update… > > Cheers, > Quentin. > > > _______________________________________________ > Etoile-dev mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-dev > _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
