Hey Mobi,
2009/4/29 mobi phil <m...@mobiphil.com>:
> Hello,
>
> I beleieve that more WT mature becomes, the more people will create more
> custom widgets. I think it would be not a bad idea to think about a single
> plugin mechanism, where one would be able to load at runtime custom
> widgets. Widgets would be registered and created/called based on factory
> mechanism (standard object factory registration pattern for classes in DLL)
>
>
> This would fit into the "generic" wt application idea, where web pages could
> be assambled based on some configuration files.
>
>
> What is your opinion?
In my opinion, the nice thing about Wt is that in any case you will
compose your application interface using existing and self-made
widgets. So, there is nothing special about a widget that is part of
Wt, versus one that is specific to your application. It is also easy
to redistribute additional (generic) widgets in a library that depends
on Wt. So, unless I am missing what you want to achieve, I do not
really understand what the benefit of a plugin mechanism would be ?
I.e., what is the benefit of:
#include "MyWidget"
MyWidget *widget = PluginManager::createNew("MyWidget");
versus
#include "MyWidget"
MyWidget *widget = new MyWidget();
?
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
