On 21 Jul 2008, at 16:15, Nicolas Roard wrote:

> Hi there,
>
> Sorry for the lack of response, I was swamped at work last week and
> only going through my email now... ;)
>
>>>> For future releases (up until 1.0), we have decided that odd  
>>>> numbered
>>>> point releases should be 'user' releases and even numbered point
>>>> releases should be 'developer' releases.  This means that the focus
>>>> for 0.4 will be frameworks, developer tools, example apps, and
>>>> documentation.
>>>>
>>>> Things I definitely want to see in 0.4:
>>>>
>>>> - Pragmatic Smalltalk 1.0
>>>> - EtoileUI 1.0
>>>
>>> These two can be ready in time I think.The time could be too  
>>> short for
>>> real in-depth code review of EtoileUI though.
>>
>> That's fine.  I'd like to see all of the EUI APIs reviewed before  
>> 0.4,
>> but the code can be reviewed incrementally afterwards.
>
> Pragmatic Smalltalk and EtoileUI will be the two corner stones of  
> the 0.4
> imho, so we shouldn't attempt to do the release if we are not sure  
> of their
> status.

I agree.  They should be ready, and should have had their interfaces  
reviewed, but they don't necessarily need a full code review for 0.4  
(although one would be nice...).

>>>> - EtoileFoundation 1.0
>>>> - Stable Camaelon release
>>>
>>> I wouldn't count on these two. I mean they are  going to be part of
>>> the release but I don't think we have time to improve the code, tune
>>> the API and write all the doc.
>>
>> Most of EtoileFoundation is documented.  The big thing I want to do
>> here is gut the uuid library and just pull the bits we actually use
>> directly into EtoileFoundation.  I'd also like to remove some of the
>> UK* classes  that are not used.
>>
>> For Camaelon, does Nicolas have an opinion?
>
> What exactly is not stable ?.. (not saying there's nothing to improve,
> just asking if there are stability issues right now?)

I think there is an issue with Camaelon + GORM (I remember having to  
turn of Camaelon for GORM, not sure if this is fixed).  There are  
also a few controls which are incorrectly drawn.

>>> Cleaning the UnitKit code a bit would be nice and integrating your
>>> UKMock code too. I haven't taken a look at it yet :-/
>>
>> Sure.  UnitKit is in quite a good state now, and the mock object code
>> can go in easily.
>
> The current UKMock code is far from being really complete I think.

It implements minimal functionality.  Patches welcome.  I've never  
found a real-world use-case for mock objects so I'm probably not the  
best person to do this...

>>>> What other thing should be in
>>>> this release?  User applications are less of a priority - we have
>>>> until 0.5 to get them really polished - but it would be nice to
>>>> have a
>>>> few working, at least as examples.
>
> Well, there's the documentation stuff that I need to submit asap,
> and we should have after that an ok documentation process that we can
> use. As a dev/framework release, documentation should be one of our
> main focus. Actually, shouldn't we try to write tutorials (even  
> short) ?
> This might be worth delaying the release by a month, in fact.

Documentation for frameworks is important, as are examples.

>>> A structured text editor as Nicolas has been working on would be  
>>> nice,
>>> a rudimentary photo manager too. I could eventually turn the crude
>>> MarkupEditor example (for plist and XML) I wrote for EtoileUI into a
>>> real application if there is an interest. But as we discussed and
>>> planned it during the hackataton, it makes more sense when combined
>>> with Nicolas' structured editor.
>>
>> All of these sound good.  Nicolas, what's the status of the  
>> structured
>> editor?
>
> Still uncomplete. I have been extremely busy at work --  
> theoretically things
> should settle now though. It would be nice to have it, but right  
> now the
> more important things would probably be the doc & camaelon than the
> editor. Such editor or other applications shouldn't anyway be the  
> focus
> for 0.4 -- more for the upcoming applications push on 0.5, no ?

I was seeing the structured editor as a CodeObject developer example,  
as well as a usable app.  I also want to write a simple outliner in  
Smalltalk as a demo.  It doesn't have to be feature-complete for 0.4,  
but having it working with some basic functionality would be nice.

David

_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss

Répondre à