On 20/05/15 08:21, Cedric BAIL wrote: > Hello, > > So top posting as answering your mail inline is really hard. First of, > I think you are confused by the state of toolkit and application. > There is two big set of application. > > The first one, have their unique user interface design and their own > world. It is the case for many standalone application like Calaos that > control the screen as one application. It is also the case for almost > all website. They have their own look like Facebook is different from > Gmail and so on. There are also a few application like blender, that > have historical reason to have their own ui style. In this scenario, > they can still use elementary and will need to use edje to do a full > customization. Nothing prevent them from providing a themability > capability for there application only. Meaning instead of making a > theme for elementary, you make a theme for Calaos that include all the > style calaos use. > > In that first case, developers need to know edc and need to care about > it. So obviously you won't use your new widget in this kind of > application as this will just not fit in. > > The second use case, it is the classic desktop application. Something > KDE/Qt do with native theme and maybe with QML now (not so sure) and > GNOME/GTK does with CSS. Something firefox also does provide. > Something we try to provide with the default theme of Elementary, an > easy way to have the same theme for every application using EFL and a > way to change the look in a conserted meaningful way. In that > scenario, the developer should never care about the look of his > application and just use default style. User and designer will provide > alternate theme. > > In that second case, developers sure should not know edc and should > not care at all about it. Sadly efl and elementary are not yet on par > of what a desktop application require, so they will need to dig in to > do the missing style and widget, but still in this case your widget > should not be used as it will break the user experience when the user > change the default theme that provide all the default style. > > That's why my assumption of the need of this widget was, this is for > Tizen Samsung way of doing things as it doesn't make sense for anyone > else outside. > > Also the policy for brand new widget in Elementary has been to push > application to develop their own widget to prove that they are useful > (terminology and its tab, edi and elm_code). This was a good idea as > it prove their is a need for a certain type of widget before pushing > something new. Now, please show me an application that can make use of > your widget and that make sense in our eco system. I still fail to see > the point of this widget wich doesn't fit in at all.
I think your last point is the strongest one. It's very easy to prove it's usefulness with a real world application. It also gives it time to evolve without forcing a possibly wrong API from the start. I think we have enough useless widgets in elm. :) -- 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
