On 12 Feb 2008, at 20:06, Michael Sweet wrote:
>
> If we did a simplified .fl parser that supported standard FLTK
> widgets with no extra code and callbacks specified by name only, we
> would have a (very) basic form of what you get with Cocoa.  Adding
> custom class support would require the application to register that
> class with the parser.  Similarly, widget pointers could be set by
> name...

OK. That sounds like too much effort to make it work, then...
So we come back to something like a per-locale file (in some format,  
generated somehow I haven't figured out) that would be a list of all  
the widgets in the GUI, and for each it would hold the size,  
position, and localised strings. And maybe some other stuff?
And what about widgets that get created on the fly...? This idea  
isn't going to work.
Anyway...
So the C++ objects and the connections between them would be fixed at  
compile time, but their layout would be configured on a per-locale  
basis, applied at startup. So the widgets can be the correct size for  
their labels, and in the correct relative positions - e.g. we can  
flip the entire GUI over for R-to-L text, if needs be.
Each locale-file would maybe be auto-generated from the default, but  
then tweaked by hand to be "correct", before being written to it's  
file - by some kind of tweaked fluid I suppose.
Oh, that sounds a lot like gettext or etc., really... Only with widgets.

I'm almost certainly not going to write this code, so I should  
probably just shut up.
-- 
Ian

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to