Re: [Ohrrpgce] Battle code refactoring

2008-09-03 Thread Ralph Versteegen
On Tue, Sep 2, 2008 at 9:29 AM, Simon Bradley [EMAIL PROTECTED] wrote: On Mon, Sep 1, 2008 at 6:09 PM, Ralph Versteegen [EMAIL PROTECTED] wrote: On Mon, Sep 1, 2008 at 7:46 AM, Mike Caron [EMAIL PROTECTED] wrote: Ralph Versteegen wrote: On Sun, Aug 31, 2008 at 5:22 PM, James Paige [EMAIL

Re: [Ohrrpgce] Battle code refactoring

2008-09-03 Thread James Paige
On Thu, Sep 04, 2008 at 07:34:04AM +1300, Ralph Versteegen wrote: I'd favour rewriting the whole text file with no slack every time. It'd be a lot easier to deal with. You could keep the index consistent (so string 20 remains string 20 even if you delete string 19 - 19 would be recycled

Re: [Ohrrpgce] Battle code refactoring

2008-08-31 Thread S'orlok Reaves
except that attempts to do indenting Haha, yeah, indenting sucks. I want to add the option to strip indents at some point if the value of a ${} code changes when the box is being displayed, the box changes? Oh, no, that's not what I meant. That would, indeed, cause errors as you

Re: [Ohrrpgce] Battle code refactoring

2008-08-31 Thread Ralph Versteegen
On Sun, Aug 31, 2008 at 5:22 PM, James Paige [EMAIL PROTECTED] wrote: On Sun, Aug 31, 2008 at 03:51:43AM +1200, Ralph Versteegen wrote: On Sun, Aug 31, 2008 at 2:49 AM, James Paige [EMAIL PROTECTED] wrote: On Sun, Aug 31, 2008 at 02:10:58AM +1200, Ralph Versteegen wrote: On Sat, Aug 23, 2008

Re: [Ohrrpgce] Battle code refactoring

2008-08-31 Thread Mike Caron
Ralph Versteegen wrote: On Sun, Aug 31, 2008 at 5:22 PM, James Paige [EMAIL PROTECTED] wrote: On Sun, Aug 31, 2008 at 03:51:43AM +1200, Ralph Versteegen wrote: On Sun, Aug 31, 2008 at 2:49 AM, James Paige [EMAIL PROTECTED] wrote: On Sun, Aug 31, 2008 at 02:10:58AM +1200, Ralph Versteegen

Re: [Ohrrpgce] Battle code refactoring

2008-08-30 Thread James Paige
On Sun, Aug 31, 2008 at 02:10:58AM +1200, Ralph Versteegen wrote: On Sat, Aug 23, 2008 at 3:50 AM, James Paige [EMAIL PROTECTED] wrote: As you may have already noticed, I have started on a major battle code refactoring quest. I plan to: * subify every single gosub in bmod.bas * make

Re: [Ohrrpgce] Battle code refactoring

2008-08-30 Thread Ralph Versteegen
On Sun, Aug 31, 2008 at 2:49 AM, James Paige [EMAIL PROTECTED] wrote: On Sun, Aug 31, 2008 at 02:10:58AM +1200, Ralph Versteegen wrote: On Sat, Aug 23, 2008 at 3:50 AM, James Paige [EMAIL PROTECTED] wrote: As you may have already noticed, I have started on a major battle code refactoring

Re: [Ohrrpgce] Battle code refactoring

2008-08-30 Thread James Paige
On Sun, Aug 31, 2008 at 03:51:43AM +1200, Ralph Versteegen wrote: On Sun, Aug 31, 2008 at 2:49 AM, James Paige [EMAIL PROTECTED] wrote: On Sun, Aug 31, 2008 at 02:10:58AM +1200, Ralph Versteegen wrote: On Sat, Aug 23, 2008 at 3:50 AM, James Paige [EMAIL PROTECTED] wrote: As you may have

Re: [Ohrrpgce] Battle code refactoring

2008-08-30 Thread S'orlok Reaves
Hmmm... what about the case where somebody writes a line with a ${} code in it that expans and makes the line too long. Is there any reasonable way to handle that case at run-time rather than edit-time? The OHRRPGCE FMF handles this by dyanmically expanding text boxes at run time, and

Re: [Ohrrpgce] Battle code refactoring

2008-08-30 Thread James Paige
On Sat, Aug 30, 2008 at 10:43:24PM -0700, S'orlok Reaves wrote: Hmmm... what about the case where somebody writes a line with a ${} code in it that expans and makes the line too long. Is there any reasonable way to handle that case at run-time rather than edit-time? The OHRRPGCE

[Ohrrpgce] Battle code refactoring

2008-08-22 Thread James Paige
As you may have already noticed, I have started on a major battle code refactoring quest. I plan to: * subify every single gosub in bmod.bas * make bmod and bmodsubs both compile with OPTION EXPLICIT In this process I am also gathering various stray data into TYPEs. I am doing this in many