Le 26 mai 09 à 20:28, Eric Wasylishen a écrit :
>> 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).
>
> Nice, I added your list for 0.4.2 and started one for 0.4.3
Nice. 0.4.3 won't be released in June, but July imo. I'm pretty sure I
cannot finish the remaining cleaning in EtoileUI in only three weeks.
Here are some more ideas for the 0.4.x (0.4.3, 0.4.4, etc.) series
which is expected to lead to 0.5:
- EScript
- PhotoManager first preview
- Stable and really usable CoreObject. This means to have probably
most of these:
- deletion model & garbage collector
- basic indexing/querying of metadatas
- versioning of structured content into a single persistent root (aka
object bundle)
- UTI-based supercasting mechanism to look up components/services
based on their role and their ability to operate on the targeted
object type.
- Cleaned EtoileFoundation and updated to use the new ObjectiveC2
abstraction layer
- Rewriting of the menu support to have a EtoileWildMenus as minimal
as possible. Most of it should be discontinued or merged into
EtoileFoundation
- Switch from Camaelon to GNUstep theming?
- Structured/Compound/Graphics document editor first preview
There are many more, but that's a starting point in addition to the
project manager you have already mentioned.
>>> -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
>
> Nicolas suggested I also add a page with the embedded video for each
> of our talks at the hackathon.
Good idea. We should probably integrate these with the website css and
offer the ability to dowload the slides (and may be the video too?).
May be we can move all this content from xdev.org to etoileos.com
server?
>>> 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.
>
> I agree, we want to minimize clicks to get to actual content, but also
> provide descriptions for links that might not be clear.
Right.
>> What sort of actual content would be interesting? What me currently
>> miss is perhaps Developer News and links to the core API references
>> imo.
>
> For a new user clicking on "Development, ideally we have an
> introduction to Etoile's architecture, languages, etc. There is a lot
> that's different and interesting that we're doing, so I'd like to show
> that off right away.
Makes sense.
> For existing users/developers, having things in the menu makes it
> easier to get directly to interesting pages. I think we will have
> room in the sidebar to list each framework.
Agreed.
>> 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?
>
> That would be good. A lot of the links are self-explanatory in my
> opinion (Coding Style, Compiling & Installing, Open Projects).
Yes. Only describing the potentially ambiguous ones should be enough.
>>> -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).
>
> Sounds good. I think Vision (or "Goals") could be its own entry in the
> top bar, because it's one of the most important parts of the site.
Good point.
>> Aside of that, the Features subsection of /etoile probably needs to
>> be
>> reworked a bit.
> Agreed.
>
> Nicolas was saying to me on silc, if you're not following a project,
> the things you look for first are: 1/ screenshots 2/ goals 3/ current
> status 4/ download
> which I think is good to keep in mind.
Fully agreed. I'd just add that if you are a developer, you probably
want to look the core architecture and APIs, to see whether the whole
thing is well designed or worth to investigate or use. At least,
that's what I usually do when I discover a new interesting project.
Cheers,
Quentin.
_______________________________________________
Etoile-dev mailing list
Etoile-dev@gna.org
https://mail.gna.org/listinfo/etoile-dev
