Delta 3 Release Available

[Sam Bacsa]

Delta 3 release is now available, and includes fixes indicated in Mantis, as well as the following additions:

- SDK: Added onBeforeDocumentSwitched
- SDK: Added onAfterDocumentSwitched
- SDK: Fixed SetCursorPosition
- Changed function descriptions implementation (see firstrun notice)
- Added "special comments" to syntax highlighting configuration
- Added support for different project types
- Deprecated "classinfo.txt" in favor of type-specific files: class_t2d.txt, class_tge.txt, and class_tse.txt.
- Added "eval" keyword to syntax highlighter and infopop
- Added functions dropdown to editor

Available now through the standard installation package.  Make sure you COMPLETELY UNINSTALL your previous version.

http://www.torquedev.com/

[Sam Bacsa]

There was an issue with saving files throwing an exception.  If you downloaded it before this post, please download it again.  The problem has been fixed.

Sorry for any inconvenience.

[Steven Chiu]

So glad that the functions dropdown been added in this version and you always give us the surprise!

A thought about this feature is if you can also put the class name in the dropdown left side just as VS.NET does then it'll be perfect. Because I found that all the functions with  namespace prefixed are missing in the dropdown list and it seems a little bit confusing.

BTW I also noticed that the performance got improved in this new version.

[Sam Bacsa]

^ Hi Steven,

Oh. Right. Classes. Heh, forgot   I'll definitely add that

Thanks again,
Sam

[brainchildcm]

Hello all,

In case anyone cares, I've been working on a plug-in that allows the user to get a tree-view style look at their active file, TIDE browser style.  I got used to this feature using jEdit so I thought I'd try to reproduce it.  Here are a couple shots of the Torque Browser plug-in in action.  I still have to work out a couple of minor bugs.  The plug-in only works with version 1.2.2063.23071 (Delta SDK Rel 3).  Functions, datablocks, and objects are shown in the tree with their respective line number.  The list is sorted by text then line number.  I have found this to be a more intuitive (for myself anyhow) way to find stuff in large files.  The user can then double-click on a tree node to go to the appropriate place in the code.  I'm still working on switching focus to the workspace tab after the double-click event.  Sam??

Anyway, any thoughts, ideas, nasty accusations would be greatly appreciated.

Thanks,
cm

PS Now for the links

Functions and Objects
http://i20.photobucket.com/albums/b208/brainchildcm/Development/plugin1.jpg

Datablocks
http://i20.photobucket.com/albums/b208/brainchildcm/Development/plugin2.jpg

[Sam Bacsa]

Wow that's good stuff

I'm still working on switching focus to the workspace tab after the double-click event. Sam??

Focus. No problem

Does this enumerate everything in the project, or only open files?  Or only the active file?

BTW, what's "The Montauk Project" about? I've heard of the "real" Montauk Project.  Is this somehow related?

[brainchildcm]

Sam,

It only works on the active file.

Woops, I guess I should have used the starter.fps project as my example.  My team and I have been working on a game by that name.  We're not really ready to announce it yet though.  We have been researching the legend of the Montauk project for just over one year.  Our design documents are complete and we're moving into phase-1 as we speak.  I'll announce something on the GG forums when we near Alpha 1.  It may actually take longer then expected cause we're going to be porting it over to TSE/SGLP.  Currently using the TGE-SGLP 1.3.5 for the dynamic lighting capabilities.  Lighting will play a huge roll in this thing.  In case you were wondering it's going to be an FPS/horror-suspense/sci-fi with just enough run and gun levels to keep the killers out there happy.  That's all I can say for now!.

Thanks,
cm.

[brandon8863]

That does look like a useful plugin! Nice work.

B--

[brainchildcm]

Sam,

Would it be possible to provide some kind of nexus for TorqueDev plugin development.  Plug-in developers could submit the code to netMercs (for safety) then individual developers could snag the plug-ins that are most useful to them.

Thanks,
cm

PS I'll definately be posting the source for this once it's done.

[Sam Bacsa]

Well my plan is to require plugins to be signed by netMercs before they'll run without a warning dialog popping up (similar to visiting secure sites without a signed certificate by an approved CA).

I'd be signing freeware plugins for no charge.  Pay-for plugins would be signed for a certain amount of money.

Turn-around time would probably be a day at max for signing.

And yeah I would probably host them on this site.