Re: Request for UI break in Yelp

On Tue, 2007-09-04 at 21:44 +0200, Andre Klapper wrote:
> ahoj don,
> Am Dienstag, den 04.09.2007, 19:53 +0100 schrieb Don Scorgie:
> > We've had a request to update the icon used in the background of the TOC
> > in yelp to use a tango-ified version of the same [1].
> > 
> > This is a request to break the UI freeze and introduce this icon.  The
> > plan is to do a straight replacement and keep virtually all code the
> > same.
> >
> > This only affects the background image on the TOC (left side, behind the
> > list of categories) and does not affect any other icons / images.
> > The tango-ified icon looks very similar to the current icon and without
> > me pointing it out, (probably) no-one would notice ;)
> > 
> > I don't believe this affects any screenshots or anything outside of the
> > app.
> is a screenshot. :)
> this is a tentative "1 of 2" r-t approval, if the code changes are
> really trivial,

No code change is involved.  It's just replacing one PNG
file with another.

>  and (more important): if you get an OK from the
> documentation team, because several screenshots (according to svn trunk,
> el, es, fi, fr, sv and zh_CN include a localized screenshot of the
> image) need to be updated.
> > [1]

I guess there's a conflict of interest here, given that I'm:

1) the guy who generally gives documentation team approval, and
2) one of the maintainers of Yelp.

But heck, I trust me.  And since I'm the documentation team
leader, I trust my judgment in trusting me.  Apply circular
reasoning ad nauseum. ;)

Seriously, the affected screenshots are different from SVN
trunk in much more serious ways than a stylistic change to
an icon (e.g. they lack a search field in the toolbar.)

Like Deadpool, I liked numbered lists:

1) The screenshots need to be retaken anyway.
2) Non-metaphor-changing icon updates don't cause confusion.
3) If they do cause confusion, popular distros using different
   default themes are a much more serious problem than a purely
   decorative graphic.

So, the documentation team says OK to itself.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]