Hey Mobi,
2009/5/5 mobi phil <m...@mobiphil.com>:
> Koen,
>
> you were close... but missed the point however:
>
> the difference would be between:
>
> MyApplication::addWidget(Config config)
> {
> //#include "MyWidget" ... this is not necessary!!!
> MyWidget *widget = PlugenManager::createNew(widgetConfig->getName());
Aha, I see.
Then it would be WWidget* (or WInteractwidget* ) widget = ..., right ?
I.e. you could place it somewhere, but not really interact with the
widget as you only get the generic interface?
>
> widget->dataSource(config->getDataSource());
> /// do someway the signal slot connection with other widgets
This could then only be done for signals/slots that are generic, or,
otherwise you would need some string-based lookup for signals/slots ?
> so the widgetConfig would read from a configuration (xml)file/database etc.
> I mention that this idea was in the context of the generic WT application
> that would have a core widget collection, would have a mechanism to read
> pages layout from xml/html etc (this was already a topic few months ago).
> The user would be able to deploy new widgets to a directory as dll, and the
> generic application would be able to read them with or without restarting
> it.
>
> The generic wt application would have an administration interface where the
> user would define layouts, would manage plugins etc.
Okay, now I understand what you are getting at. It might be useful
(and feasible) to implement get-signal-by-name() functionality in Wt
for this.
I also think a plugin mechanism could eventually become part of Wt,
but because of the uncertainty on requirements and use-cases (and
portability for loading a .so/dll), I would keep it outside the
library itself, until its API and usage matures. I think it makes an
excellent project in its own right (cfr your other post in this
thread).
Regards,
koen
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
