Plan for Cameron Aycock
by Cameron Aycock · 06/21/2004 (9:37 pm) · 2 comments
This is my first plan, so bear with me.
I am in the middle of building a new computer, I sold my old one, so during that time I have had an old celeron 300A (used to be o/cd to 450), to do my browsing/playing. It uses the intel i810 chipset and onboard graphics controller, so running the Torque engine is just barly usable.
Due to this condition, I reinstalled the OS on the machine and have played with Eclipse and MingW. I have had great success with compiling from this environment. I am still learning the Eclipse IDE, but am very impressed by the responsivenes of a Java IDE (thanks to the SWT). My next step is to see how debugging works in the environment.
In contrast, I fired up JEdit, and noticed how much slower it was on this machine, which led me to go back to TribalIDE. I realized how SPOILED I am on the Jedi/TIDE platform for editing scripts.
I am a professional Delphi programmer, and managed to find the TribalIDE Source code. After all night finding and backreving some of the components to their 2002 versions (some wern't even listed), I managed to get my own build of TribalIDE, which I released to the community, and made a post on the boards. I simply added importing of GUI and MIS files in addition to the cs files.
After playing with it, and realizing that my new machine will be put together on Wed., I decided to go back to using JEdit, and see if I could get help out on the TIDE front. I think this would be the optimal solution for everyone.
I spent a great deal of time today throughly looking at all "normal" features in JEdit, and how I canuse them to my advantage. Here are some tips that have proven to be invaluable to anyone using JEdit:
1. You can modify the right click context menu in the buffer. (Right click -> customize) I used this ability to add the "Search Current Selection In Project" option from the TIDE Browse plug-in. (you MUST remove any operators in the project viewer extension eg: "C++" for this to work.. otherwise it will error out). This basically game me a simple "Goto Definition" popup menu! WOOT!
2. I got bugged by the damn result popping up, so I docked the hypersearchwindow to the right (with TIDE Browse) and I can easily switch without losing my place!
3. The REAL power lies in JEdit's abbreviations (like templates). I added roughly 15 custom abbreviations to the abbreviations list and have probably sped up my typing speed by %100. It even allows for parameters. I made them for function declarations with comments, and for loops with an iterator. As I come across repetitave things, I will keep on adding them.
4. MACROS -- I am thinking that I may be able to add some really nifty tools for Torque Script with simple Macros (instead of writing an entire plug-in). This is an area I have used in other languages, but am just beginning to play with in JEdit. If anyone has any they would like to share, I am all ear...er...eyes.
5. Code Completion. JEdit has a rudimentary code completion for the current buffer built right into the editor (it is CTRL-b by default) I changed it to CTRL-Space, and BAM.. like Delphi-- well ALMOST(damn I'm spoiled).
6. Wishes. Here is my current wish list/gripes/planned project for TIDE in the future:
-- Expand the nodes by default. I am sick of having to open the list every time I switch buffers.
-- Add a "Globals" tree to the browser. One of my quirks about TorqueScript, is that you can define vars ANYWHERE. It is simple, but I am worried that down the line this will cause confusion with global vars. I have thought about making a sepatate cs file and using namespaces to aoganize all globals, but, it would be cool if the browser listed them, the files they are in, and the line in each file.
-- Code Completion ...everyone wants this one. Basically, object smart "Dot" completion across the current project.
-- DEBUGGER... 1 thing, just 1 thing, ... to follow the debug line. So much tiome is wasted trying to figure out where the debugger's "current line" went, when you step out of a function. The active file/line should be opened automatically whenever you step out or pause the game. If it already does this, can someone show me how to get it working.
Whelp, thank you for readin my first Plan. I hope I didn't bore you.
Cameron Aycock
Lead Programmer
The Chronicles Of Ny
www.clownkeep.com
I am in the middle of building a new computer, I sold my old one, so during that time I have had an old celeron 300A (used to be o/cd to 450), to do my browsing/playing. It uses the intel i810 chipset and onboard graphics controller, so running the Torque engine is just barly usable.
Due to this condition, I reinstalled the OS on the machine and have played with Eclipse and MingW. I have had great success with compiling from this environment. I am still learning the Eclipse IDE, but am very impressed by the responsivenes of a Java IDE (thanks to the SWT). My next step is to see how debugging works in the environment.
In contrast, I fired up JEdit, and noticed how much slower it was on this machine, which led me to go back to TribalIDE. I realized how SPOILED I am on the Jedi/TIDE platform for editing scripts.
I am a professional Delphi programmer, and managed to find the TribalIDE Source code. After all night finding and backreving some of the components to their 2002 versions (some wern't even listed), I managed to get my own build of TribalIDE, which I released to the community, and made a post on the boards. I simply added importing of GUI and MIS files in addition to the cs files.
After playing with it, and realizing that my new machine will be put together on Wed., I decided to go back to using JEdit, and see if I could get help out on the TIDE front. I think this would be the optimal solution for everyone.
I spent a great deal of time today throughly looking at all "normal" features in JEdit, and how I canuse them to my advantage. Here are some tips that have proven to be invaluable to anyone using JEdit:
1. You can modify the right click context menu in the buffer. (Right click -> customize) I used this ability to add the "Search Current Selection In Project" option from the TIDE Browse plug-in. (you MUST remove any operators in the project viewer extension eg: "C++" for this to work.. otherwise it will error out). This basically game me a simple "Goto Definition" popup menu! WOOT!
2. I got bugged by the damn result popping up, so I docked the hypersearchwindow to the right (with TIDE Browse) and I can easily switch without losing my place!
3. The REAL power lies in JEdit's abbreviations (like templates). I added roughly 15 custom abbreviations to the abbreviations list and have probably sped up my typing speed by %100. It even allows for parameters. I made them for function declarations with comments, and for loops with an iterator. As I come across repetitave things, I will keep on adding them.
4. MACROS -- I am thinking that I may be able to add some really nifty tools for Torque Script with simple Macros (instead of writing an entire plug-in). This is an area I have used in other languages, but am just beginning to play with in JEdit. If anyone has any they would like to share, I am all ear...er...eyes.
5. Code Completion. JEdit has a rudimentary code completion for the current buffer built right into the editor (it is CTRL-b by default) I changed it to CTRL-Space, and BAM.. like Delphi-- well ALMOST(damn I'm spoiled).
6. Wishes. Here is my current wish list/gripes/planned project for TIDE in the future:
-- Expand the nodes by default. I am sick of having to open the list every time I switch buffers.
-- Add a "Globals" tree to the browser. One of my quirks about TorqueScript, is that you can define vars ANYWHERE. It is simple, but I am worried that down the line this will cause confusion with global vars. I have thought about making a sepatate cs file and using namespaces to aoganize all globals, but, it would be cool if the browser listed them, the files they are in, and the line in each file.
-- Code Completion ...everyone wants this one. Basically, object smart "Dot" completion across the current project.
-- DEBUGGER... 1 thing, just 1 thing, ... to follow the debug line. So much tiome is wasted trying to figure out where the debugger's "current line" went, when you step out of a function. The active file/line should be opened automatically whenever you step out or pause the game. If it already does this, can someone show me how to get it working.
Whelp, thank you for readin my first Plan. I hope I didn't bore you.
Cameron Aycock
Lead Programmer
The Chronicles Of Ny
www.clownkeep.com
#2
06/22/2004 (6:19 am)
indeed good tips. I remember the first time i realized you could bind things to the right click menu and added the search in project option... ahhh happy day! Thanks again for that beffy! :) 
Associate Melv May
I use JEdit for everything and it would take a good app to stop me using it. Those tips are *really* useful, many thanks for sharing.
I can only suggest that you post this plan as a resource as people may miss these handy tips and it also may encourage people to post more of them.
Many thanks,
- Melv.