[Qt-interest] Doubts about the Plugin Framework

[Bruno Seabra Lima]

Again i wanna apologize for my english in advance.
****
just giving some feedback to the list
The factory to the real object worked like a charm
thanks.
****

But i have one more question:
I have a core classes that manages plugins, transactions and stuff like that.
My question is:
Can i compile these classes as libraries (including the plugin manager
- that loads and instanciates the plugins),
and still have the main application extended by plugins ?
In resume is necessary that the interfaces and the loader of the
plugins are in the main application ?
Or can i define that in separate library ?

Thanks for all the replies ...

On Wed, Mar 17, 2010 at 5:17 AM, Ender EREL <erelender at yahoo.com> wrote:
> I think you may consider reviewing your design there. Don't forget the
> principle that signals should not be interested in what's connected to
> them so use them as fire-and-forget type of constructs.
>
> Quoting from Qt Docs:
>
> "Signals and slots are loosely coupled: A class which emits a signal
> neither knows nor cares which slots receive the signal."
> ... and ...
> "Signals are emitted by objects when they change their state in a way
> that may be interesting to other objects. This is all the object does to
> communicate. It does not know or care whether anything is receiving the
> signals it emits. This is true information encapsulation, and ensures
> that the object can be used as a software component."
>
> Of course, this is not mandatory but it's just good practice.
>
> Best Regards.
> --
> Ender EREL
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>



-- 
Bruno Seabra Mendonça Lima
--------------
Bacharel em Ciência da Computação - UFMA
Mestrando da PUC-Rio
Pesquisador Laboratório Telemidia (PUC-Rio)
-------------
www.bslima.com