Paul,
I do miss the feature. I use it quit regularly when debugging. Is there a reason you did not implement this in FF3?
Regards,
Marc
Marc,
There is no Jellyfish Pro project file per se. I am assuming you just mean the .bas file (BASIC source code file) If that's the case then you probably are looking for the CODEGEN files that FF produces.
You can now turn that on and off in the Project Properties dialog. It's the checkbox labeled 'Delete generated code after compile'. Make sure it is unchecked. Take note of the 'Main Project Folder' specified in a field a little further down that dialog. You will find the FF generated code you are looking for in the 'release' folder under the 'Main Project Folder'.
Open the one that ends with 'MAIN.bas' in JellyFish.
David
David,
Marc was quite right, FF2 generated a Jellyfish Pro project file:
CODEGEN_DBMANAGER.jfp
I removed the automatic generation of the .jfp project file. No real good reason why I did so. I will implement it again for the next update.
Thank you Paul.
I stand corrected Marc. I have never noticed this file before. I don't see how it could be used for debugging however. And I really don't think that JFP stands for Jellyfish Pro. :)
What use did you find for it Marc?
David,
At first, in FF3, in "Project properties", the option "Delete generated code after compile" should not be set.
Then In JellyFish Pro, choose menu "Project", "Open Project ..." to load all the source codes generated by FF3.
Then you should be able to compile your FF3 project directly in JellyFish Pro.
Jean-Pierre
QuoteI don't see how it could be used for debugging however.
Reason is that if PB returns an error it will give you the code line of the
generated code. In most cases FireFly will show you the correct line of code in the project, but not always. Since Jellyfish uses the generated code it will always point to the correct line of that code. That can be helpful to find an error.
Thank you Jean-Pierre and Rolf. Nothing to add :)
Marc
:-[ :-[ :-[
Well... I really should make sure I know what I am talking about before posting! I didn't notice that JFP had the feature you are referring to.
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.
Marc, Please accept my apologies - I sincerely hope I didn't offend you.
David Kenny
No problem David.
Trying to help is what makes this forum. I have done my fair share of 'not being quit right'.
It got me thinking and that is OK.
Come to think of it, if you had not reacted to this topic would MAYBE have no reply. Rolf and Jean-Pierre would MAYBE not have reacted and Paul would MAYBE not have solved my problem in 3.05.
So thank you very much :) ;) :) ;) :) ;).
Marc
P.S. example of chaos theory me thinks.
Perfectly normal paranoia. (Douglas Adams)
I will have to look up Douglas Adams. :D
Great guy! Unfortunately died much too young. He wrote the "Hitchhiker's Guide to the Galaxy", a very humerous persiflage of Star Trek. It is the incarnation of British Humor.
I just looked him up at Wikipedia.
I really liked 'Hitchhiker's Guide to the Galaxy', did not know it was him who wrote it.
British humor, the best.
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.
Me thinks you were just being kind to me:
QuoteMAYBE 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
You got a point there, David.
Quote from: David Kenny on December 08, 2009, 12:10:07 PM
...
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?
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. :P 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
Quote from: David Kenny on December 08, 2009, 09:20:06 PM
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).