From: Nathan I. <nin...@gm...> - 2007-03-23 04:27:38
|
On 3/22/07, jos...@ju... <jos...@ju...> wrote: > > Now that would be good indeed... What exactly would one need > from ewl or etk for this? > One'd also need to come up with a format for decribing such > gui-interfaces, one that would have the concepts of toolkit widget > types, and edje groups... > Any suggestions??? :) werkt put together an app called ewler that did a lot of the serialization necessary for describing EWL widgets. It hasn't been updated in a while, so I'm not sure if it works still. Some combination of this with an edje layout application could provide a basic framework. > It'd be good to see a real example of this combined use > of toolkit-widgets + custom-edje-widgets in an app like "rage" or > "entrance" or "elicit" or whatever. src/bin/ewl_embed_test.c shows how to do this. It's a simple application, but it does show how the interaction can work. > I also think, as I mentioned before, that it would be nice > if the toolkits allowed for 'widgets' obtained via run-time loadable > libs (rather than requiring included headers for custom/derived > widgets), ie. the 'gui-module' kind of thing I mentioned earlier. > Why? Well, I think the 'epplet' kinds of things that eg. > some of e17's modules now give would be nice to have *widely available* > and *easily added* in gui's - and I just don't see why an app should > need to know eg. internal headers for a "clock" gizmo? (maybe just > certain simple interfaces that such a thing might want to export..??). > This might be too unstructured, and there may be better ways.. > but just thought I'd mention it. :) I don't think this kind of gizmo support belongs directly in the toolkit library. It sounds more like a module loading wrapper around widgets that don't export any API calls. An external library, lets call it ewl-candy for now, could do this by defining a module hooks and simply returning an Ewl_Widget. That widget could then be placed inside of any EWL container. The library itself could be very simple, but provide some basic gizmos for re-use. These widgets could also be an extended widget type that exports additional interfaces beyond the base Ewl_Widget class. |