Hi Carsten! I bow before your words of wisdom, lol. Everything you said makes sense and that's what I understood from the start (kind of). I like your analogy of apple and orange juice :p As I said many times, I never asked for an "official toolkit" (although I presented that idea, as part of a 'let my brain go free' theory about ETK wrapping EWL in order to have the API and look&feel it wants without duplicating code efforts). I was merely asking for an official (non biased by either group members) position on the pros and cons of each toolkit. the EWL guys will tell me that EWL is better, the ETK guys will tell me ETK is better, but both teams use their own way of presenting information, which may or may not be completely true. Maybe I should have said "the opinion of someone who investigated both projects" instead. By opininon I'm not requesting a "this one is better", but only requesting "this one has these pros and cons, and this other one has these pros and cons", maybe concluded by "I chose x because I needed this and I felt more confortable with its API" for example, which does not mean that *I* would choose the same thing. To go back to your apple vs. juice analogy, one could say : - apple juice is sweeter but has more calories - orange juice is more healthy and has vitamin C I chose apple juice because I like sweets.
In other words, pros and cons, real facts, and in the end, based on that 'comparison table', one could choose what best fits for his application. Having the choice between two toolkits is good (apart from the code duplication involved), as long as it doesn't take 1 week of code reading and testing and proof of concept writing for someone to finally decide which one to choose. Being able to choose what you like best would be easier with such a listing. Again, I don't vote for a single toolkit, I just vote for an 'official/non-official' expertise on the two toolkits, providing the users (of the library) with valuable information to help them decide on which toolkit to choose. Thanks for your time. KaKaRoTo On Tue, Sep 11, 2007 at 08:23:58AM +0900, Carsten Haitzler wrote: > Oh dear me. Look what this has become while i've not been looking. (i'm just > going to reply to the whole thread tree here and ignore the sniping bits - hey > kids - back to your seats!). > > ETK vs. EWL - it can be summed up with: > > "I may not agree with what you say, but I will defend your right to say it to > the death.". > > We are not going to kill one off. They are like Apple vs. Orange juice. ETK > and > EWL developers were working together at one point - but basically had a core > disagreement in philosophy. They have agreed to disagree. Unlike GTK vs. Qt > the > cost is much lower. They share big amounts of core via Ecore, Evas, Edje etc. > I > realise that saying "this one is official" will alienate the other group. Both > groups are important to E in general. Both have made invaluable contributions > and continue to help. At some point (E18/19) I will need to use one or the > other for E itself - but do NOT take this as official endorsement - it will be > based on whichever I feel more comfortable with. > > Those familiar and happy with GTK's API might prefer ETK. Others may prefer > EWL. It's a matter of choosing if you like Apple or Orange juice. Both are > juices. Both quench your thirst. Both are sweet. (And no nit picking on the > analogy. You get the idea!!!). > > Which should you choose? Well - try both. Which one do you like best? No one > can make that decision for you. You either try both - or just make a leap of > faith. Both teams will promote their work - and good for them. take away with > that only what they can tell you factually about their code. > > Now everyone - back to your benches and take 5. :) > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] > 裸好多 > Tokyo, Japan (東京 日本) > > ------------------------------------------------------------------------- > 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 ------------------------------------------------------------------------- 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
