** VOTE ** - New TorqueScript extension!

Friendly conversations, and everything that doesn't fit into the other forums.
24 posts Page 2 of 3
Jason Campbell
Posts: 272
Joined: Fri Feb 13, 2015 2:51 am
 
by Jason Campbell » Tue Jun 28, 2016 3:29 am
I'd rather stick with .ts or another non-three-letter. How about .os for onlyScript.
Dwarf King
Posts: 168
Joined: Thu Feb 05, 2015 7:20 pm
  by Dwarf King » Wed Jun 29, 2016 3:30 pm
Should the day come where .cs is changed I shall see this as an act of war. Prepare yourself for a declaration then.



:mrgreen: :mrgreen: :mrgreen: :mrgreen: :mrgreen: :mrgreen:

Awesome song even though it is a parody :D
Bloodknight
Posts: 148
Joined: Tue Feb 03, 2015 8:58 pm
by Bloodknight » Fri Jul 01, 2016 2:36 pm
I'm pretty much on the fence with this.

Identifiable pros
The .cs is handy as it does trigger rudimentary (but incorrect) highlighting in most common editors, this highlighting is enough to aid navigation and readability for the most part.

identifiable cons.
If you've installed visual studio *after* your common editors, it hijacks the launch via extension. On my system at least this lumbering beats takes a while to start up before it can be shut down.

Identifiable work regardless of pro/con.
Extension needs to be assigned to the correct editor.
Editor needs to have the correct highlighting. you can add .ts .tsc to the C/C++/C# highlighting lists of most editors anyway
(side note, notepad++ gets quite pissy when trying to reassign .cs files to C or C++ highlighting.)

Seems to me that there are several issues here regardless of the actual extension.
The main one being lack of 'correct' syntax highlighting in many editors. So, regardless of extension changing perhaps the people who are good at editing such things could make functioning syntax highlighters for their favourite editors. I have seen a notepad++ one in the past, cant find it now, i also seem to think it wasnt quite right.

So to all you atom/sublime/notepad/VScode users out there, would you consider making a highlighter plugin for torque, we can always make minor changes if the extension changes.
LukasPJ
Site Admin
Posts: 388
Joined: Tue Feb 03, 2015 7:25 pm
 
by LukasPJ » Sun Jul 03, 2016 5:00 pm
I'm pretty much on the fence with this.

Identifiable pros
The .cs is handy as it does trigger rudimentary (but incorrect) highlighting in most common editors, this highlighting is enough to aid navigation and readability for the most part.

identifiable cons.
If you've installed visual studio *after* your common editors, it hijacks the launch via extension. On my system at least this lumbering beats takes a while to start up before it can be shut down.

Identifiable work regardless of pro/con.
Extension needs to be assigned to the correct editor.
Editor needs to have the correct highlighting. you can add .ts .tsc to the C/C++/C# highlighting lists of most editors anyway
(side note, notepad++ gets quite pissy when trying to reassign .cs files to C or C++ highlighting.)

Seems to me that there are several issues here regardless of the actual extension.
The main one being lack of 'correct' syntax highlighting in many editors. So, regardless of extension changing perhaps the people who are good at editing such things could make functioning syntax highlighters for their favourite editors. I have seen a notepad++ one in the past, cant find it now, i also seem to think it wasnt quite right.

So to all you atom/sublime/notepad/VScode users out there, would you consider making a highlighter plugin for torque, we can always make minor changes if the extension changes.
Here is the known list of editors and plugins in case you were wondering: http://wiki.torque3d.org/introduction:scripting-ides
Bloodknight
Posts: 148
Joined: Tue Feb 03, 2015 8:58 pm
by Bloodknight » Sun Jul 03, 2016 5:22 pm
ive seen that page and frankly, it needs to be rewritten so that

1) its written by somebody who doesnt dispise torquescript and or windows.
2) uses software developed this century.
3) doesnt actually scare the living shit out of potential developers.

vim seriously, apart from superiority complex, antique and bristly microsoft haters pretty much nobody really uses vim. :p

most of the other options are old open source software with some hacked together half working syntax, again developed for much older version of the engines so not much more than the half baked syntax highlighting even works anymore.

The potential saving grace here is that the two leading windows contenders are now open source, it would do the community better if one was picked and modernised, and possibly made cross platform.

This conversation has gotten wholly sidetracked, probably all my fault, but really all i was trying to point out was that a small amount of work potentially fixes most of the problems associated with the extension 'problem'.

The only real problem i see with .cs is the C# conflict for those who develop in C# most of whom will be using Visual Studio simply because of its superiority in its domain, other C# devs who use a 'one editor to rule them all' system like atom or VS code or sublime etc only have issues of highlighting which i dont really see an alternative to extension change as a solution.

it does however need pointing out that for those who do have issues with the extension, the ability to change the extension for a particular project is pretty trivial, and tbh its something i might possibly recommend anyway.
Johxz
Posts: 447
Joined: Sat Feb 07, 2015 11:37 pm
by Johxz » Sun Jul 03, 2016 10:13 pm
I have seen a notepad++ one in the past, cant find it now, i also seem to think it wasnt quite right.

So to all you atom/sublime/notepad/VScode users out there, would you consider making a highlighter plugin for torque, we can always make minor changes if the extension changes.
You can download from here: To configure the plugin:
  • open Notepad++
  • in the View menu, click Language, then "Define your language..."
  • Click Import and select the file you downloaded
  • restart Notepad++
  • in the Language menu, you should now see a language called Torquescript at the bottom. Select it, and you're ready to go.
vim seriously, apart from superiority complex, antique and bristly microsoft haters pretty much nobody really uses vim. :p
Ahm not completely true hahaha :lol: maybe for game development you are right I don't know in this field.... but vi, vim, emacs, and other obscure editors are used everyday, for different uses, not only to program... Especially the 3 which I named :D but you're right....
The potential saving grace here is that the two leading windows contenders are now open source, it would do the community better if one was picked and modernised, and possibly made cross platform.
we're on it ;) of course!!!
This conversation has gotten wholly sidetracked, probably all my fault
Don't worry... some went through this too :D
'one editor to rule them all' system like atom or VS code or sublime etc only have issues of highlighting which i dont really see an alternative to extension change as a solution.
This are good alternatives, even notepad++ with his plugins, but this are text editors, you need to tweak to do stuff more like IDE. I remember doing something like this in sublime to compile my project and stuff..

Ok but an IDE or a TEXT EDITOR are two different thing...
Bloodknight
Posts: 148
Joined: Tue Feb 03, 2015 8:58 pm
by Bloodknight » Mon Jul 04, 2016 12:54 am
the lines are blurring, and have been for some time, vim was always just an editor with some decent plugins, now theres a variety of plugins to turn it into an IDE and even some guis that turn it into a full ide, many of the text editors especially the newer ones have the ability to compile on command, when the ability to debug in text editors is ironed out the transformation will be complete.

however there are still a lot of people especially on linux that spend an inordinate amount of time typing make into a terminal rather than clicking on the run button, and tbh torque script editing is much more like that for many people, and will be for many more when autoloading and autorunning overwritten functions become a thing in T3D. At which point the text editor and its corrected syntax highlighting become a more useful tool; imo.

as for the NPP thing, yeah i tried it before managed to screw up notepad... dont ask, its a gift :p
Monkeychops
Posts: 25
Joined: Wed Feb 18, 2015 11:53 am
by Monkeychops » Mon Jul 11, 2016 4:18 pm
Microsoft stole your ".cs" extension, but you should also be aware they stole your ".ts" proposal as well with "Typescript", and "tsc" is the typescript compiler :D

i would suggest .t3d as the safest extension that isn't like to clash.
andrewmac
Posts: 295
Joined: Tue Feb 03, 2015 9:45 pm
 
by andrewmac » Mon Jul 11, 2016 6:18 pm
and "tsc" is the typescript compiler :D
That usage is an initialism not a file extension. As a file extension .tsc is said to only be used by TINA: http://filext.com/file-extension/TSC which is a circuit simulator. Obscure enough that I think we're safe to use it.
rlranft
Posts: 298
Joined: Thu Feb 05, 2015 3:11 pm
 
by rlranft » Tue Jul 12, 2016 6:44 am
vim seriously, apart from superiority complex, antique and bristly microsoft haters pretty much nobody really uses vim. :p
No doubt! I use vi much more often than vim.

And I voted for .torquescript because I'm perverse that way (I'm a father, after all). And it won't clash.
24 posts Page 2 of 3

Who is online

Users browsing this forum: No registered users and 3 guests