Jose Gonzalez wrote: > dan sinclair wrote: > >> To what end? What's the point of tying them together like this? It would >> be better, in the long run, to just have a single widget library instead >> of 3. >> >> > > The 'one true way' of widgetry with the one true mechanism for > theming, > leading to the possibility of a uniform look&feel for 'all' apps? > Maybe. But wether 1 or 3 or 15 widget libs, it's really the one(s) > that have > apps written for them that count - and of those, it'd have to be the > apps that > choose to use default theme elements for the standard widgets and little > else. > There's a pretty standard component/theming mechanism for simple > web pages - html + css, and you still have the issue that people write these > web pages using whatever designs they like.. and even that isn't considered > enough, they want more variability and uniqueness! > >
Is Edje not the one true mechanism for theme? A uniform look and feel is nice, but you'd notice if you looked, Ewl allows you to override the theme on anything you want. At any point in the widget hierarchy. So, yes, I think it would be a good idea to have one widget library. And no, I don't see why you have to lock the theme in. I really don't see how your html example is relevant. People can re-theme Ewl widgets, they can code in straight Edje if they want. They can even embed those Ewl widgets into their Edje application. Guess what, they still get variability and uniqueness. dan ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
