On Thu, May 21, 2015 at 2:03 AM, ChunEon Park <her...@naver.com> wrote: > 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. > > -> These apps are in the 10 % apps in the application world > Anyway they will build up their application whatever they want compatible > with eco-system.
I have no idea where you statistic come from ! Even Windows and Mac OS X have theme ! You are just trowing numbers in the air and dismissing that a large number of application and environment are skinable. I did on purpose not throw number here has there is none. > 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. > > -> Maybe. but it depends on the app design. if you think so. even we should > not provide any content area > because user will put any kind of pre-shaped image as the content what we've > not expected. > Mask is a convenient widget for that cases. I am sorry I don't understand your sentence here and what you are trying to say. Point is, this desktop have a uniform skinable toolkit that work for all kind of application and all their widget do follow this without trouble at all. > 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. > -> Why this is for Tizen Samsung way? Don't misunderstand. And you are > working for tizen samsung. Because that's the only use case where it would have made sense, knowing the people that use EFL there. As for me working for Samsung, sure, I am, but that's no excuse to let everything going in. Elementary has a goal, offering a skinable toolkit for application. It is not a place to drop every bit of logic we don't know where to put. > 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. > -> no problem. i will push an example how people utilize it. No, not an example. An application ! Push a patch that make sense in Rage, Terminology, Enlightenment, EDI, or even Enventor. Example is still useful and needed, but not for validating the usefulness of a widget. -- Cedric BAIL ------------------------------------------------------------------------------ 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
