Am Wed, 18 Apr 2007 19:42:22 -0400
schrieb Michael Jennings [EMAIL PROTECTED]:
On Wednesday, 18 April 2007, at 21:29:05 (+0200),
Hannes Janetzek wrote:
I would say engage, devian, calendar and all this desklet-stuff
falls in this category for example.
Devian and calendar are both dead.
Hannes wrote:
...
...
In short: there are a bunch of other modules that need to control
how and where they appear on the desk; modules which might have
multiple instance configurations to store.
I would say engage, devian, calendar and all this desklet-stuff
falls in this
On Wed, Apr 18, 2007 at 11:54:28PM -0500, Brian Mattern wrote:
On Sun, Apr 08, 2007 at 03:49:08PM -0400, Christopher Michael wrote:
Hi all,
Mekius recently discovered a nasty segfault when trying to use the Enter
key to dismiss a dialog. As it turns out, this affects all dialogs.
I wrote:
Out of curiosity I looked up desklet and found references
to 'gdesklets' and 'SuperKaramba', which it seems are very popular
projects for gnome and kde respectively.
But there also came up something called 'adesklets', which
is a similar independent project
Brian wrote:
After some more digging, here's what I've come up with:
* When you hit enter, the button widget is 'activated'
* e_widget_activate() calls the No buttons callback, which
deletes the dialog
* this frees the evas, which frees its layers, which frees
its
Hi,
this patch changes the shelfs autohide feature to use polling to detect
when then mouse is out of the shelf.
There is still one problem left: If a module pops up a menu or if one
drags something out of the shelf the shelf doesn't hide. My Idea for
this would be to add the functions
[EMAIL PROTECTED] wrote:
Brian wrote:
After some more digging, here's what I've come up with:
* When you hit enter, the button widget is 'activated'
* e_widget_activate() calls the No buttons callback, which
deletes the dialog
* this frees the evas, which frees its layers, which
Sebastian wrote:
So, should we require that evas callbacks not free their evas?
(E.g. force them to schedule a free and then actually do it
outside of any callbacks)
Or, should we alter evas to defer evas frees while walking
an object's callbacks?
Ummm... this is
Hi,
I quite agree with you, I think that for now, modules are rather
limited. Either a module is contained by a shelf by providing a gadcon
client, or it has to do everything by itself (for example, if we want
to put a module on the background, we have to handle its placement, the
Simon wrote:
I think it would be great if we could place freely modules on the
background, as it was possible with the old gadman thing. It would
allow to have desklets like the ones in adesklets (ie. a cpu monitor
with an histogram for example). Shelf are great for small modules,
On Thu, Apr 19, 2007 at 08:51:43PM +, [EMAIL PROTECTED] wrote:
Simon wrote:
I think it would be good to have freely placed modules in
e17... but I just wonder if this should be the main method for having
large numbers of interesting desklets kinds of things in e.
Write an
Am Thu, 19 Apr 2007 15:46:16 GMT
schrieb [EMAIL PROTECTED] [EMAIL PROTECTED]:
Hannes wrote:
...
...
In short: there are a bunch of other modules that need to control
how and where they appear on the desk; modules which might have
multiple instance configurations to store.
On Thu, 19 Apr 2007 16:04:24 -0500,
Brian Mattern [EMAIL PROTECTED] wrote :
On Thu, Apr 19, 2007 at 08:51:43PM +, [EMAIL PROTECTED] wrote:
Simon wrote:
I think it would be good to have freely placed modules in
e17... but I just wonder if this should be the main method for
Of course it has some drawbacks, the biggest I can see is that
modules are dependent to e17 but... who cares, we use e17 :)
And you use the modules -- with e17. Someone(s) has to
maintain them all, throughout the lifetime of e17.. to be in sinc
with it, and error free, and not slow
14 matches
Mail list logo
