Adding a new Torque Script Extension

#1 I think the best extension would be *.ts short for torque script

#2 Have been thinking about this most of the day, and the only real things I can think of:

1) You'll need to obviously change all of your scripts that exec(...) files to reflect the new extension.
2) You'll need to modify the exec(...) function itself, as well as any low level primitives in consolexxx.cc/h that deal with loading and compiling script files.
3) You'll need to probably look for the same thing in 2) above for searching for (and writing out) .cs.dso files. We normally just call them .dso, but there is a .cs stub in there as well.
4) There is probably more that I'm missing!

#3 .ts would be better since TSE/TGE/T2D all use TorqueScript.

#4 @ Stephen Zepp - Thanks for the insight sound like a big deal as I suspected. I've been mulling things over and I'm starting to think it might be a better use of my time to work on a Torque editor. Meaning an editor built on/in Torque. Labrat suggested I check out Davis Sickmon's work TGE In-Game Script Editor. So I need to at least research that first.

@ Michael-Paul & David - Actual .ts was the second thing that jumped into my mind (after .tcs), but according to FileExt that is the extension for "Transport Stream MPEG-2 Video Stream" which I was thinking could lead to some problems.

Quote:VOB files you find on a DVD are MPEG2-PS files. The PS format, however, is not adapted for streaming video through a network or by satellite. Another format called Transport Stream (TS) was designed for streaming MPEG videos through such channels. VideoLAN software can handle these streams.

On the other hand it isn't a language and maybe that is all that matters.

#5 Every time I've seen TS files utilized in realtime, they've been ecapsulated in another wrapper format like WMF's, MOV's, or Real Media formats. Video encoding programs may see them and try to encode them, but they shouldn't cause streaming problems. At least not from my experience. I only have limited distanced learning and streaming video knowledge, though.

How about .tps for Torque Platform Script.

But that could get confused with TPS reports...

#6 How about .tsc?

I haven't seen this extension used in programs.
GG any comments about the new extension for torque scripts suggestions?

#7 I'm curious... What does the c in cs stand for?

I'm not sure about macs or linux, but on windows, we're no longer limited to two or three letters in extensions. How about just .torque?

-Nick

#8 @Nikhil
I always assumed it stood for compiled script

#9 .cs (as far as I know) stands for c script.

#10 @Philip
I think Nikhil was wondering what the "c" in the torque script extension cs is for. But yes, .cs is also the extension for c#.

#11 @Todd Yes, and he answered. ;) Script that is derivative of the language 'C', predecessor to 'C++'.

#12 @Daniel
Now that you say that I see what he was saying, I totally read it wrong heh

#13 That was funny. I guess I should be more clear.

To Torque .cs = c script
To Visual Studio .cs = c sharp

To Einstein c is the constant speed of light

#14 @David Blake -

But that could get confused with TPS reports...

was that a reference to Office Space??

#15 Office Space was a great movie. :) .TSC would be a good extension, but really, since the engine doesn't use C#, it's hard to confuse C# code files and scripts.

#16 @daniel

Atleast we configure the application when doubleclick seperately from C# plus we can provide a new kickass icon for Torque Scripts without ruining Bill Gate's Empire Softwares lol.

*.tsc for torque script WHO SAYS AYE?

#17 Good point John. Forgot about that.

#18 We see you've been missing a lot of work.
Well, I can't say I've been missing it!

Since I haven't felt like doing a find/replace on cs and then recompiling the engine and then sorting out a large number of referential bugs, it may be a good reference point to check on the TorqueBASIC project. The aim of TorqueBASIC was to add TorqueScript functionality with BASIC syntax for new user integration. I believe that a BASIC parser was even created. It might be a good idea to use it as a starting point.

#19 @Daniel - Maybe I'm missing the joke but the problem isn't a human telling the difference between the files the problem is that I can't add Torque Script as a language Visual Studio recognizes because it conflicts with C# Sharp files. As far as I've figured there is no way around this problem within Visual Studio so I figured it might be easier to change the extension from with in Torque.

At this point, I'm so busy working on my game etc. that I haven't put much more time into the project. I've started using ConText which is free and does alright.

@David - I'll have to looking to this project, maybe it'll outline some of the work necessary.

In general because I am a programmer by trade I tend to get involved in complicated tools changes which slows down the progress on my game. So I'm constantly reminding myself to put the game first. Maybe If I didn't have a day job and I could put aside a few hours a week to improve tools I'd be able to make some progress in this area, but for now I would count on it.

#20 Philip, you're absolutely right - I just didn't see the problem at first because I use Visual Studio to read my .cs scripts, but I only have C++... not C#, so I have no conflicts. A new extension is necessary. :)