Since it would usually be a waste of space in embedded environments, PicoGUI doesn't 
have any way (other than reading the property and seeing if you get an error message 
doing so) to get information on supported properties. It would need to use an external 
table of property names, descriptions, and information on the expected data type. (all 
properties are fundamentally 32-bit numbers, but they might be a handle to a more 
complex data type)

This could be hard-coded into glade, or even better read from the picogui header files 
at runtime.

At the moment it's looking like we might as well write a GUI editor from scratch in 
100% picogui code, since picogui has lots of weird features that are probably hard to 
support in an existing editor.

But, when the time comes to start actually coding an editor I will keep glade2 in mind.



On Tue, Feb 19, 2002 at 02:04:33PM +0100, Carlos Perell? Mar?n wrote:
> El mar, 19-02-2002 a las 12:22, Micah Dowty escribi?:
> > PicoGUI does pretty much everything with an interface like this:
> > 
> >    myWidget = pgNewWidget(PG_WIDGET_BUTTON, PG_DERIVE_INSIDE, parentWidget);
> >    pgSetWidget(myWidget,
> >                property_1,  value_1,
> >                property_2,  value_2,
> >                ...
> >                0);
> > 
> 
> We were talking about how PicoGUI gives us the properties for every
> widget.
> 
> With gtk we have the ParamSpec (from gobject) options that gives us this
> information, then, with the widget class and the library we can get all
> its properties at runtime.
> 
> > That would indeed be nifty if glade2 could be made to use PicoGUI widgets like 
>this. The other concern though is having real WYSIWYG previewing while you build the 
>GUI. I have been assuming that with Glade I would have to wrap Gtk widgets with a 
>layer to emulate PicoGUI widgets' properties. Is this the case, or could it be 
>interfaced somehow to use real PicoGUI widgets?
> > 
> 
> I'm busy now with other tasks (i18n issues) but I will try to look for
> options.
> 
> The most important thing is that you tell us how could we get all
> properties from a PicoGUI widget or must we code all properties as
> glade1 does?
>
> > Thanks,
> > Micah
> > 
> 
> Cheers.
> 
> > On Mon, Feb 18, 2002 at 05:14:50PM +0100, Carlos Perell? Mar?n wrote:
> > > El vie, 15-02-2002 a las 19:59, Damon Chaplin escribi?:
> > > > On Thu, 2002-02-14 at 23:00, Micah Dowty wrote:
> > > > > Hello,
> > > > > 
> > > > > I was wondering how difficult it would be to adapt Glade to edit GUIs other 
>than GTK. 
> > > > > 
> > > > > I'm the original author of PicoGUI (http://picogui.org), a new GUI 
>architecture designed for embedded systems. We've been wanting to implement a "widget 
>template" feature where a predesigned layout of widgets including their properties 
>and all related objects can be designed ahead of time as a template, then 
>instantiated one or more times by the application later on.
> > > > > 
> > > > > The format used at runtime would be optimized for minimal CPU and memory 
>usage, but we're thinking about using XML as the source format. Since Glade is a GUI 
>editor, and uses XML, I thought it might be a good starting point.
> > > > > 
> > > > > In case you're wondering about the differences between GTK's needs and 
>PicoGUI's needs... PicoGUI is client-server, but all widgets are built into the 
>server. Widgets have properties, and they can generate events, like the signals in 
>GTK. PicoGUI does not allow x,y coordinates, and instead every widget has a couple 
>properties to specify the layout. PicoGUI has something like a layout manager built 
>in, that requires each widget to 'stick' to one side of its parent then use the 
>remaining space for the next widget in that level of GUI hierarchy.
> > > > 
> > > > I'm afraid Glade is extremely GTK+-specific, so I doubt much of the code
> > > > would be of use. Though maybe the overall architecture may be
> > > > interesting.
> > > > 
> > > > If the PicoGUI widgets support generic querying & setting of widget
> > > > properties then you may want to look at the glade2 module in CVS rather
> > > > than the original glade (where we had to code individual support for
> > > > each property).
> > > 
> > > 
> > > Yes, If you have this feature it's ?easy? to use glade2 with PicoGUI. If
> > > you use gobject (from glib) as gtk does you will be able to use glade2
> > > as libgnome will do (almost I'm trying to do it this way).
> > > 
> > > 
> > > Cheers.
> > > 
> > > > 
> > > > Damon
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Glade-devel maillist  -  [EMAIL PROTECTED]
> > > > http://lists.ximian.com/mailman/listinfo/glade-devel
> > > -- 
> > > Carlos Perell? Mar?n
> > > mailto:[EMAIL PROTECTED]
> > > mailto:[EMAIL PROTECTED]
> > > http://www.gnome-db.org
> > > http://www.Hispalinux.es
> > > Valencia - Spain
> > 
> > 
> > 
> > -- 
> > Only you can prevent creeping featurism!
> > 
> > _______________________________________________
> > Glade-devel maillist  -  [EMAIL PROTECTED]
> > http://lists.ximian.com/mailman/listinfo/glade-devel
> -- 
> Carlos Perell? Mar?n
> mailto:[EMAIL PROTECTED]
> mailto:[EMAIL PROTECTED]
> http://www.gnome-db.org
> http://www.Hispalinux.es
> Valencia - Spain



-- 
Only you can prevent creeping featurism!

_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/pgui-devel

Reply via email to