This file is not a milestone feature checklist, just a list of things
I'd like to do for various releases. It is only a scratch-pad, don't
expect it to make any sense. DO NOT ASSUME THAT IF YOU SEE SOMETHING
HERE, IT WILL ACTUALLY BE IMPLEMENTED FOR THAT RELEASE.
						- Cactus

NEXT RELEASE (0.12)
------------------
Form editor UI improvements:
	showing the name of the currently selected widget in the palette
	select multiple widgets and move/remove them together
	zooming
Store unsupported RCP code blobs as simple text

1.0 BLOCKING
------------
??? more intelligent defaults for width/height (when changing from auto to manual)
??? scrollbar arrow rendering fix
!!! Check positions -- some widgets may need adjustments of plus or minus one pixel here
	and there
Form editor UI improvements:
	showing the name of the currently selected widget in the palette
	select multiple widgets and move/remove them together
---	moving/resizing widgets on the canvas from a context menu/via the mouse
???	zooming
!!! session manager support (yuck!)

Widget checklist:
		LABEL		FIELD		GRAFFITI
		BUTTON		PUSHBUTTON	SELECTORTRIGGER
		CHECKBOX	POPUPTRIGGER	LIST
		SCROLLBAR	TABLE		BITMAP!
		GADGET?!
		( ) Done
		(*) Scheduled for next release
		(?) Needs research
		(!) Not planned for 1.0

POST-1.0 (1.1.x)
----------------
gadget and formbitmap widgets
icons, bitmaps
stringlists
??? Relative positioning
??? In-place editing for texts
custom fonts -- are there any special fontsets? (symbol???)
??? multiple target machines
Migrating to GNOME 2 (depending on the schedule of Guikachu and GNOME 2
	  releases) -- this will likely be post-1.2
RCP importing

Internal stuff
--------------
--- Use Bakery for Doc/View (it might be too late for that...)
Use GnomeVFS for I/O (maybe this should wait until GNOME 2)
??? XML schema for .guikachu file format (would it be useful at all?)
Research the possibility of reusing PilrcEditor efforts
-- Maybe using the canvas is a bad idea and a straight pixel-based
	drawing method would be better?
The specialization hacks in widgets/propertytable.cc are very evil.
	Maybe an intelligent GUI::Widget superclass could solve these
	issues
