[Qgis-psc] How do we handle icon discussions?
Tim Sutton
tim at linfiniti.com
Sun Feb 23 10:22:05 PST 2014
Hi
On Sun, Feb 23, 2014 at 1:36 PM, Anita Graser <anitagraser at gmx.at> wrote:
> Am 19.02.2014, 09:55 Uhr, schrieb Otto Dassau <dassau at gbd-consult.de>:
>
>
> Hi,
>>
>> Am Tue, 18 Feb 2014 18:54:20 +0100
>> schrieb "Anita Graser" <anitagraser at gmx.at>:
>>
>> Hi PSC,
>>>
>>> This mail is motivated by the following discussion:
>>> https://github.com/qgis/QGIS/pull/1146#issuecomment-35365231
>>>
>>> I think it is necessary to put down some instructions how to approach
>>> icon changes. In my opinion, this is not only a matter of taste,and
>>> whether the suggested icons are better than the old ones, but also an
>>> issue for the documentation team (workload) and users (recognizing
>>> changed
>>> icons, interface different from documentation).
>>>
>>> Do you want to discuss this issue on the list or during an IRC meeting? I
>>> would appreciate feedback especially from those involved in documentation
>>> and training.
>>>
>>> Best wishes,
>>> Anita
>>>
>>
>> In my opinion icon changes are no problem and should be handled like this:
>>
>> * keep the same name as the version before (if you want to backup the old
>> one, name it xxx_backup, maybe with a version number as well
>> xxx_backup2.0).
>> * create a png version from the original svg in the relevant folder
>>
>> Then we can once before a new release copy/update all icons as *.png into
>> the documentation, ... repos and everything should be fine again.
>>
>> Did I miss something?
>>
>
>
> Tim, would you like to add your opinion to this discussion since you
> brought it up in the Github issue?
>
>
Thanks Anita and Otto. My concern in the original thread was mainly
relating to trivial updates to icons invalidating training materials and
other resources out there. We would like to invest more time and effort
into training materials for QGIS but its not so nice if as soon as you
write them a new version of QGIS comes out with different icons making all
the screenshots invalid. Same goes for people writing books etc. about
QGIS. My thinking was that we should adopt some kind of policy whereby we
accept new icons for new tools in minor releases but collect general icon
tweaks and improvements together for e.g. major releases. That way we we
limit the amount of brain retraining that has to happen between each minor
version for users, and reduce the amount of churn that documentation
related to QGIS needs to undergo with each release.
Regards
Tim
> Thanks and best wishes,
> Anita
>
>
>
> --
> anitagraser.com
>
--
Tim Sutton
-------------------------------------------------------------------------------------------
Visit http://linfiniti.com to find out about:
* QGIS programming services
* GeoDjango web development
* QGIS Training
* FOSS Consulting Services
Skype: timlinux Irc: timlinux on #qgis at freenode.net
Tim is a member of the QGIS Project Steering Committee
-------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20140223/3c200a06/attachment.html>
More information about the Qgis-psc
mailing list