Re: [Tuxmath-devel] Further performance improvement with more caching mechanisms

[Tim H. <ho...@wu...>]

Hi Wenyuan,

On Friday, July 23, 2010 07:31:56 pm Wenyuan Guo wrote:
> Tim: should I move onto PNG -> SVG conversion phase, now that we have
> achieved most of our objectives of program optimization? It might be
> interesting to see what problems may occur as more images are in SVG.
> What is your opinion?

I agree that this is probably the best thing to do now. Certainly it seems 
likely that loading times will increase as you have more images. If that 
becomes problematic, one obvious solution would be to defer loading of images 
that are not needed immediately (e.g., menu items only when you need them, 
comets game images only when you need them, etc.). But assuming that's not 
already implemented, it seems sensible to first try the straightforward "just 
load everything" and see how long it takes; if it's too long, then deal with 
the issues when you can profile and see where the bottlenecks are.

Exciting!
--Tim

> 
> Cheers
> Wenyuan
> 
> On Fri, Jul 23, 2010 at 9:06 AM, David Bruce <dav...@gm...> 
wrote:
> > Hi,
> > 
> >> Has anyone else tried the new program? Any feedback is most welcome!
> > 
> > I built it just now on my home desktop and it works great.  I also
> > built and ran it on a Dell Mini 9 (a much slower machine), and also
> > had excellent results.  The first execution has a few seconds of
> > delay, but after that the program responds quite quickly both at
> > startup and change of resolution.
> > 
> > Hooray!
> > 
> > On a completely unrelated note, I noticed one build pitfall that is
> > triggered if the same build directory is used for a CMake build and
> > then an autotools build - CMake puts config.h under src, whereas
> > autoheader puts config.h directly into the build directory.  The
> > problem is that they don't create  equivalent files, and the CMake
> > version shows up first in the include path, so a subsequent autotools
> > build doesn't find the correct config.h.  This leads to an compile
> > error the first time something from config.h is needed, in this case
> > PACKAGE.
> > 
> > The moral of the story is that when testing both build systems, keep
> > each in its own build directory.
> > 
> > David