RE: [java-gnome-hackers] API freeze - reality

[Jeffrey M. <Jef...@Br...>]

>   I am becoming increasingly worried that we may not be able 
> to meet the
> API freeze. There is an awful lot of work to be done.

I agree that there is an awful lot of work to be done but
I am still optimistic that we can meet the API freeze date
of Feb 16th.  The past few weeks have been holiday time and
things have moved slowly.  Now that is behind us and I
expect to have a lot of time to work on the bindings.

> 
> IMHO, the release schedule with an API freeze is wrong for a language
> binding - most of our time is spent modifying api. The reason for
> freezes are so that the other parts of the project can catch up - ui,
> translations, bug testing, etc. 
> With the current schedule, we will probably have very little 
> work to do
> between the start of the api freeze and the start of mass 
> development of
> the next major version. However, we will be very busy the rest of the
> time.

Perhaps we can use this time to fix bugs, enhance examples, and
write documentation.


> To make our plans more realistic, I would like to propose that we now
> concentrate on designing an API rather than implementation 
> and then add
> the implementation either at the same time or just after designing the
> api. We may then spend the time after the freeze implementing our api
> (as well as documenting, translating and creating example apps).
> 
> For example, I would like to add this java api to TreeSelection now:
> public TreeRow[] getRows(){}
> and then spend a long time doing the complicated 
> implementation (based on
> a function which returns a GList *) once all the api has been 
> added for
> gtk 2.4
> 
> Does anybody disagree strongly with this?

I agree with this approach.

-Jeff