Mailwatch plugin ported to new panel

[Brian J. Tarricone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jasper,

I was looking through your diff, and I noticed something I meant to
comment on earlier, but forgot.  Is it really a good idea to tie the
panel's config API to XfceRc?  I can see instances where someone might
want to use an XML file, or some other configuration mechanism.  And
this makes it pretty much impossible to add better/different config
mechanisms to Xfce in the future and use them easily within panel plugins.

I'd suggest just returning the file name of the config file, and let the
application decide what to do with it (which may indeed be
xfce_rc_simple_open(), but let the plugin developer decide).

	-brian

On 9/16/2005 10:48 AM, Brian J. Tarricone wrote:
> On 9/16/2005 2:45 AM, Jasper Huijsmans wrote:
> 
>>>Hi all,
>>>
>>>To test the new panel plugin API, I decided to try and port one of the 
>>>more complex plugins, mailwatch. Well, it was a piece of cake ;-)
> 
> 
> Ok, now that's just freakin cool.
> 
> 
>>>Whether this is due to the exemplary modular design of mailwatch, or my 
>>>l33t API designing skillz, I'll leave for you to decide ;-)
> 
> 
> I'll take the diplomatic route and say it was a combination of the two ^_^.
> 
> 
>>>Anyway, I imported it into branches/experimental of the 
>>>xfce4-mailwatch-plugin in SVN. Brian, I hope you don't mind. Feel free 
>>>to ignore it and come up with something better.
>>>
>>>It should just work, but of course I may have missed a couple of things, 
>>>so if you're feeling bored, you could try it out.
> 
> 
> Cool.  I might have a chance to look at it tonight, otherwise in a week
> or so.
> 
> 	-brian
> 
_______________________________________________
Xfce4-dev mailing list
Xfce4-dev at xfce.org
http://foo-projects.org/mailman/listinfo/xfce4-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFDKwlE6XyW6VEeAnsRAreqAJwJkQnmBYc8jfQPq5WQXVO0g7SEeQCfdEdp
vf3BH1pH3jCfJzgqQis/i+w=
=yxCb
-----END PGP SIGNATURE-----