[PATCH] Panel Clock Improvements: I18N tooltip, calender popup

Oliver M. Bolzer oliver at fakeroot.net
Fri Dec 5 20:28:52 CET 2003

On Fri, Dec 05, 2003 at 03:38:42PM +0100, Jasper Huijsmans <jasper at moongroup.com> wrote...
> The advantage is that all implementation is inside xfcalendar, so it
> doesn't need to be kept in sync. If Korbinus decides to start using
> D-bus for communication it will still work ;-)

Basic problem: how to communicate between processes.
 A. Define some kind of IPC-mechanism. Sockets, XEvents, Telepathy whatever
 B. Do everything over command line. How the newly invoked instance tells
    the already running instance the information is implementation detail.
    The mechanism and interfaces for that would be the same as A, but the
    interface is not exported.

I guess it's more a matter of taste.

> The only thing that will not work with this method is the special
> calendar positioning, but I'm not sure that is necessary. If you feel
> strongly about this, it might be possible to come up with a command line
> option to xfcalendar that takes care of this.

Well, I actually DO feel very strongly about it. I probably wouldn't die
if the calender popped up right next to the tasktray icon, but the clock
would be more convenient. I must confess, that the calender popup was
THE one single thing, I liked most in KDE and missed when I first tried
XFce. Time and Date somehow belong together and when I click on the clock,
I don't want to move my eyes to search for the calender. I look at it for
a moment and then close it again with another click.

Having the ability to make the calender move to another place makes it
possible to "embed" it into other applications, too.

> Forget about options ;-) We have xfcalendar, it's a perfect fit, if you
> don't install it, you get no calendar.

:-) Fine with me.

	Oliver M. Bolzer
	oliver at gol.com

GPG (PGP) Fingerprint = 621B 52F6 2AC1 36DB 8761  018F 8786 87AD EF50 D1FF

More information about the Xfce4-dev mailing list