Re: [Tuxpaint-dev] the *.txt files
Albert Cahalan [EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]: First of all, in the CVS, could we keep translations out of the *.txt files? They can be added at build time. No, that would an enormous dependency (Python) on all platforms + making the build much slower. There's no need to keep checking in redundant data, bloating up the CVS records with noise. Come on, there are just a few commit messages (I don't know why CVS splits the commit at all), and I *usually* only generate them before each release, i.e. about once a year (or if translators ask for it). Second of all, important comments are disappearing. I don't know if this is intentional, but it sucks. It's not intentional, and it sucks, but at least all the information is available in CVS (and some of it in the changelog file) if you need it. -- Karl Ove Hufthammer ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] the *.dat files
Albert Cahalan [EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]: How about merging these into the *.txt files? I think it would only make things (extracting, merging and manually editing the files) more complicated and error-prone. Disk reads and space is cheap, especially now with the new threaded stamp-loading code. If you really want to reduce disk reads, creating some sort of internal stamp description cache file, and only checking last modification times when loading stamps may be a better solution (but still unnecessary, IMHO). -- Karl Ove Hufthammer ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] the *.txt files
On Tue, 2005-01-25 at 19:02 +0100, Karl Ove Hufthammer wrote: Albert Cahalan [EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]: First of all, in the CVS, could we keep translations out of the *.txt files? They can be added at build time. No, that would an enormous dependency (Python) on all platforms + making the build much slower. Well, how about just using gettext() then? That's the way the whole rest of Tux Paint operates. ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] the *.dat files
On Tue, 2005-01-25 at 19:08 +0100, Karl Ove Hufthammer wrote: Albert Cahalan [EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]: How about merging these into the *.txt files? I think it would only make things (extracting, merging and manually editing the files) more complicated and error-prone. Disk reads and space is cheap, especially now with the new threaded stamp-loading code. The funny thing about disk reads is that bulk reads are cheap, while tiny reads are costly. The disk might go at 100 MB/s, but every seek will cost you 5 ms. BTW, how does Tux Paint from CVS work for you? Font scanning is now done in a separate process. For filling in the tool option buttons and for the selected item, both fonts and stamps are loaded on demand by the main thread. If you really want to reduce disk reads, creating some sort of internal stamp description cache file, and only checking last modification times when loading stamps may be a better solution (but still unnecessary, IMHO). I've thought of doing that. It has another huge gain: stamp scaling need not be done if thumbnails are cached. ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
