Re: [ddccontrol-devel] Panel Applet, libddcci

[Nicolas B. <ni...@bo...>]

Hello Christian,

Nice to hear again from you .-)

On Tue, 2005-08-23 at 20:15 +0200, Christian Schilling wrote:
> hello,
> 
> first off, sorry for beeing off the project for so long my spare time
> was quite limited (a-levels...)

No problem .-)

> i'm currently working on a panel applet for gnome, with allows quick
> changeing of profiles created with gddccontrol.

Nice idea .-) One thing you should take care of is multi-screen (which
monitor are you controlling?).

> while doing this i noticed libddcci is build as a static library.
> as i needed it's functionality in my applet i changed the makefiles (and
> headers) to build a shared library and install it in $PREFIX/lib
> (headers in $prefix/include/ddcci)

There is no problem about it. My only concern is about two applications
accessing the monitors at the same time. It could create huge problems
(particularly with ddcpci)... I think we need a mechanism to lock and
unlock the libraries, but I've no experience on it. Any idea??

> now i'd suggest to split the project into seperate modules:
> - libgddcc (or libddcci??)
What do you think of libddccontrol ? (the so file would be
libddccontrol.so, and be linked with -lddccontrol)
> - ddccontrol
> - gddccontrol
> - ddcc-applet
Maybe should you a a "g" somewhere, because there are also KDE applets I think.

Now, about the idea of splitting the project in modules, I'm not sure of
what you mean... Do you suggest to split the project in different
tarballs?? If so, I disagree. I think two tarballs (ddccontrol and
ddcontrol-db) are already enough to download, and as their size is
relatively limited I don't see any problem (if you only want some parts
of ddccontrol, you can enable them with configure flags).
Of course, if a packager want to split the project, there is no problem
(you often see this with RPMs: ddccontrol-lib, ddccontrol,
ddccontrol-devel...).

> another benefit of making libddcc a seperate package would be, that fo
> instance someone could write "kddccontrol",

If someone want to write kddccontrol, it would very probably be
integrated into the project.

> or build the funktionality
> into applications like video players (automaticly change to "movie"
> profile, when fullscreen video playback is started)..and so on..

Yes, that's a good idea.

> what do you think about this idea?

I think you can commit your modifications. Please just add a tag before
doing it ("cvs tag Before_shared_lib" for example).

Thanks for working again on this project.

Best regards,

Nicolas