On 20 Mar 2010, at 19:22, Matthew Tylee Atkinson wrote: > Not that I can see -- please could you send me the shareware version you > have, just so I have a copy?
Just to clarify: by "not that I can see" I meant there is not a problem as far as I can see. As long as you don't modify the .pak files during install. I suppose strictly you shouldn't really be modifying the id Software-provided media, but everyone does this and nobody minds because (a) we're not ripping id software off -- we're just re-packaging stuff they made available and (b) I very-much doubt id Software would mind if it knew what we were doing. Just a note about contributing any code: please bear in mind that the audioquake project on Launchpad is designed to be cross-platform so try to avoid changing any code that could break stuff on another platform. For example: removing or modifying much in the engine or relating to the Windows install files will not necessarily cause problems for Mac users, but could stop Windows users from being able to compile and run the program. It would be great if people were able to contribute stuff they're doing back to the launchpad project as this provides a central repository for all of our work. I had always intended to make documentation that explained how it works and make the process easy but of course life got in the way. However if anyone does want to contribute, particularly to the install/build process, then I would be happy to explain how it works if the current docs are out-of-date (which I assume they are :-)). Currently it does rely on having a Linux/Mac box to build the mod and package it -- even for Windows, where a zip file is made that contains an installer script which can then be moved to a Windows box and compiled with Inno Setup into a setup.exe file on Windows. Finally: the documentation is still available (including developer docs) but only the stuff that's generated from the QuakeC library code is likely to be up-to-date -- if anyone wants to learn how to build and host up-to-date documentation that'd be great as it could ease the task for new developers of learning what's what. But let's take one step at a time :-). It is fantastic that you're all willing to pitch in and I hope that any changes I make to the site or whatever will be good for allowing the community to move on more autonomously (that's certainly the intent). best regards, -- Matthew Tylee Atkinson http://mta.agrip.org.uk/ _______________________________________________ AGRIP-discuss mailing list [email protected] http://lists.agrip.org.uk/mailman/listinfo/agrip-discuss
