Hi Eric, Le 26 mai 09 à 09:05, Eric Wasylishen a écrit :
> Hey Everyone, > Now that the hackathon is over and I have some free time, my first > project is finishing the website improvements I've wanted to make for > a while. That's really great! :-) > - I started an FAQ page at http://etoileos.com/faq/. Currently Jesse's > precognitive FAQ from the old site. Looks like a good start. > - I also started a "Current Status & Roadmap" page at > http://etoileos.com/dev/roadmap/ ok. We should probably mention 0.4.2 and possibly 0.4.3. I expect 0.4.2 at the beginning in the coming months (probably in July). Here is what comes to my mind for the upcoming 0.4.2: - EtoileUI first official/usable release - stable and more polished LanguageKit. This might include stuff like: - debugging support (may be the only work that remains to be done is in CodeMonkey now, I don't really know) - friendly parsing/compilation error reporting - probably other improvements worth to mention - CodeMonkey first preview - Cleaned EtoileSerialize and CoreObject may be: - ETSerialObjectStore protocol which represents a full object with all its history rather than just a branch (this will allow to remove code in CO that more or less simulates that) - COObject hierarchy returns proxies and not real instances (which means the object graph restoration code can be simplified) - the possibility to update/migrate the database schema. We should at least handle basic addition/removal of columns/tables without deleting the old database - FUSE bridge (to be committed and cleaned) - EtoileUI backend (already committed in EtoileUI/CoreObjectBackend, but needs to be cleaned) - concurrency control - update/notification to push changes to processes that access the same core objects concurrently - Generic Object Manager prototype written in Smalltalk+CO+EUI… yes the Potato thing I have been working on during the hackathon :-) - Updated Mélodie that uses the latest EUI API, support undo/redo (works in CoreObjectExample, but not in Mélodie currently) and pick/ drop (although the broken drag and drop is mostly to be fixed in EUI and AppKit) - ObjectiveC2 abstraction layer - and probably other stuff I'm not currently able to remember… :-) > -Finally, I added "Events & Publications", > http://etoileos.com/eventspublications/. Very nice. You could add the following ones I think (David might have other suggestions too): - http://www.cs.swan.ac.uk/~csdavec/papers/google.pdf - http://www.cs.swan.ac.uk/~csdavec/papers/languagekit.pdf - http://www.swan.ac.uk/compsci/research/reports/2008/CSR14-2008.pdf > My current plans are: > - Start to use the sidebar for listing sub-pages in a section, rather > than filling the page body with those h2 headers which are also links > and verbose descriptions. This will leave more room on the page body > for actual content (I started to do this on http://etoileos.com/dev/) > Does this sound okay? I like the sidebar changes you did, but I'm not fully convinced the rest of the page is bad. I'm not saying it cannot be improved though. A relatively detailed map of the developer oriented content seems to be the most useful start page for a developer section. I tend to dislike most developer portals because you have a bunch of clicks to do when you want to access the actual content, or you cannot have a quick overview of the whole developer section or you have one but without short summaries and some links are then unclear. What sort of actual content would be interesting? What me currently miss is perhaps Developer News and links to the core API references imo. At least, I'd like to keep somewhere the small descriptions which explain the purpose of each subsection… may be as tool tips on the sidebar links if they are listed here? > -Redo the /etoile section to mostly be about the "vision", with a bit > of a history section and a references section. There will links to > different sets of mockups, maybe with one page dedicated to the latest > agreed upon UI ideas? I think Vision should be on a different page and will probably need to be splitted on two or three pages. imo /etoile should keep a small overview with screenshots of Étoilé in its current state. This quick overview could have a very obvious link to the Vision page which explains every points of the quick overview with plenty of details. Each list entry in the quick overview could also be linked to specific parts in the Vision page(s). Aside of that, the Features subsection of /etoile probably needs to be reworked a bit. Thanks again to tackle this Eric :-) Quentin. _______________________________________________ Etoile-dev mailing list Etoile-dev@gna.org https://mail.gna.org/listinfo/etoile-dev
