On 13/10/11 14:11, Carsten Haitzler (The Rasterman) wrote:
well here's my take.
signals are a generic abstract way to talk with edje. it literally allows edje
to even have the whole engine run in another process/thread and handle signals
off there. the design allows it so in future we could
On Mon, 17 Oct 2011 08:17:49 +0200 Tom Hacohen
tom.haco...@partner.samsung.com said:
On 13/10/11 14:11, Carsten Haitzler (The Rasterman) wrote:
well here's my take.
signals are a generic abstract way to talk with edje. it literally allows
edje to even have the whole engine run in another
On 17/10/11 08:20, Carsten Haitzler (The Rasterman) wrote:
On Mon, 17 Oct 2011 08:17:49 +0200 Tom Hacohen
tom.haco...@partner.samsung.com said:
On 13/10/11 14:11, Carsten Haitzler (The Rasterman) wrote:
well here's my take.
signals are a generic abstract way to talk with edje. it literally
On Mon, 03 Oct 2011 14:35:59 +0200 Tom Hacohen
tom.haco...@partner.samsung.com said:
Hey guys,
In commit 63771 I added support for adding additional data to edje
signals, and in commit 63773 I added additional info to
entry,changed,user which allows users of the API to implement undo/redo
Hey guys,
In commit 63771 I added support for adding additional data to edje
signals, and in commit 63773 I added additional info to
entry,changed,user which allows users of the API to implement undo/redo
nicely.
It should work just fine for simple entries but there's still one
issue I'm
