On 9/7/07, James Paige <[EMAIL PROTECTED]> wrote: > On Fri, Sep 07, 2007 at 03:39:41AM +1200, Ralph Versteegen wrote: > > On 9/6/07, James Paige <[EMAIL PROTECTED]> wrote: > > > On Thu, Sep 06, 2007 at 09:10:02AM +0930, David Gowers wrote: > > > > On 9/6/07, James Paige <[EMAIL PROTECTED]> wrote: > > > > > On Wed, Sep 05, 2007 at 08:15:48AM -0700, James Paige wrote: > > > > > > On Wed, Sep 05, 2007 at 07:57:27PM +1200, Ralph Versteegen wrote: > > > > > > > James! James! You forgot plotdictionary.html! I really hope you > > > > > > > don't > > > > > > > try to justify using the wiki instead. It's just not convenient! > > > > > > > The > > > > > > > html file has related commands documentated sequentially, normally > > > > > > > assuming that you don't need cross links to find relevant commands > > > > > > > documented one paragraph down the page. > > > > > > > > > > > > I see the value in having the all-in-one file, but I don't see the > > > > > > advantage of actually including the file. How about if I ad a URL > > > > > > shortcut that points to > > > > > > http://hamsterrepublic.com/ohrrpgce/docs/plotdict.xml > > > > > > > > > > ... actually, I just realized why I still need to include > > > > > plotdictionary.html ... because a lot of people will be installing > > > > > right > > > > > over a previous installation, and if their old plotdict.html doesn't > > > > > get > > > > > overwritten with a new one, they will be wondering why they cant find > > > > > the docs for the new commands (or they won't even know the new > > > > > commands > > > > > exist at all) > > > > > > > > Then why don't you just make plotdict.html contain a single link to > > > > http://hamsterrepublic.com/ohrrpgce/docs/plotdict.xml, plus some blurb > > > > about new location? > > > > > > generating plotdictionary.html from plotdict.xml is pretty easy, and > > > keeping plotdictionary.html is a courtesy to those who are masochistic > > > enough to keep using hssed :) > > > > > > --- > > > James Paige > > > > On my computer it takes about 15 seconds to render plotdict.xml, but I > > still prefer it to the wiki. > > The html version will compress down to only a few kB. I don't see any > > good reason to leave it out even if people didn't have old copies > > lying around. The full package and installers are meant to include > > everything you need to make a game, and plotscripting documentation is > > definitely part of that. > > The slowness of plotdict.xml is a good point. it takes about 12 seconds > on my very-fast work computer. > > > (Also, I still use Hssed, but I don't normally use its help function) > > Funny, that was the only feature of HssEd that I missed when I started > doing my plotscripting in SciTE > > > Actually, what exactly is the aim of the minimalist .zip? > > A not insignifigant contingent of OHR users genuinely wants to put the > zip on a floppy to take it home. Remember that the OHR is a low-system > requirement program, that makes it attractive to people who still use > floppies for things. > > Of course, feedback on the floppy release of ubersetzung will detemine > whether or not we keep doing it in Voxhumana. > > > It doesn't > > include the necessities for scripting, and the only way to get them is > > by getting the full distribution, OR a nightly and an HSpeak nightly > > at the point Ubersetzung was released. A nightly HSpeak after the > > release may not be compatible. It's sort of more of a ohrrpgce_play > > with Custom thrown in for examining games. > > Ack! How the heck did I forget hspeak? No wonder I had room for > madplay+oggenc :( > Good news! We forgot UPX!
After running game and custom through UPX on brute force strength (eclipsed only by the ULTRA-BRUTE setting in terms of CPU wastage) I managed add madplay, oggenc, plotdictionary.html and whatsnew.txt into the floppy package with just 37kb of floppy space to spare. Yes, it takes several minutes to compress each of game and custom, but we're only doing it once. Why did you leave whatsnew.txt out anyway? Forgot again? The commands: (should we add upx.exe to /support?) upx --brute game.exe upx --brute custom.exe (If we were really desperate to squeeze out extra kB, we could decompress oggenc, madplay and hspeak and recompress them at brute force strength (which tries 36 compression settings), and do SDL_mixer.dll too (compressed dll's can't be shared between programs using the same dll, but this shouldn't be too big a problem for our custom build) We could run nightly builds of game and custom through UPX at --best setting too: this shaves about 100kb off the zips, and only takes a couple seconds. TMC _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
