On 22/05/15 03:27, Carsten Haitzler wrote: > On Fri, 15 May 2015 19:50:37 +0200 Cedric BAIL <moa.blueb...@gmail.com> said: > > i still disagree that this widget is "oh so bad". but do you know what? remove > it then if you all hate it so much, but be warned, i will say "i told you so" > when the day comes. you simply make efl that much harder to use for developers > and hurt its image, adoption and use.
I'm not as much against the concept of the widget as I am against everything else about it. My main concerns are: 1. Yet another widget that "someone needs" but no one is using. I'd have said the same about tabs (like you have in terminology). I'd rather see features get baked in an app before going in. 2. It's against the Elementary spirit. I think it should be marked differently (different namespace?) if not be in a different .so. Why? So developers will be aware of the consequences of their decisions. 3. Shouldn't we just create a few different edje files with different masking implementations that people can just load + swallow an object in to get the same effect? Why do we need a widget we'd have to maintain? I think it's a good tihng to have a few of those that implement different masking and can be used by developers. Also, if you ask me, I think the addition of a new widget into Elementary needs to be discussed and reviewed more before the fact and not after. Thoughts? -- Tom. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
