Automatic generation of Jellyfish Pro project file

[Rolf Brandt]

Yes, he left quite an impression. All the 42 stuff is based on the "Guide". I've got the original BBC radio plays. Can't count anymore how often I listened to them.

[David Kenny]

Me thinks you were just being kind to me:

MAYBE have no reply

Couldn't happen on this forum.  It's not in Paul's nature! 
I can't take credit for Paul's work ethics.

David

[Rolf Brandt]

You got a point there, David.

[John Montenigro]

...
I have always used JFP manually for testing FF compilation problems.  I had no idea (entirely my fault) that Paul had done anything to make that process easier. 
...
David Kenny

OK, I'm confused... How do I use this JFPro feature of FF3?

Let's say I have installed JFPro in FF3's User Tools, I've been editing in FF3, then I run a compile and get an error.

It sounds like I should go to User Tools, run JFPro, and open the project's .JFP file. At that point, JFPro will locate the line with the error?

Is that correct?

[David Kenny]

John,

First off, it's only needed occasionally - when FF can't correctly display the offending line of code.  Most often it does show you which line the compiler didn't like.  Then, on those rare occasions, you might have to resort to other tactics.

But, loading the .JFP file in JFP is only one step. JFP should load all the files specified in that .JFP file.  Then, I believe, you have to select the leftmost tab (should end in MAIN.bas). Then compile as you normally do in JFP. If there are any errors in the compile, JFP should take you to the correct line.

That is my current understanding of how it works.    I am, however, looking forward to someone clarifying for me how this is different/better than opening the MAIN.bas file in JFP and then compiling.

David

[Paul Squires]

I am, however, looking forward to someone clarifying for me how this is different/better than opening the MAIN.bas file in JFP and then compiling.

It is no better, or no worse. Actually, I usually just open the CODEGEN_*MAIN.BAS file most of the time. The JFP will also open a few extra files as a convenience. Whatever you're most comfortable with. It is not very often in FF3 that the file needs to be compiled in JFP in order to track down the error (that is to say that the error detection is much improved in FF3 over FF2).