On 9/9/07, Youness Alaoui <[EMAIL PROTECTED]> wrote: > On Sun, Sep 09, 2007 at 05:48:56PM -0400, Christopher Michael wrote: > > Youness Alaoui wrote: > >> Hi, > >> I'm also very interested in such an answer. > >> I've been 'bought' by the EWL developers early when I started looking at > >> EFL. I heard that EWL is more stable, more maintained, better in > >> performance, etc... so I chose EWL. > >> Then I was approached by the ETK developers and I was also 'bought' by > >> them into using ETK. saying that ETK is more stable, more maintained and > >> the performance is also very good (not better than EWL but the difference > >> for a 'normal' application (not using thousands of widgets at once) is > >> not noticeable). > >> I see some kind of war between EWL and ETK. Both are toolkits for EFL, > >> both are good, both are maintained, etc.. and each group says the same > >> thing against the other, but I personally think that both of them are > >> equivalent. > >> I think that this war should cease, because the users of EFL are lost when > >> it comes to choosing one of the two toolkits, and there is nothing > >> official stating which one is to be used. > >> I think that a wiki page saying something along the lines of : > >> - If your application aims to do this and that, then use EWL > >> - If your application aims to do that and this, then use ETK > >> (showing the pros and cons of each toolkit, and saying which one is best > >> suited for your application depending on the use you want it to have, > >> etc...) > >> I'm not a gtk developer either, so choosing ETK only because its API looks > >> like the gtk API is not relevant for me. > >> Right now, I'm working with ETK *ONLY* because cmarcelo is writing ETK > >> bindings for python and I need to work with python, and I don't want to > >> start writing the bindings for EWL from scratch without any help. > >> Can we please finally have an official, objective answer on this very > >> important matter, without partiality and without people trolling one > >> toolkit with false arguments only for the sake of convincing us to choose > >> their own toolkit. > >> Thanks, > >> KaKaRoTo > >> On Sun, Sep 09, 2007 at 01:06:12PM -0300, Diogo Dutra wrote: > >>> What is more recommended to start programing in widgets EFL? > >>> EWL or ETK? > >>> I dont programming in gtk.... > >>> I want know, what is more powerfull, and stable, if possible without > >>> very bugs... > >>> I have started in EWL a little... i should to keep in ewl? > >>> And another question, have a way to set up the ewl theme in E17 theme? > >>> > > > > Sure...this is pretty easy to answer. You use whatever toolkit you think > > will serve your needs best. There Is NO official toolkit, nor do I believe > > there ever will be. > > > > dh > > Yes, but how should we know which one serves our needs best if we can't get a > straightforward and honest answer on the pros and cons of each one. > As I suggested, having an 'official page' (not official toolkit) stating > which one should be used depending on the situation would be useful... > Both are different, both are good, but unless we work extensively with both > of them, we won't know the difference to decide 'which one serves > our needs best'.
I agree with Christopher and I propose another way to "see" it: choose one and ignore the other, pretend it doesn't exist. So far the toolkits are leveled, you'll not loose or gain too much choosing one or another, most of "different" things you'll have to do yourself, like we're doing Python-ETK. Asking for an official position is just asking others to choose for you. If this is the case, then I choose ETK for you :-) Waiting for them to integrate is a non-end thing, I've talked to both teams, both have good points and the main thing: most people work on that on their spare-time or it's their hobby, they can do whatever they want and we have no right to demand them to do our needs. Is like waiting for Gnome or KDE to die and developers migrate to each other. I've proposed that common parts should be made as another library, so more things are shared... as they already share evas (base graphics) and edje (theme), I think that layout could be split in a libelayout, doing hbox, vbox and tabular, with all required packing options (expand, fill, ...), we could use this in other apps, like "rage". But both teams said they're completely different in this area and would need a deep refactor to adapt to this... I proposed to do that myself, but no time yet :-P Anyway, sharing these basic components could (in theory!) lead to these toolkits unifying someday, but someone need to do the work others don't want to do (like this libelayout). -- Gustavo Sverzut Barbieri -------------------------------------- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
