Keep in mind that I haven't actually tried adesklets, only read their web site.
On Mon, 3 Oct 2005 10:39:57 +0200 Fernando Meira <[EMAIL PROTECTED]> wrote: > after this I looked for adesklets (I been looking forward to try > gdesklets but dependencies took me away from that idea, since I don't > use gnome), I installed it but couldn't make it working!! After > looking here and there, I found that adesklets are not working under > e17.. but that was on Feb '05. So, is it still like that? > Is there any way to make them work? adesklets draw to the root window using pretend transparency. Since e17 uses what adesklets calls a fake root window, adesklets needs to know that so that it can track down the e17 root window in order to draw on it. There is documentation on the various ways that adesklets can help with this. Since adesklets uses fake transparency, you will get the same problems you get with all other programs that try to use fake transparency with e17. Personally, adesklets and other similar systems try to fill the same niche as e17 modules, and e17 modules are better integrated with e17 for obvious reasons. I'm gonna go with e17 modules. Of course, this means that we need a decent community of e17 module writers. When the e17 API has stabilised we will probably see an explosion of module and theme writers appear. Also on a personal note, engage, the start module, and e17genmenu fill the same need as the gkrellm plugin that I wrote, and my module was incomplete and unreleased. There is still a small thing that mine does better, and I will integrate that into e17 then just forget about my gkrellm plugin. Hopefully after I have fulfilled my current coding commitments I can get stuck into some e17 coding.
pgpHSf2bj0KFv.pgp
Description: PGP signature
