Hello all,
I am intending to start a project + webpage (forum + wiki + etc.) for the
"standalone wt application" where following ideas would flow:
* core WT application with:
** basic widgets
** database engine
** plugin layout management with xml or html configuration files (a sort of
html template)
** the configuration file would allow a sort of mechanism for connecting
signals to slots
** administration panel
* plugin management repository and mechanism
Modern websites need following patterns on websites:
* forum
* wiki
* blogs
* gadgets like maps, multimedia, timeline, etc..
It would be interesting to offer an uniform naming convention for links
between forums-blogs-wikis, so a wiki page could become a blog entry or a
forum entry and so on.. implementing simple widgets for forum, blog and
wikis with (modified) markdown that would (eventually) offer compatibility
with most used wiki syntax (mediawiki, wikipedia) ... maybe one day
wikipedia would use the new engine :)
anybody interested to help? Would WT authors feel "offended" ?
On Tue, May 5, 2009 at 4:12 PM, Dushan Savich <d...@stosha.net> wrote:
> Hi all,
> I agree with Mobi, because, if it does anything , the factory
> registration class cuts down the compile time , because you #include less
> files .
>
> Cheers!
> Dushan
>
> mobi phil wrote:
>
> 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());
>
> widget->dataSource(config->getDataSource());
> /// do someway the signal slot connection with other widgets
> }
>
> versus:
> #include "MyWidget"
> MyWidget *widget = new MyWidget();
>
>
> 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.
>
>
>
>
>
>
>
>
>
>
> On Tue, May 5, 2009 at 9:10 AM, Koen Deforche <k...@emweb.be> wrote:
>
>> 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
>>
>
>
>
> --
> being mobile, but including technology
> http://mobiphil.com
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> 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
> listwitty-inter...@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/witty-interest
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
--
being mobile, but including technology
http://mobiphil.com
------------------------------------------------------------------------------
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
