fenolftalein wrote:I've tried Python 2.6, but it's very laggy. Active python version (described in wiki) has some minor bugs, such as double song loading, very slow browsing collection (when folder contains 50+ songs, AP version "browse" it more that 30 seconds), "no countdown bug" (song start immediately after loading screen),
building binaries doesn't work
What version are you using? Double song loading has been fixed for a while. Song browsing always took a while, especially if it has to cache the folder (loads much quicker from cache). Never seen the no countdown bug. Fair enough, building binaries is broken for most people's set ups atm.
fenolftalein wrote:PS. +40% FPS compared with normal ActivePython 2.3 installation. RB2 graphic menu is loading two times faster!
ActivePython 2.3? When have we ever used that? (Was that just a typo?)
---- EDIT ----
akedrou wrote:Now on the topic of development. (!) Over at
FoFiX issue 394, I'm working on character select support, so here I have a question for you all (at the issue, or here). I'm of a mind to do the player thing through sqlite, as it's there and I have a personal loathing of INI files. However, this would have the side effect of limiting player portability. Thoughts on this? I suppose the options are
1) Database all the way. INI sucks and people who have friends do too.
2) INI files, because you want to spite me, have hordes of friends at whose houses you play FoFiX, or are informing me of some serious issues I have not considered.
And yes, this is aimed at those of you who know what's up with this sort of thing.
I vote INI, because I want to spite you
Well, not really, but I do have hordes - Nope, can't complete that sentence without bursting into laughter.
I would prefer INIs because you can
see the data that's in them and change it if necessary. If it becomes corrupt for whatever reason, you can fix it. If a database becomes corrupt, you basically lose your profile.
That's my opinion. As a side note, sql would probably be
a lot faster.
---- EDIT ----
I just read through
FoFiX issue 394 and I would like to see option 2 or 3 on that, I think
For those of you who cbf reading the issue, the options are:
1) Database.
2) Database with an import/export feature for INIs.
3) Database, writing to INIs on exit/change/etc.
4) INI files.