Hi Everybody,

This email is mainly because I haven't said much on here in a while. I haven't had 
much time to work on picogui lately, but these still seem to be the main issues at 
hand for me at least, in order of importance:

 - Textbox widget
 - Widget templates
 - Moving standard dialogs to pgserver (dependent on widget templates)
 - Modularizing network protocol in pgserver (dependent on standard dialogs in server)

The textbox widget.. I haven't worked on it much recently, as you all have certainly 
noticed. The current architecture is flexible yet slow, so it's both difficult and a 
little unsatisfying to work on. I might take on a redesign of the textbox widget 
myself. Of course there's still the possibility that Blue Mug will have a nifty 
textbox, but their most recent design isn't nearly as flexible as I'd like.

Widget Templates.. the WT loader in pgserver has been done for a while now. Lalo has 
WT writing support in the Python client lib, but he hasn't had time to write the 
actual compiler. One thing we can do to help besides actually writing the WT compiler 
is to create sample XML files that it will eventually be able to process. I've had 
some thoughts on it here, but nothing too substantial:
   http://picogui.org/wiki/view/Main/WidgetTemplateXML

The other items are dependent on WT support, so I haven't touched 'em yet.

In other news, James Hollingshead and others have been working on some fun new PicoGUI 
apps. BigThor is porting xmerlin (a handwriting recognition program) to PicoGUI and 
already has a version that works and should be in CVS soon.

Many apps should go in CVS, but some are already being maintained outside of 
picogui.org. If PicoGUI is to eventually become a successful general-purpose GUI with 
a large base of applications, we'll need somewhere to index them all.

Of course, we don't even have the first release out yet :)
And that brings us back to the textbox widget...

-- 
Only you can prevent creeping featurism!

Reply via email to