Re: Application specific themable icons
On Fri, 2006-12-15 at 11:49 +0100, Luca Ferretti wrote: Here [1] is a page about application specific themable icons (named icons installed by application outside the system-wide hicolor directory). Feel free to edit (by now it's just a draf), implement suggested changes in your applications and add new subpages listing icons installed by your application[2] (useful for theme maker people). Thanks to Rodney Dawes for the original idea[3]. [1] http://live.gnome.org/ThemableAppIcons [2] http://live.gnome.org/ThemableAppIcons/EpiphanySpecificIcons [3] http://wayofthemonkey.com/index.php?date=2006-11-15month=11year=2006 I participated a bit in some of the xdg-list discussions about doing this, and I was a big proponent of having the application theme directory contain directories for each theme, rather than just have a single set of fallback icons. For me, the big reason was that applications could provide accessibility versions of all their custom icons. What I also wanted was a standard fallback theme for each of our accessibility themes, much like hicolor is a fallback for other themes. That is, our actual high contrast theme would continue to be HighContrast, but it would inherit from some other theme, like hicontrast. That would, in turn, inherit from hicolor. Applications could then install high contrast versions of all their custom icons in hicontrast. Perhaps Rodney knows if there was any further discussion about this. It would certainly be nice for applications to be able to provide for accessibility needs without being tied to one desktop. And the current trend of having our accessibility themes try to provide everything for every application just doesn't scale. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Application specific themable icons
On Mon, 2007-01-15 at 10:57 -0600, Shaun McCance wrote: On Fri, 2006-12-15 at 11:49 +0100, Luca Ferretti wrote: Here [1] is a page about application specific themable icons (named icons installed by application outside the system-wide hicolor directory). Feel free to edit (by now it's just a draf), implement suggested changes in your applications and add new subpages listing icons installed by your application[2] (useful for theme maker people). Thanks to Rodney Dawes for the original idea[3]. [1] http://live.gnome.org/ThemableAppIcons [2] http://live.gnome.org/ThemableAppIcons/EpiphanySpecificIcons [3] http://wayofthemonkey.com/index.php?date=2006-11-15month=11year=2006 I participated a bit in some of the xdg-list discussions about doing this, and I was a big proponent of having the application theme directory contain directories for each theme, rather than just have a single set of fallback icons. For me, the big reason was that applications could provide accessibility versions of all their custom icons. There is no reason they can't do this. In fact, this is exactly what my recommendations here, allow you to do. You can just stick a HighContrast or whatever other theme, alongside the hicolor theme, in the app-private icons directory, and things will Just Work (TM), assuming you complete the rest of the puzzle. What I also wanted was a standard fallback theme for each of our accessibility themes, much like hicolor is a fallback for other themes. That is, our actual high contrast theme would continue to be HighContrast, but it would inherit from some other theme, like hicontrast. That would, in turn, inherit from hicolor. Applications could then install high contrast versions of all their custom icons in hicontrast. Perhaps Rodney knows if there was any further discussion about this. It would certainly be nice for applications to be able to provide for accessibility needs without being tied to one desktop. And the current trend of having our accessibility themes try to provide everything for every application just doesn't scale. I don't think there is any disagreement to wanting standard accessibility themes across the desktops. The KDE people on the XDG list expressed only interest in doing that, when it came up. I don't think there has been any activity in getting it done, though. There have also been numerous suggestions of other ways to do the accessible themes, including automatically deriving such icons from the selected theme's icons. Andy Fitzsimon demoed a little bit of the work he'd been doing on this, at the GNOME Summit in October. In the end, this may end up being the best route to take, as it could mean that all themes are automatically accessible, and we can avoid doing the same work over and over again in a bunch of different files in different themes, spread across the disk, allowing us to pick up a little performance benefit too. -- dobey ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Application specific themable icons
Le samedi 13 janvier 2007, à 20:13, Nickolay V. Shmyrev a écrit :
I dislike the need to install all icons into ${datadir}/hicolor/...
This made me read http://live.gnome.org/ThemableAppIcons and I'm now
wondering about one thing...
The path where apps install icons is $(pkgdatadir)/icons/hicolor. I
guess this path is chosen to avoid conflicts between icons of various
applications. However, how does this work for icon themes you download
and put in ~/.themes/$(name)/icons/? I mean, the name clash for icons of
various apps that the theme author wants to theme will appear there too.
Vincent
--
Les gens heureux ne sont pas pressés.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Application specific themable icons
Here [1] is a page about application specific themable icons (named
icons installed by application outside the system-wide hicolor
directory).
Feel free to edit (by now it's just a draf), implement suggested changes
in your applications and add new subpages listing icons installed by
your application[2] (useful for theme maker people).
Thanks to Rodney Dawes for the original idea[3].
[1] http://live.gnome.org/ThemableAppIcons
[2] http://live.gnome.org/ThemableAppIcons/EpiphanySpecificIcons
[3] http://wayofthemonkey.com/index.php?date=2006-11-15month=11year=2006
Since I've now meet this problem in evince bug
http://bugzilla.gnome.org/show_bug.cgi?id=386226
let me complain about new way too. For other complains one can also read
http://mail.gnome.org/archives/desktop-devel-list/2006-January/msg00302.html
http://mail.gnome.org/archives/desktop-devel-list/2006-February/msg00024.html
http://mail.gnome.org/archives/desktop-devel-list/2006-July/msg00797.html
as Luca kindly mentioned.
Looking at Epiphany specific icons I don't quite understand why download or
bookmark-view
is Epiphany specific icon. Also I don't understand why quite ugly looking icon
for
sidebar should be evince specific.
I dislike the need to install all icons into ${datadir}/hicolor/... and don't
see how it
will improve consistent look of the desktop. I understand that it's hard to
maintain large
set of icons in gnome-icon-theme, but nobody tells maintaince is an easy thing.
So if you'd
like to have small subset, you can just split icon-theme in two packages -
maintained and
unmaintained one.
signature.asc
Description: Эта часть сообщения подписана цифровой подписью
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Application specific themable icons
This got sent before I was finished. Sorry about that. Butterfingers.
On Sat, 2007-01-13 at 20:13 +0300, Nickolay V. Shmyrev wrote:
Since I've now meet this problem in evince bug
http://bugzilla.gnome.org/show_bug.cgi?id=386226
let me complain about new way too. For other complains one can also read
http://mail.gnome.org/archives/desktop-devel-list/2006-January/msg00302.html
http://mail.gnome.org/archives/desktop-devel-list/2006-February/msg00024.html
http://mail.gnome.org/archives/desktop-devel-list/2006-July/msg00797.html
as Luca kindly mentioned.
Looking at Epiphany specific icons I don't quite understand why download or
bookmark-view
is Epiphany specific icon. Also I don't understand why quite ugly looking
icon for
sidebar should be evince specific.
Because these icons are specific to epiphany. We don't have desktop-wide
bookmarks, that integrate all the various types. The bookmarks in
epiphany, are quite different from those in nautilus, which may be
different from those shown in the file chooser. Download I admit, is not
specific to epiphany. In fact, download and save are the same action, and
should not have different icons. However, I'm sure plenty of people will
also disagree with that, hence the reason that epiphany seems to need a
download icon.
I dislike the need to install all icons into ${datadir}/hicolor/... and don't
see how it
will improve consistent look of the desktop. I understand that it's hard to
maintain large
set of icons in gnome-icon-theme, but nobody tells maintaince is an easy
thing. So if you'd
like to have small subset, you can just split icon-theme in two packages -
maintained and
unmaintained one.
So applications will have to depend on the extra package, to even be
functional? I don't think so. Nobody wants that.
-- dobey
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
