[java-gnome-hackers] RE: Process for next release

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

Correction.  Where I mention the PasswordDialog below I really
mean the BindingSet in the gtk package.

> We need to workout our process for the next release.  After
> reviewing the latest gtk I see that there are many objects that
> have been added that we should support.  Here is a list of
> header files that contain new objects:
> 
> < gtkaction.h
> < gtkactiongroup.h
> < gtkcelllayout.h
> < gtkcolorbutton.h
> < gtkcombobox.h
> < gtkcomboboxentry.h
> < gtkentrycompletion.h
> < gtkexpander.h
> < gtkfilechooser.h
> < gtkfilechooserdialog.h
> < gtkfilechooserwidget.h
> < gtkfilefilter.h
> < gtkfilesystem.h
> < gtkfontbutton.h
> < gtkicontheme.h
> < gtkradioaction.h
> < gtkradiotoolbutton.h
> < gtkseparatortoolitem.h
> < gtktoggleaction.h
> < gtktoggletoolbutton.h
> < gtktoolbutton.h
> < gtktoolitem.h
> < gtktreemodelfilter.h
> < gtkuimanager.h
> 
> For each object we will need to write the glue code (the 
> protected java methods
> that make the calls to the JNI C code), the JNI code, the 
> public iterface, and any
> example apps to demonstrate how it is used.  We also need to 
> deprecate the old
> widgets.
> 
> I propose that we do the following:
> 
> 1) Those who know JNI well can write the glue and jni code 
> for each object.  Once
> this is complete they will check it into cvs and inform this 
> list.  To see an example
> of the state of the java class at this time please look at 
> the new PasswordDialog object
> in the gnome package.  The glue code is inside of the 
> comments at the bottom of the
> file.  Also, this developer will be responsible for any 
> additional Enum or Flag classes
> needed to support the new Object.
> 2) Another developer that wishes to write the public 
> interface for this object will notify
> the list so we don't have more than one person working on the 
> same code.  To see and
> example of the public interface please look at the 
> PasswordDialog constructor.  The
> public interface should be as complete as possible and 
> contain useful javadocs.  If the
> new object is replacing an old object the developer should 
> deprecate the old widget once
> the new one is complete.  Also, the developer should consider 
> writing an example to
> test the widget and to also demonstrate its' usage.
> 
> Please let me know what you think of this process.  Also, 
> please let me know if you
> wish to work on the JNI or interface.  I will be working on the JNI.
> 
> -Jeff