

Note that there won't be much new development on this version of Glade any
more. As soon as everything works for GTK+ 2 and GNOME 2, only bug fixes
will be allowed.

A rewrite of Glade (called Glade 3) is underway, and is in the glade3
module in the GNOME cvs repository.


Glade for GNOME 2
=================

 o Check all signal prototypes we generate & add new ones. (gtk-doc as well)
   - look at gtk+/docs/reference/gtk/gtk.signals to see what needs fixing,
   and in libgnomeui/doc/reference/libgnomeui.signals.
   basically anything that has arg1 in it. Lots.

   o Write a program that queries all signals (like gtk-doc) and outputs
     the prototypes using GTK+ type names. Then check if all the types are OK.


 o 86565 - gail crash in druid. May not be a Glade bug.

 o SM - check the saved XML session file is newer than the real project file.
   If it isn't, load the real project files instead.

 o sort out CFLAGS for GNOME apps - see Owen's message & patch about this.

 o Sort out gtk_window_set_wmclass() stuff. Use title or set_role() instead.
   Need to add a Role property, but GTK+ doesn't support it so would need
   special code in libglade.

 o Check generated code for deprecated stuff.
   How can I do this?
   a) Output -DDISABLE_DEPRECATED in Makefiles and check each widget.
   b) Create a list of deprecated functions and grep Glade code for them.



 o widget tree - add icons & popup list.
 o Get rid of GtkCLists & other badly deprecated stuff.

 o Grid/Snap settings should be in project options, so other developers use
   the same settings. Move to Options dialog.
   Move 'Show Widget Tooltips' to View menu for now.
   Get rid of 'Settings' menu.


LOADING & SAVING
================

  o Let the user open either the .glade or .gladep file.
    If no .gladep file exists, don't save one, unless we have to.
    So libglade users can just use the one .glade file.

  o Check for old GTK+ 1.2/GNOME 1.4 files, prompt to run glade instead.


SOURCE CODE GENERATION
======================

 o source_make_string_internal() - need to handle UTF-8?
   - Can UTF-8 be used in a C string? How? Is C limited to ASCII? Or do we
     assume it is 8-bit clean? But then how will it appear in code editors?


Minor bugs & notes
==================

 o Optional int properties - we currently use a checkbutton with no label, but
   it doesn't receive the input focus. Use a checkbutton with indicator off?
   with tick and cross icons? There is a GTK+ bug & patch about this issue.

 o Look for code that iterates over strings. need to use UTF8 functions.
   - project options stuff that creates options automatically.
   - widget name stuff?
   - signal handler name stuff in menu editor.
   - will only become a problem when non-ASCII used.

 o popup menus - make sure correct menu items are displayed - for widgets
   which can't be deleted/have event boxes added etc.

 o In GNOME version of Glade, if GNOME support is off, don't show the stock
   GNOME items (these have ids that start with 'gnome-stock').

 o buttons with label & icon. Bad interactions between label field in button
   and label, e.g. if you select the label and turn markup on, then select the
   button and enter bad markup.

   Either
    o Turn markup off when we set the label in the button.
    o Use common function to set the label from the button.
      But will this work for all buttons? in libglade?

 o radio groups - the widgets don't update well when you move them between
   groups, e.g. sometimes no widgets in the group are selected. I'm not sure
   if this matters.
