[Kommander-devel] Kommander plugins

[Eric Laffoon]

On Sunday 13 April 2008 11:53:45 pm Andras Mantia wrote:
> On Monday 14 April 2008, Eric Laffoon wrote:
> > I just thought I'd mention that so far any attempts in the plugin not
> > to reference libkommanderplugin or to build Kommander with the
> > additional library have all cause failures where nothing seems to
> > know where anything is. I'll look at it more, but any help is
> > appreciated.
>
> I can't log on right now to my home PC to check it, but as I said the
> widgets directory is just a plugin. So look there to the CMakeFile.txt
> how it is done and look at the kmdrplugins.cpp (if I'm right), how the
> plugins are registered. But this isn't different from the old version.
>
> Andras

The problem is just misleading. I link to kommandercore and everything builds, 
but then I get an error for every reference to an sql class, but in linking. 
It shows the plugin 100% compiled, but it can't link. There are so many 
errors, seemingly nearly every line, I assumed it must be something with 
Kommander. Instead it has to be a cmake issue with the QSql module, which 
must require some additional info to link.

I did have to make several fixes like exporing kommanderplugin.h. 

I was looking at enabling the widgets for the new designer. There is actually 
more to it than I thought, but it's not that bad. 
1) a pretty much boilerplate header file for a designer pluging class
2) half a dozen or so functions to set up the widget in a cpp file, mostly 
boilerplate
3) one main loader class to load it as a group instead of scattered all over

Of course every widget needs to be there to be useful. BTW I'm thinking about 
discontinuing the rich text widget. Anyway my one concern here is if there 
might be any problems with a widget and designer, but it seems they ought to 
be fine. I think the plugin files should probably go with the widgets as they 
will be logically together for these purposes.

-- 
Eric Laffoon
Project Lead - kdewebdev module