info.icon in HAL

[Martin Owens]

The icon is generated by the following logic:

[customer icon] or [hardware icon] or [type icon] or [default icon]

Default icon is a blue cube of sorts, type icons are generic icons per
hardware type (as stored) hardware icon is a named icon (as stored)
and the custom icon is hardware specific icons which are stored (pngs
mostly). all the information is in the hardware profile.

I'm attempting to bridge this information gap between hardware
detection and I'd really like other people to come in with suggestions
and ideas for how things are structured.

If HAL does provide an icon I can simply take that data as the default
hardware icon when a new profile is created.

Best Regards, Martin Owens

On 01/03/07, Richard Hughes <hughsient at gmail.com> wrote:
> On 02/03/07, Martin Owens <doctormo at gmail.com> wrote:
> > hmm, I often have to wonder how much more HAL will attempt to border
> > my project before I simply see all the functionality there.
> >
> > What is HAL for exactly? abstracting functionality of hardware into
> > singular interfaces or simply providing more information about
> > hardware in general? because dohickey.sourceforge.net is based on hal
> > and I'd rather not see the same functionality merged into hal
> > directly; it just doesn't make sense.
> >
> > If you want icon or picture information please work with me on
> > information abstraction.
>
> Sure, but I'm not sure where the functional overlap is occurring?
> Surely you have code in dohicky to work out the icon, and there's also
> similar code in gnome-vfs and I'm guessing KDE also.
>
> By sharing the code and adding the logic to hal-info, we all benefit
> and new hardware is supported painlessly and easily just by updating
> one package.
>
> Richard.
>