changed:
-
- Copy/Paste widgets the Linux way by using the middle mouse button and maybe holding in SHIFT to move. (Terje Pedersen - http://senikk.com)

- Try to put all project windows in a notebook inside Gazpacho interface as http://couve.no-ip.org/shots/one-window-glade.png . Problems of this approach:
  
  - width and height properties for the window are not WYSIWYG anymore
  
  - internally Gazpacho needs a toplevel widget to know how to draw the selection rectangle of a selected widget. I guess this can be changed but maybe tricky because it's low level gdk stuff

- More Documentation:

  - How to create, support and use custom widgets within gazpacho

  - Short tutorial (probably taking as reference and adapting an existing one)

  - Write general help, overview, options, etc... using devhelp? or plain html?
  
- Widgets templates as Johan suggested

- Have special HIG templates

- Include links to xml files in glade files for widget reutilization

- Write a DTD for Gazpacho xml files (just differences between libglade DTD)

- Think about the Palette organization: How many widget groups should we have and which widget should go in each group

- Translate everything into different languages

- Write a miniHOWTO about the creation of an i18n application with Gazpacho. There must be a better solution to i18n than the solution suggested at: http://www.daa.com.au/pipermail/pygtk/2000-July/000157.html - Update: Found a solution at: http://primates.ximian.com/~sandino/python-glade/tepache/

- <strike>Write a .desktop file</strike> (*done*)

- Have a debug/logging system

- Improve Project support: when there is no project open we should desensitice most of the UI. Right now the Project Menu is always inactive and we should fix this and test opening, closing and creating a lot of projects.

- Put Gazpacho UI in a .glade file and make Gazpacho loads itself at runtime (This may be a good thing for 1.0 so we can show everybody that Gazpacho is actually working)

- <strike>Write an uninstall script</strike> (*done*)

- Look into making Gazpacho work with other IDE's such as Eclipse.

- Add tooltips to palette buttons showing short description of widget, as in the pygtk reference.

- Add tooltips to Editor labels that explain properties. Also we could use short descriptions from the pygtk reference. (Works for Gtk+ widget properties, but Name and Class properties are missing, as signals in the signals and callbacks treeview).

- Make gazpacho work fine on small resolution screens, probably using ellipsization when we have long strings and, in general, trying to avoid minimal sizes being too wide/tall for containers.

- Would it be possible to have a pygtk coded devhelp so we could run it on every platform gazpacho works?

- Write a text on how to use gazpacho generated files using pygtk. Are they handled the same way as glade files? Do you need some special loader? What about custom widgets? what about the proxy? are we waiting for kiwi2? :)...

- Write an example of a pygtk coded widget showing needed methods to get it working, how to add it to the palette as a custom widget (this is already in a txt), and later how it can be used in a little pygtk project. As the previous suggestion this shows we lack a lot of docs explaining how to use tools outside their world. Maybe mini-tutorials could be useful.

- Could gazpacho be used in other editors such as anjuta, pydev (eclipse)...? Is there something easy to do this? D-BUS support?

- Make gazpacho use Command internally for all actions so it becomes a sort of interpreter and so it is more easily scriptable and may be used to test GUIs

- Make into a full studio for python at least.

- Make it possible to design non toplevel widgets, i.e. components that are not sit inside a Window or a Dialog or any other toplevel widgets. ("Bug #301335":http://bugzilla.gnome.org/show_bug.cgi?id=301335 )