Hey Toma!
Glad to see you posting

and of course I remember you from #e and even from before when you were on #amsn... :p
This is really great news and I'd like to thank you for proposing your help with edje... I'm really not having enough time to keep the efl front end up to date as well as working on the core (which I'm not doing either anyway :p)...
billiob started to work on the efl front end too, he wanted to add support for images....
I suggest you first read the technical details of how we want to do it :
http://thread.gmane.org/gmane.network.instant-messaging.amsn.devel/9502that's the design, so it's really simple and gives a lot of power to the core and minimum power to the front end.. problem with that is that edje can have scripts and can have so many things done in the .edj that it might limit the themeing... but I guess we'll see about that when the time comes...
Did you get the amsn2 svn and got it to work? I saw on #e that you couldn't compile python-efl because it's not updated to work with the latest version of cython.. there's a thread in this forum about it and which version I was using to get it to compile....
I'd like you to read the edc files I wrote for the login screen and get your comments on it, I spent a llloooot of work on that login screen so be kind :p
Anyways, having an experienced edje developer would be really awesome, I just saw the themes you did and they look nice, I have yet to try them...
Do you have any python experience by the way ?
give me your SF username and I'll add you to the team members so you can get write access to the SVN.
About the big, huge EWL/ETK debate... I never know which one to use, I even started a flamewar about that on e-devel a while ago (a year ago I think)... at the time, both were maintained, and both authors were bitching about the other toolkit.. I didn't mind either API and I decided to try them both and see how it goes...
etk_test worked very well.. and ewl_test was buggy as hell, so I thought etk was better, but ewl devs said that the ewl_test app was the one that was buggy, not ewl itself... anyways, I still wasn't too sure (very hard decision) but I liked the 'performance review' wiki page on ewl... and when k-s (the indt guys) were writing python-etk bindings, I decided to go with etk since that's what they were using and they made the bindings for it...
I just tried ewl_test again and it looks like it's still as buggy as before... and I'm not convinced...
anyways, we'll see about etk/ewl later... for now we still need the core to be made into something more usable... have a good contact list and chat window... then we can look at etk/ewl... if we decide to go with ewl, we'll have to first write the python-ewl bindings... and the change will be small.. I was thinking of maybe having efl-etk and efl-ewl front ends.. can't be that complicated!! :p (same code, share the same edje base, and have a flag to either use etk or ewl for the widgets...
after all.. amsn2 is all about the choice of your toolkit

about the textblock thing, that would be cool, but I wonder how indt are advancing with the efl port of webkit...
anyways, our original idea was to implement the obstacles detection in evas, then the webkit idea seems so nice... we'll see about that, but if the efl team can help us with all that, it would be awesome (amsn would become 'THE EFL killer app' so they have a looot to gain by helping us :p).
By the way, as I said before, billiob was trying to implement the Image interface of the front end.. and we ran into some problems.. it seems you can't create an evas image (Evas_Object *) without the corresponding evas.. so we can't create one image, and use it wherever we want (a smiley that we'd want to show in the contact list, and in multiple chat windows...), it also doesn't match with the design, and I think it would be really ugly to create an 'image' object passing it the window where we want to put it... + it's different from other toolkits, so the core wouldn't know whether it would need to create a new Image (if an image/smiley is used twice for two windows) or if it should reuse the one that was created before...
It would be nice to be able to have an Image object not associated with any Evas window, and then add the image to the Evas window and Evas would take care of creating an Evas_Object linked to that Image object....
That's it for now, hope to see you soon with some exciting stuff.. I'd really like to see what magic you can do with edje

Take care
