Mailinglist Archive: zypp-devel (70 mails)
| < Previous | Next > |
[zypp-devel] Icons for the package selector
- From: Ricardo Cruz <rpmcruz@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 14 Oct 2007 21:03:53 +0100
- Message-id: <1192392233.4114.7.camel@xxxxxxxxxxxx>
Hi,
Do you guys want to comment on this? (icons for the package selector:
http://sukimashita.com/temp/yast2-gtk-package-selector-1.gif ;)
Please CC to opensuse-gnome@xxxxxxxxxxxx
Thanks,
Ricardo
On Fri, 2007-10-12 at 15:45 +0100, Ricardo Cruz wrote:
> The mockup looks great, thanks. Christian Jäger also suggested the
use
> of icons. However, I am afraid we can only hack that for installed
> software.
> Zypp downloads a file from the repos that has some informations about
> the packages (names, descriptions, ...), but it doesn't have an
inlined
> icon -- it doesn't even have all the RPM header info. We would need to
> download the entire package to extract that information.
> What we can do, for the available packages, is to use the icon of the
> group they belong to. E.g. for bombermaze, I guess the games/action.
>
# I could imagine a stacked icon retrieval algo.; top to bottom:
- Use the "icon" property supplied by package tag from zypper/metadata
(described below)
- Use GNOME icon lookup interface with specific package name
- Package Category's icon (Icon naming spec gives us appropriate icons)
- Use generic icon for application/x-rpm
Of course the biggest challenge are icons for not installed packages.
An idea to solve this...
# Get icon metadata from packager up to the software stack:
- .spec files allow "Icon:" tags, let's put them to use to specify an
icon name for a package
- Generated repository metadata gets "icon" attribute which is read from
the .spec file
- Zypper gets "icon" attribute support in the API
- Packagemanager is able to use/read the "icon" information (which now
comes all the way from the .spec file) and use it in the icon lookup
process
While this would add the ability for packagers to specify an "Icon:" tag
with a name according to the icon naming spec and thus at least already
gain a good set of icons to use, it still would not work for completely
custom icons.
# External icons
Here, we would require to get those from some place in the internets.
I think one solution would be to extend the "Icon:" tag to be able to
specify names, filenames and URLs so the build process might pull the
appropriate images into the final repository (probably the repodata/ or
src/ directory renamed according to the package).
If the icons are put in some directory in the repository they could be
accessible from the createrepo generated html pages, from within the
build service's package listings or even some supergeeky AJAX frontend
(oh, like http://software.opensuse.org/search/)
Again, just an idea and for sure needs a final specification to become
reality.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Do you guys want to comment on this? (icons for the package selector:
http://sukimashita.com/temp/yast2-gtk-package-selector-1.gif ;)
Please CC to opensuse-gnome@xxxxxxxxxxxx
Thanks,
Ricardo
On Fri, 2007-10-12 at 15:45 +0100, Ricardo Cruz wrote:
> The mockup looks great, thanks. Christian Jäger also suggested the
use
> of icons. However, I am afraid we can only hack that for installed
> software.
> Zypp downloads a file from the repos that has some informations about
> the packages (names, descriptions, ...), but it doesn't have an
inlined
> icon -- it doesn't even have all the RPM header info. We would need to
> download the entire package to extract that information.
> What we can do, for the available packages, is to use the icon of the
> group they belong to. E.g. for bombermaze, I guess the games/action.
>
# I could imagine a stacked icon retrieval algo.; top to bottom:
- Use the "icon" property supplied by package tag from zypper/metadata
(described below)
- Use GNOME icon lookup interface with specific package name
- Package Category's icon (Icon naming spec gives us appropriate icons)
- Use generic icon for application/x-rpm
Of course the biggest challenge are icons for not installed packages.
An idea to solve this...
# Get icon metadata from packager up to the software stack:
- .spec files allow "Icon:" tags, let's put them to use to specify an
icon name for a package
- Generated repository metadata gets "icon" attribute which is read from
the .spec file
- Zypper gets "icon" attribute support in the API
- Packagemanager is able to use/read the "icon" information (which now
comes all the way from the .spec file) and use it in the icon lookup
process
While this would add the ability for packagers to specify an "Icon:" tag
with a name according to the icon naming spec and thus at least already
gain a good set of icons to use, it still would not work for completely
custom icons.
# External icons
Here, we would require to get those from some place in the internets.
I think one solution would be to extend the "Icon:" tag to be able to
specify names, filenames and URLs so the build process might pull the
appropriate images into the final repository (probably the repodata/ or
src/ directory renamed according to the package).
If the icons are put in some directory in the repository they could be
accessible from the createrepo generated html pages, from within the
build service's package listings or even some supergeeky AJAX frontend
(oh, like http://software.opensuse.org/search/)
Again, just an idea and for sure needs a final specification to become
reality.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |