Hi, Can we pick this up again please? if neither 1) nor 2) are likely to happen then I feel the requirement to add 3) so that each app can add 1 line to do fdo_elementary lookups for the whole app. I'm now looking at menus that are a mix of icons because, as far as I can tell, there's no API for setting the lookup order for menu_item icons. Ether way this feels like it's really anti-new-developers - we don't have a complete icon set and I think we need to deal with that.
Either 2) or 3) are changes that I feel have become essential if we can't get 1) resolved in the next EFL release or two... Any strong feelings on how we deal with the current state of play? Cheers, Andrew On Sun, 30 Aug 2015 at 10:39 Andrew Williams <a...@andywilliams.me> wrote: > I agree with this, I can't ship any large featured app using elm icons at > this time, I have to use an fdo lookup. > > If elm were a complete icon theme (including all E, efm and media player > etc icons) the current ordering makes sense - but not until then. > > Therefore I propose for efl 1.16 we need either: > 1) import a complete icon theme that works; or > 2) change the lookup order so efl apps don't look a mess by default. > > And possibly in either case: > 3) add an elm api to set strategy for the whole app > > Primarily I want an elm app to be consistent in itself but overall it > should be consistent with E or the desktop it's running within. > > Andy > > On Tue, 11 Aug 2015 15:39 Stephen Houston <smhousto...@gmail.com> wrote: > >> At any rate, Raster's reasoning is only good if the theme provides a >> complete icon set... so for that to make sense right now, someone needs to >> finish the elm theme icon set or as Davide said just import an already >> complete icon set into the elm theme. >> >> On Tue, Aug 11, 2015 at 7:35 AM, Davide Andreoli <d...@gurumeditation.it> >> wrote: >> >> > 2015-08-11 2:14 GMT+02:00 Carsten Haitzler <ras...@rasterman.com>: >> > >> > > On Mon, 10 Aug 2015 09:53:08 -0500 Stephen Houston < >> > smhousto...@gmail.com> >> > > said: >> > > >> > > > I'm sure this has been discussed before but I feel the need to >> bring it >> > > up >> > > > again. >> > > > >> > > > It is super annoying that when requesting a standard icon, you will >> > > always >> > > > get the blue icon from Elementary first if it exists, and then it >> falls >> > > > back on the icon theme. I feel like this should be exactly the >> > opposite. >> > > > Check the icon theme first and fallback on Elementary's blue icons >> if >> > the >> > > > user's icon theme doesn't have the requested standard icon. >> > > > >> > > > For instance: >> > > > http://www.enlightenment.org/ss/e-55c4c1af28ccf5.97362633.jpg >> > > > >> > > > The blue slideshow icon is out of place here. It should go with the >> > icon >> > > > theme first instead of finding that icon in Elementary. >> > > > >> > > > Thoughts? >> > > >> > > not changing. >> > > >> > > 1. breaks default behavior of an icon object. since icons come from >> theme >> > > an >> > > app dev can customize by doing a theme overlay and thus expect his >> icons >> > to >> > > appear - but if default behavior changes then his app loses HIS icons. >> > this >> > > is a break. no. not changing. >> > > >> > >> > I quite disagree here, but we need to split in two different scenario: >> > >> > A: the developer want to provide an icon that will never change >> (regardless >> > of the user elm theme in use). This is usually wrong, unless you >> > are providing a full theme overlay inside your app (my media center is >> an >> > example), otherwise your icon will looks wrong on other elm themes that >> > the user may be using. >> > >> > B: the developer want to make a themable app that will always looks good >> > for every elm theme. This is the "normal" behavior of desktop >> applications, >> > and at the moment is quite impossible to aquire using elm. >> > >> > I think both scenario can be done using elm: the sceanrio B is coded >> using >> > elm_icon_standard_set(ic, "a-fdo-standard-name") >> > While the scenario A should be coded a little different: the dev can set >> > the icon >> > using elm_icon_file_set(ic, theme_file, "icon_name") or also using >> > standard_set >> > but not using fdo names, fe: elm_icon_standard_set(ic, >> > "my_custom_icon_name") >> > >> > So I think there are no breackage involved, unless an app is using >> standard >> > fdo name while wanted only the custom icon to be displayed. >> > >> > >> > >> > >> > > 2. the point is to have icons match the THEME... not some fdo icon >> theme. >> > > icons >> > > will almost always look out of place in a theme being different >> > style/color >> > > etc. etc. and so people are eternally hunting for a "matching icon >> theme" >> > > separately to their theme. the whole POINT of an edj file is to have a >> > > single >> > > unified theme with everything - widgets and wm and icons etc. your >> point >> > > violates this entire concept. >> > > >> > > -- >> > > ------------- Codito, ergo sum - "I code, therefore I am" >> -------------- >> > > The Rasterman (Carsten Haitzler) ras...@rasterman.com >> > > >> > > >> > > >> > > >> > >> ------------------------------------------------------------------------------ >> > > _______________________________________________ >> > > enlightenment-devel mailing list >> > > enlightenment-devel@lists.sourceforge.net >> > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > >> > >> > >> ------------------------------------------------------------------------------ >> > _______________________________________________ >> > enlightenment-devel mailing list >> > enlightenment-devel@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel