On Mon, Nov 22, 2010 at 06:37:31PM +0200, Eino Keskitalo wrote:
> > (These are optimizations of built packages, not of source.)
> 
> I didn't understand what this meant.

We have two different sets of images:
* the generated combined textures
  These don't even exist in git or source packages, are generated based on
  source tiles, and it's them (and only them, plus title*.png) which are
  shipped in binary packages.
  My optimization here reduces their size, making the downloads smaller.

* source images
  They are what we store and what tile artists edit.  They live in git and
  source tarballs but don't get shipped in compiled form.
  We can optimize them -- heck, even using all brute force aggressive
  optimizations that take a long time since it's done only once, however I
  wonder if that is a good idea since that would increase the size of our
  git trees (as git would have to store both the old and new versions unless
  we rewrite history).
  Since hardly anyone uses source tarballs anymore and we use git
  extensively, I didn't do that, at least not yet.

Of course, when you add new tiles, it's a good idea to optimize them before
committing.  From this research, I see that currently the best way
(generally) is to use both optipng and advancecomp, in this order:

optipng kitty.png
advpng -z -4 kitty.png

This does not decrease the quality, nor doesn't make decoding the images any
slower.

-- 
1KB             // Microsoft corollary to Hanlon's razor:
                //      Never attribute to stupidity what can be
                //      adequately explained by malice.

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Crawl-ref-discuss mailing list
Crawl-ref-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/crawl-ref-discuss

Reply via email to