On 9/1/07, Marijn van Vliet <[EMAIL PROTECTED]> wrote:
> Evolve was just the thing I was looking for. Thanks alot Hisham, for
> your thourough answer.
>
Quick answer as I need to run, Evolve needs an update to compile right
now (some eet work). It should hopefully be done soon. (=
> The suggestio
Evolve was just the thing I was looking for. Thanks alot Hisham, for
your thourough answer.
The suggestion Youness makes is interesting, but I would opt for
Evolve to have a plugin system, instead of throwing away the entire
lib (and many, many hours of labour). As far as I can see on first
Hi,
This is interesting, but I thought the same as Marijn when I first saw EWL/ETK.
I had an idea about providing some kind of
plugin system for edje, where you can create custom types. I was more thinking
of something like :
part {
name, "my_entry";
type, ETK_ENTRY;
mouse_event, 1;
...
}
part {
On 9/1/07, Marijn van Vliet <[EMAIL PROTECTED]> wrote:
> While reading the documentation on Edje, I was instantly excited. True
> seperation of programming code and interface design, all in a clean and
> simple way. Then I went on and read about the EWL libary, build on top of
> Edje. And all the E
While reading the documentation on Edje, I was instantly excited. True
seperation of programming code and interface design, all in a clean and
simple way. Then I went on and read about the EWL libary, build on top of
Edje. And all the Edje goodness was gone. In order to have prewritten
text
