On Monday 31 July 2006 06:54, Michel Hermier wrote:
> Hi,
>
> I would like to propose the separation of libkopete in to part.
> The libkopete (core) which would contains the core objects.
> And libkopeteui which would contains all the gui stuff from
> libkopete/ui, libkopete/private, libkopete/avdevice and some of the
> kopete application ui (for the default ui).
> The libkopeteui would be to provide the standards object interface to
> access and manipulate the gui.
> What is bothering me a lot with current code is that we can't reuse it
> for plasma integration (and KPart).
> One of the main example is the contact list, one would probably ask to
> put the contact list on the desktop (this was done via plugin). But
> what the plugin has to do ? Handle the dcop communications, and fill
> the contact list ... In fact reimplement all the code from the core
> kopete application (at the exception of the dcop/dbus communications).
> Another example would be the chat windows. They can't be really
> skinned. What to do if a user want the look and fill of X or Y. With
> this we could simply create chat window plugins, without changing the
> core lib.
>
> As I see it libkopeteui would use libkopete directly in a first time,
> and go dcop/dbus/kpart, in a second time.
>
> Comments ?
>
> Michel

All in all, I think this is a good diea, although i'm sure we'll be discussing 
later the real directory layout, etc.
--
Matt

_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel

Reply via email to