JEdit and TIDE fiddling...
by Stefan Beffy Moises · 11/23/2006 (3:30 pm) · 25 comments
Hey folks,
just wanted to let you guys know what I'm up to currently... besides doing some contract work and careing for our little baby-boy Erik (see my last blog), I found some late evening hours yesterday and today to re-visit our TIDE plugin suite for JEdit for Torque script file editing and debugging (torqueide.sf.net) - not sure if anyone else (still) uses JEdit for Torque, but wth :P To me, its still the best solution (and it works on linux, too, yay!)
I was using Codeweaver for quite some time but got annoyed with crashes and stuff some day, so I switched back to my beloved JEdit a couple of months ago... although I realized that TIDE was missing ONE major feature (to me, anyways): Code-completion!
So I was looking into the JEdit Sidekick plugin and tried to get it to work for Torque key words, so that I'd get some auto-complete features... basic completion (based on Codeweaver's "autocomplete.txt" file) wasn't very hard to get in, so I got that part working tonight:
If I find the time I'll also look into adding the exported engine classes for auto-completion just like Codeweaver does, but that may take a while... but I think the current completion already saves me lots of time, so I'm happy :) Got some more tests and little fixes to do still, but if anyone's interested in trying, just send me an email...
Other than that... little Erik is doing well, the Animal pack should hopefully be finished soon (it only needs some final sounds and some testing...) and I really need some sleep! ;)
until next time,
cheers,
beffy
just wanted to let you guys know what I'm up to currently... besides doing some contract work and careing for our little baby-boy Erik (see my last blog), I found some late evening hours yesterday and today to re-visit our TIDE plugin suite for JEdit for Torque script file editing and debugging (torqueide.sf.net) - not sure if anyone else (still) uses JEdit for Torque, but wth :P To me, its still the best solution (and it works on linux, too, yay!)
I was using Codeweaver for quite some time but got annoyed with crashes and stuff some day, so I switched back to my beloved JEdit a couple of months ago... although I realized that TIDE was missing ONE major feature (to me, anyways): Code-completion!
So I was looking into the JEdit Sidekick plugin and tried to get it to work for Torque key words, so that I'd get some auto-complete features... basic completion (based on Codeweaver's "autocomplete.txt" file) wasn't very hard to get in, so I got that part working tonight:
If I find the time I'll also look into adding the exported engine classes for auto-completion just like Codeweaver does, but that may take a while... but I think the current completion already saves me lots of time, so I'm happy :) Got some more tests and little fixes to do still, but if anyone's interested in trying, just send me an email...Other than that... little Erik is doing well, the Animal pack should hopefully be finished soon (it only needs some final sounds and some testing...) and I really need some sleep! ;)
until next time,
cheers,
beffy
#22
02/08/2007 (2:55 pm)
ah i see, i thought it was like torsion where you get the console responses and can do commands from it but this is still cool, kinda like vc++'s debugger.
#23
thanx again
03/15/2007 (9:22 am)
Hey, thanks for all this great work on Tide! So I've found it time to finally upgrade my version of Jedit to something more recent. I am going to go for 4.3pre9. Well once I did that, and use your jars from sourceforge, they wouldn't work. I got errors in ProjectViewer & SideKick. Things like missing method calls, incorrect method calls, etc. Is there anyway you can build against the latest stuff? I would really like to use 4.3pre9. But even if you can suggest which veersion you are using, or even if you can zip up your jedit folder with tide configured, that might be useful. thanx again
#24
a) find out what they've changed this time
b) change my code accordingly
which I dont have any time for at the moment... (
For now you'll have to stick with 4.2 final... I'll see if I can fix it when 4.3 turns final ;)
03/15/2007 (9:36 am)
Well, it looks like JEdit is changing its plugin API with every release :( Unfortunately, I'd have to a) find out what they've changed this time
b) change my code accordingly
which I dont have any time for at the moment... (
For now you'll have to stick with 4.2 final... I'll see if I can fix it when 4.3 turns final ;)
#25
03/15/2007 (9:54 am)
Yeah I can understand what you mean. Anyways, I'll stick with 4.2, works like a charm (except when Java acts up and garbage collection doesn't kick in ;) 
Associate Stefan Beffy Moises
@Benj: hm, I think the ProjectViewer has to be open at least once to make the debugging work iirc, yes.... that's because the Debugger needs to know what project you are working on currently, and that is only set if you open it or if you change projects... maybe I can find a workaround there, gotta check that.
And yes, it gives feedback... basically, you can set breakpoints (with the red dot) at lines where it make sense and where you want to stop execution, say at the end of "GameConnection::createPlayer()" in game.cs... then you start the debugger and it stops the engine once it arrives at that line... now you can see the value of variables by pointing your mouse arrow over them, and you can also use "Step into", "Step over", etc. in the TIDEDebug menu... for further details, see torqueide.sourceforge.net/docs/using.html and this image.