Re: Icon Name Standardization, second draft

On Thu, 2005-03-31 at 14:57 -0500, Rodney Dawes wrote:
> Aliasing really belongs in the Icon Theme and MIME Type specifications
> themselves, rather than in the Icon Naming Specification, I think. The
> aliases aren't there to say that something should be named some way.
> They should be meant to allow theme authors to create one image, and
> specify legacy names for that icon, that apps may still use, so that
> we don't have to copy icons around or create symlink farms, to make the
> desktop look proper when using the theme. I will be working on a patch
> to the Icon Theme spec, and to gtk+ as well, for implementation value,
> to do something like Provides=foo,bar for the .icon files.

I didn't realize there were two specs. ;)

> One of the purposes of this spec, is to list all the generic icon names,
> as well as many of the more specific names. However, I am not sure how
> best to distinguish the two, in the docbook source for the spec.

Generic being the designated name and specific being legacy names?  If
that, we could just add a column on that list and name it "Provides
these legacy icons" or something.  Just like you're suggesting to add
to .icon files.

> If this is happening in GNOME, then it is a regression, and you should
> file a bug report. The panel used to have code to strip the extension
> and path off of an icon's filename in the desktop files, for looking up
> in the icon theme. If no icon was found in the theme, it would fall back
> to trying to use the full path as specified in the file. I'm not sure
> what KDE does here, though.

Nope, Xfce here.  That Gnome slickness, though, seems a bit of a

[kde-artists] [Bug 102772] copyrighted icons in kpilot

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.kde.org/show_bug.cgi?id=102772         

------- Additional Comments From groot kde org  2005-04-01 12:36 -------
On Thursday 31 March 2005 10:27, Stephan Binner wrote:
>          AssignedTo|groot kde org               |kde-artists mail kde org
>             Product|kpilot                      |artwork

That's fine, though I'm still totally in the dark as to _which_ icon might be 
copyrighted and if so, why. Unless having two arrows is "Right Out", I just 
don't see the problem (since I drew the original two arrows and had it 
cleaned up by a friend, and then pasted them over the original artwork by 
Frank or Kristof).
______________________________________________________________________________
kde-artists <at> mail.kde.org |  https://mail.kde.org/mailman/listinfo/kde-artists

[kde-artists] [Bug 102772] copyrighted icons in kpilot

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.kde.org/show_bug.cgi?id=102772         

------- Additional Comments From wimer suse de  2005-04-01 17:58 -------
because this is not a part of their logo and is simply the same motive for a visual metaphor I seriously doubt
that this is a problem
______________________________________________________________________________
kde-artists <at> mail.kde.org |  https://mail.kde.org/mailman/listinfo/kde-artists

Re: Icon Name Standardization, second draft

On Thu, 2005-03-31 at 21:01 -0500, Andrew Conkling wrote:
> On Thu, 2005-03-31 at 14:57 -0500, Rodney Dawes wrote:
> > Aliasing really belongs in the Icon Theme and MIME Type specifications
> > themselves, rather than in the Icon Naming Specification, I think. The
> > aliases aren't there to say that something should be named some way.
> > They should be meant to allow theme authors to create one image, and
> > specify legacy names for that icon, that apps may still use, so that
> > we don't have to copy icons around or create symlink farms, to make the
> > desktop look proper when using the theme. I will be working on a patch
> > to the Icon Theme spec, and to gtk+ as well, for implementation value,
> > to do something like Provides=foo,bar for the .icon files.
> 
> I didn't realize there were two specs. ;)

There are multiple specs. I believe the Shared MIME Info spec takes care
of allowing aliases for MIME type definitions. The Icon Theme spec needs
something similar for icons.

> > One of the purposes of this spec, is to list all the generic icon names,
> > as well as many of the more specific names. However, I am not sure how
> > best to distinguish the two, in the docbook source for the spec.
> 
> Generic being the designated name and specific being legacy names?  If
> that, we could just add a column on that list and name it "Provides
> these legacy icons" or something.  Just like you're suggesting to add
> to .icon files.

No. Generic is the generic name, and specific is the specific name. For
instance, "printer-remote" is generic, while "printer-remote-smb" is
more specific. "printer-remote-smb-hp" would be even more specific.

e: [kde-artists] Recent crystalsvg and some older changes

> in nearly every review of KDE, people complain that KDE is much to 
colourfull, teletubby like and childish.

I guess either you're reading different reviews than those I read, or you're 
confusing winders XP ones with kde ones. I read more and more reviews 
claiming kde is becoming more proffessional the further it goes on the 3.x 
releases. But ... ermm.. I don't know why. They never mention icons!

> We try to make KDE look more professional and  
> decent.

Now again you're confusing professionalism with ugliness. A professional theme 
for me is one that got a uniform look in all the icons. A professional theme 
for me is one that got the whole theme complete, not mixed from other 
different-styled themes.  A professional theme for me is one that all icons 
are comprehensible and got an easy meaning. A professional theme is one that 
makes it easy to recognise an icon at first sight.

That got nothing to do with colour.. well wrong. Colours help reading the icon 
quicker at first sight. Colours allow making complex icons more readable ( a 
huge  grayscale svg icon reduced to 16x16 is usually unreadable until you 
help it a bit with colours). And correct me here if I'm wrong, but if one 
person got sight problems (say you left your glasses at home and you're far 
from the monitor), you can easier recognise a RED icon from a BLUE icon than 
two black icons.

> This is needed if we want to attract more corporate users.  

What you need to do to attract corporate users is making icons comprehensible. 

Re: [kde-artists] Recent crystalsvg and some older changes

qwertz wrote:

> Yesterday i saw that new action icons were comitted to the kde cvs.
> They resemble the pre KDE 1.0  icons:)
> Most are B/W some are grey.
> Again the function of color is lost.
> Most users these days have 16bit capable graphic cards.
> We should use them.

Which icons, specifically?

--

-- 
JRT

______________________________________________________________________________
kde-artists <at> mail.kde.org |  https://mail.kde.org/mailman/listinfo/kde-artists

Re: [kde-artists] Recent crystalsvg and some older changes

Frank Karlitschek wrote:
> Hi,
> 
> in nearly every review of KDE, people complain that KDE is much to colourfull, 
> teletubby like and childish. We try to make KDE look more professional and 
> decent. This is needed if we want to attract more corporate users. 

IMHO, corporate users and users that want something 'way cool' are never 
going to be able to agree.  Therefore, I feel that we need to continue 
to have full support of HiColor/KDEClassic for those that value 
usability over the coolness factor.

> We keep the colorfull crystal look for most of the icons. But the action icons 
> and especially the 16x16 ones in the menus should be a bit more unobtrusive 
> and simpler. I don't think that we need 16 million colors in 16x16 pixels for 
> a good looking desktop.

 From a technical point: when you make an icon small enough to the point 
that more than two very different colors are combined into one pixel, 
you have problems.  This is why some Crystal icons turn into fuzzy 
colored blobs in the small (16x16 & 22x22) sizes.  The only cure for 
this is simpler and more graphical icons.

--

-- 
JRT
______________________________________________________________________________
kde-artists <at> mail.kde.org |  https://mail.kde.org/mailman/listinfo/kde-artists

[kde-artists] Vector version of link overlay

Hello KDE Artists,
I read on your Wiki page, that you need a vectorized version of the Link 
Overlay, so I created one. If you like it, feel free to use it, or modify it.

Greetings,
--

-- 
Marcel Dierkes
marcel.dierkes <at> gmail.com

______________________________________________________________________________
kde-artists <at> mail.kde.org |  https://mail.kde.org/mailman/listinfo/kde-artists

kdelibs/pics/crystalsvg

CVS commit by karli: 

fix.Thanx Greg

  M            cr16-action-forward.png   1.9

[kde-artists] [Bug 103059] Using new tab icons

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.kde.org/show_bug.cgi?id=103059         
christian.loose hamburg de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|faure kde org               |kde-artists mail kde org
______________________________________________________________________________
kde-artists <at> mail.kde.org |  https://mail.kde.org/mailman/listinfo/kde-artists