Re: [Warzone-dev] Approaching Version 2.0.6
i have just about completed the updating of the manual... a few more pages to do... as soon as i have completed them i will delete the old file and upload the new one. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
will be plain ordinary html ( through ms frontpage - version 2003) in a zip file. will be approximately 75mb... give or take a few mb. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
Am Donnerstag, 15. Februar 2007 schrieb Christian Ohm: On Monday, 12 February 2007 at 23:50, Dennis Schridde wrote: In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Any hints on that? Delaying the release for a bug you don't have any idea on how to tackle seems a bit pointless... (same as some of the others you listed). Anyway, I'd like to improve the current documentation a bit (inspired by the long comment at http://happypenguin.org/show?Warzone%202100), that might take some time, so if the release is delayed for a bit that could be added as well. Any progress on this? --Dennis pgpNSOinD54Hh.pgp Description: PGP signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
Dennis Schridde schreef: Am Donnerstag, 15. Februar 2007 schrieb Christian Ohm: On Monday, 12 February 2007 at 23:50, Dennis Schridde wrote: In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Any hints on that? Delaying the release for a bug you don't have any idea on how to tackle seems a bit pointless... (same as some of the others you listed). Anyway, I'd like to improve the current documentation a bit (inspired by the long comment at http://happypenguin.org/show?Warzone%202100), that might take some time, so if the release is delayed for a bit that could be added as well. Any progress on this? Not by me. I've tried looking into this but haven't ever been able to reproduce this. Which makes me start to wonder whether this issue actually is real. As for the Radeon issues. As long as no one capable of working on the Warzone code has a Radeon video device (the one's mentioned in the bugreport of course) I think we shouldn't wait for that either. Personally I'd say we should release 2.0.6 within a week at max from now (that is while looking at the current situation of course). -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
Am Samstag, 17. Februar 2007 schrieb kim metcalfe: ok here is the latest stats on the documents project... and as the WZ2100R project goes along - it will be added to. you have a mailbox you want it sent to - or can i upload to a site using ftp. Kamaze: Can you setup a FTP account for Kim, so he can upload that file onto the server? Otherwise send it to dschridde ... gmail ... com --Dennis pgp09tbg2v8pv.pgp Description: PGP signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
About the documentation, why not create a subfolder like www.wz2100.net/docs/, it is absolutly no problem to give kim (for example) access to this. Maybe we can integrate or port it some day into the wiki. (Integrating them as pure HTML code -we tried that- will break the HTML code and make xss attacks easily possible, so don't ask for that :)) Oh, because we talking about the wiki: i'll play around with MediWiki this weekend. To replace dokuwiki. It looks like the most people are more familar with the MediaWiki software/syntax. But it is a bit difficult to integrate the forums-accounts as wiki-accounts. And i'll will register at ModDB these days, and try to add WZR again :) - Kamaze Dennis Schridde schrieb: Am Donnerstag, 15. Februar 2007 schrieb Christian Ohm: On Monday, 12 February 2007 at 23:50, Dennis Schridde wrote: In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Any hints on that? Delaying the release for a bug you don't have any idea on how to tackle seems a bit pointless... (same as some of the others you listed). Anyway, I'd like to improve the current documentation a bit (inspired by the long comment at http://happypenguin.org/show?Warzone%202100), that might take some time, so if the release is delayed for a bit that could be added as well. Oh, and how about a release candidate for 2.0.6? Not as see if anyone finds some bugs in it, that can be done by the release as well. But add the return TRUE to disable videos, and ask people to especially report any problems related to that (so perhaps its more a test release than a release candidate - just a name, anyway). That'll have the effect of delaying the release a bit as well, and gives people something to play with in the meantime. (some time later) Ah, well, I don't want to rewrite all that, I'll look some more into the video issue, so take the previous paragraph with a grain of salt. And finally, the release checklist is missing run ./autogen.sh to create the build system for the source tarball, and happypenguin.org to announce the release on (any other interesting sites?). Excellent game, shame about the documentation and not having one central Warzone 2100 online resource. I just found out that I did not include the README in the Linux package. It is not even installed by default... And he is absolutely right... If someone not knowing anything about Warzone comes along the way, he will be totally lost... And as he mentioned what I experienced earlier: Kim, could you send me the raw HTML files (NOT compiled into a .chm)? --Dennis PS: (About 3 hours after I wrote the part above) The README, COPYING, etc. files are now installed by default on Linux. The AutoPackage and NSIS installer will also contain them. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
On Monday, 12 February 2007 at 23:50, Dennis Schridde wrote: In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Any hints on that? Delaying the release for a bug you don't have any idea on how to tackle seems a bit pointless... (same as some of the others you listed). Anyway, I'd like to improve the current documentation a bit (inspired by the long comment at http://happypenguin.org/show?Warzone%202100), that might take some time, so if the release is delayed for a bit that could be added as well. Oh, and how about a release candidate for 2.0.6? Not as see if anyone finds some bugs in it, that can be done by the release as well. But add the return TRUE to disable videos, and ask people to especially report any problems related to that (so perhaps its more a test release than a release candidate - just a name, anyway). That'll have the effect of delaying the release a bit as well, and gives people something to play with in the meantime. (some time later) Ah, well, I don't want to rewrite all that, I'll look some more into the video issue, so take the previous paragraph with a grain of salt. And finally, the release checklist is missing run ./autogen.sh to create the build system for the source tarball, and happypenguin.org to announce the release on (any other interesting sites?). -- Labor, n.: One of the processes by which A acquires property for B. -- Ambrose Bierce, The Devil's Dictionary ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
On 2/15/07, Giel van Schijndel [EMAIL PROTECTED] wrote: On Thu, 15 Feb 2007 12:27:27 +0100, Christian Ohm [EMAIL PROTECTED] wrote: On Monday, 12 February 2007 at 23:50, Dennis Schridde wrote: In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Any hints on that? Delaying the release for a bug you don't have any idea on how to tackle seems a bit pointless... (same as some of the others you listed). Anyway, I'd like to improve the current documentation a bit (inspired by the long comment at http://happypenguin.org/show?Warzone%202100), that might take some time, so if the release is delayed for a bit that could be added as well. Oh, and how about a release candidate for 2.0.6? Not as see if anyone finds some bugs in it, that can be done by the release as well. But add the return TRUE to disable videos, and ask people to especially report any problems related to that (so perhaps its more a test release than a release candidate - just a name, anyway). That'll have the effect of delaying the release a bit as well, and gives people something to play with in the meantime. (some time later) Ah, well, I don't want to rewrite all that, I'll look some more into the video issue, so take the previous paragraph with a grain of salt. And finally, the release checklist is missing run ./autogen.sh to create the build system for the source tarball, and happypenguin.org to announce the release on (any other interesting sites?). Well, tweakers.net would be the place where I'd submit an entry for the new release to the so called meuktracker (they usually only place full releases though, not release candidates). As for the autgen.sh thingy I think that one is not included in the list because its results (i.e. the build system) should not be commited into the Subversion repository. -- Giel that empty config bug is mingw related,it's a potential bug in those static linked .a library or a bug of windows.But it's very hard to reproduce/pinpoint the problem,since the bug only happens with certain version of system dlls and certain version of windows. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
Dennis Schridde schreef: Am Donnerstag, 15. Februar 2007 schrieb The Watermelon: that empty config bug is mingw related,it's a potential bug in those static linked .a library or a bug of windows.But it's very hard to reproduce/pinpoint the problem,since the bug only happens with certain version of system dlls and certain version of windows. So this is a bug in MinGWs implementation of strlen??? I would have guess that MinGW uses the strlen implementation provided by MS in their C runtime... Is it even strlen that is at fault there? @Watermelon: could you please elaborate as to _what_ bug causes the empty config file problem. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
Am Donnerstag, 15. Februar 2007 schrieb Giel van Schijndel: Dennis Schridde schreef: Am Donnerstag, 15. Februar 2007 schrieb The Watermelon: that empty config bug is mingw related,it's a potential bug in those static linked .a library or a bug of windows.But it's very hard to reproduce/pinpoint the problem,since the bug only happens with certain version of system dlls and certain version of windows. So this is a bug in MinGWs implementation of strlen??? I would have guess that MinGW uses the strlen implementation provided by MS in their C runtime... Is it even strlen that is at fault there? I am 99% sure. The logfiles I saw all state that We are to write (config) of size 0. Code is in lib/framework/frame.c:497 : debug(LOG_WZ, We are to write (%s) of size %d, pFileName, fileSize); fileSize is int count from lib/framework/configfile.c:238, calculated using strlen on line 250. @Watermelon: could you please elaborate as to _what_ bug causes the empty config file problem. pgpsfVt34EApS.pgp Description: PGP signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
On 2/15/07, Giel van Schijndel [EMAIL PROTECTED] wrote: Dennis Schridde schreef: Am Donnerstag, 15. Februar 2007 schrieb The Watermelon: that empty config bug is mingw related,it's a potential bug in those static linked .a library or a bug of windows.But it's very hard to reproduce/pinpoint the problem,since the bug only happens with certain version of system dlls and certain version of windows. So this is a bug in MinGWs implementation of strlen??? I would have guess that MinGW uses the strlen implementation provided by MS in their C runtime... Is it even strlen that is at fault there? @Watermelon: could you please elaborate as to _what_ bug causes the empty config file problem. -- Giel I am not sure what exactly the problem is,though it seems devurandom already found the bug. =) ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
Am Donnerstag, 15. Februar 2007 schrieb The Watermelon: On 2/15/07, Giel van Schijndel [EMAIL PROTECTED] wrote: Dennis Schridde schreef: Am Donnerstag, 15. Februar 2007 schrieb The Watermelon: that empty config bug is mingw related,it's a potential bug in those static linked .a library or a bug of windows.But it's very hard to reproduce/pinpoint the problem,since the bug only happens with certain version of system dlls and certain version of windows. So this is a bug in MinGWs implementation of strlen??? I would have guess that MinGW uses the strlen implementation provided by MS in their C runtime... Is it even strlen that is at fault there? @Watermelon: could you please elaborate as to _what_ bug causes the empty config file problem. -- Giel I am not sure what exactly the problem is,though it seems devurandom already found the bug. =) I don't think that the MinGW implementation of strlen is broken for several reasons: They can simply use the MS implementation. strlen is really not difficult to implement. It is a very commonly used function, so unlikely that there will be an undetected bug. pgpvOQCx5xTon.pgp Description: PGP signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
On 2/12/07, Dennis Schridde [EMAIL PROTECTED] wrote: Hi! In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Does anyone else have some bugs he wants to be fixed in 2.0.6 or bugfixes he thinks need to be ported from trunk? Otherwise I would release 2.0.6 as soon as I fixed the above mentioned problem. --Dennis Possible show-stoppers for 2.0.6: https://gna.org/bugs/index.php?8202 https://gna.org/bugs/index.php?8144 https://gna.org/bugs/index.php?8090 https://gna.org/bugs/index.php?7317 I'd like to see what bug #8454 turns out to be, if possible, but it's not a real showstopper to my knowledge since 2.0.x seems playable and savable/loadable on the Mac to date. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
Am Dienstag, 13. Februar 2007 schrieb Ari Johnson: On 2/12/07, Dennis Schridde [EMAIL PROTECTED] wrote: Hi! In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Does anyone else have some bugs he wants to be fixed in 2.0.6 or bugfixes he thinks need to be ported from trunk? Otherwise I would release 2.0.6 as soon as I fixed the above mentioned problem. --Dennis Possible show-stoppers for 2.0.6: https://gna.org/bugs/index.php?8202 https://gna.org/bugs/index.php?8144 https://gna.org/bugs/index.php?8090 https://gna.org/bugs/index.php?7317 I'd like to see what bug #8454 turns out to be, if possible, but it's not a real showstopper to my knowledge since 2.0.x seems playable and savable/loadable on the Mac to date. Ok, I wont finish the fix for the configfile before the end of the week anyway. If you want to fix it for 2.0.6, just tell me and give an estimate how long it will take. A week or two is totally ok, imo. --Dennis pgpSBX5ku5cBl.pgp Description: PGP signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Approaching Version 2.0.6
On 2/12/07, Dennis Schridde [EMAIL PROTECTED] wrote: Am Dienstag, 13. Februar 2007 schrieb Ari Johnson: On 2/12/07, Dennis Schridde [EMAIL PROTECTED] wrote: Hi! In the roadmap (http://wz2100.net/wiki/roadmap:2.0.6) only one bug is left, which I want to fix for 2.0.6 (empty config file on Windows). Does anyone else have some bugs he wants to be fixed in 2.0.6 or bugfixes he thinks need to be ported from trunk? Otherwise I would release 2.0.6 as soon as I fixed the above mentioned problem. --Dennis Possible show-stoppers for 2.0.6: https://gna.org/bugs/index.php?8202 https://gna.org/bugs/index.php?8144 https://gna.org/bugs/index.php?8090 https://gna.org/bugs/index.php?7317 I'd like to see what bug #8454 turns out to be, if possible, but it's not a real showstopper to my knowledge since 2.0.x seems playable and savable/loadable on the Mac to date. Ok, I wont finish the fix for the configfile before the end of the week anyway. If you want to fix it for 2.0.6, just tell me and give an estimate how long it will take. A week or two is totally ok, imo. It all depends if the bug reporter will send me a savegame that causes the crash or not. I have no way of reproducing the crash until I get a savegame from him. In other words, don't hold the release of 2.0.6 back because of this bug. :) ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
