vJass syntax highLight for gEdit

What is Gedit?
Gedit is a simple text tool with many highlights for Linux with Gnome. It is free and open source software and is not available for Windows, so yes, if you are a Windows user, this is not for you.
You can have more information about Gedit at: http://projects.gnome.org/gedit/

Hi guys, a few days ago I was working on Linux... when suddenly I wanted to code warcraft (lol). However, I don't have it installed on Linux due a few problems and so JNGP can not help me. So, the next logical solution would be to make something light that could aid me making my codes, which is why I decided to create this plugin for Gedit, a plugin that allows people to have syntax highlight checker in Gnome for vJass.
This plugin allows the user to have highlights to all non-BJ functions and to automatically view ".j" files. This plugin is the most possible user friend there can be with the limitations of Gedit .lang files, I can't add anything else or it won't run because it will be to big (damn stupid compilers xD ). It gave me lots of work and hell to make this thing work, please I hope Linux people enjoy it xD



History:

Hidden information: Version 1.0: - Initial public release Version 1.1: - Added "local" and "elseif" to keywords - Improved the documentation in many points Version 1.2: - Added Credits to the comments of the header of the file - Completed the game variable type highlight Version 1.3: - Completed the list of keywords - Added more people to credits Version 1.4: - Added more keywords - Fixed a small exploit with word nothing - Closed the file, it cannot support anything esle

How to install?

There are two files: vJass.lang and vJass.xml and they go to separate folders.

vJass.xml:
1 - This is an optional step. By making it you will be able to automatically have the vJass highlights mode when you open a ".j" file. It is not necessary to make the highlights work, but it is nice because this way you don't need to go to "View -> Highlight -> Others -> vJass".
2 - Go to "~/.local/share/mime/packages" (create it if it doesn't exist yet)
2.1 - Remember .local is a hidden folder, you have to enable the view of hidden folders
3 - paste this file there
4 - Go to "~/.local/share" and run: "update-mime-database mime" (if you can't run the command it is ok as well, but I advice to do so)

vJass.lang:
1 - This is the necessary step for you to have highlights working.
2 - copy this file to the following path: "/usr/share/gtksourceview-2.0/language-specs"

Note: All the process must be done with Gedit closed.

After this simple steps, Gedit will now syntax Highlight vJass from ".j" files =P
Have fun!

Sounds well but I would have prefered Kwrite/Kate.
Maybe I will test it next days.

Dude your thread title sounds like some spammer trying to boost google page ranks...

You could, like make it yourself...

I should really find out if there's a way for Jass in geany, I would be able to get rid of gvim as Jass is the only reason I have that installed. Yeah, I wish to have a geany vJass plugin, however those things are made.

Edit: Regarding this: It doesn't seem to highlight local or elseif...

A KDE adept hein? Well, I suppose the files and extensions can't differ much, however the information available for Kate extensions is quite limited, and the foruns are not much of a help. If I do something for Kate, I will be sure to post it here.

I am sorry, my true intention was to be very specific. Can someone please change the title to:
vJass HighLight checker for Gedit please? I will add "What is Gedit" mini-section after the title is changed.

Sounds very interesting. Let me make a quick search:


So, Hacking Geany seems to be quite legal... nice =P
For more info:
http://www.geany.org/Documentation/FAQ#QQuestions4

Ohhh I forgot those xD
Well, problem is now Fixed version 1.1 released.

I really hope this gets approved xD

EDIT EDIT EDIT

New version released, 1.2, see "History" for more information.

Bump, new version released, 1.3, see changelog for more info.

approval bait.

Thx for approval =D

I wonder if I can make a tutorial on how to have JNGP in Linux ... xD

Anyways, back on topic, I hope Gnome users enjoy this extension.

Thanks again bro. And I'd take you up on that JNGP in linux offer, it'd be nice to get back into mapping.

*cough* bug, second nothing isnt highlighted.

add nothing to variable types ...
and add module, endmodule and implement.
And why is "threaded" highlighted as keyword ?

And when you highlight onDestroy, you should highlight onInit aswell ....and allocate and eventual even create / Create

nothing is defined as a keyword. If it doesn't get highlighted it's because of gnome's poor gtk compiler.
not sure if that will be possible. You see, gnome's gtk compiler is so weak, that it doesn't allow me to add anything else to the list. If I add more keywords and regular expressions to the list, the user will start seeing "Efficiency problems" on the plugin, and if I ignore this warning and add even more, the plugin will simply blow up gedit and nothing will be highlighted at all.

I will give this a better look however. Thx for rep.
As for the gnome plugin database, I make no idea on how to do that xD

EDIT EDIT EDIT

plugin updated, please read History for more information.
I will not fix nor add anything else about missing keywords or datatypes or missing things. The file is already giving me efficiency warnings, the source file is now considered to big. Any attempt at adding more information will blow the plugin. This is the best you can do with the current version of Gedit.

i added more keywords to my file myself, however i havent got any warnings ...

Seriously, you don't believe me? Fine, do whatever you want.

I explicitly say for people NOT to add anything else to version 1.4 of Gedit HE, I will not take responsibility for what happens.
In your case, the HE still works because it has what I call of a "warning zone". Inside that warning zone, people who know how to work with Gedit via processes will find warnings about the extension of the file. You can add more and more information to the file, however, the "warning zone" will eventually run out of space, and when that happens, the plugin will stop working.

Gedit has a poor architecture, you are not able to see any warnings if you use its GUI. To see Gedit warnings you must open it like a foreground process using the terminal.

Basically, do this:
- Open terminal
- type: "gedit file.j"

After making this simple test, you will see Gedit user interface open and you will read the file. However, in the terminal you will see a huge text, saying that the file has an error, and that the error is "expression is too big" or something like this.

There is a reason why I tell people not to add anything else to the file ... that reason is that the more you add, the more unstable the plugin will be, until it reaches a point of not working at all, and I don't want that to happen.

yeah you are right...
However i found a REALLY nice way to fix this issue ...

Hidden information: Although it took me about an hour to find this fix, since there is nearly no information avaiable about this error... i found it finally ;) ...use prefixes to shrink the definitions: Code: <context id="TriggerRegisterFunctions" style-ref="function"> <prefix>^TriggerRegister</prefix> <keyword>DeathEvent</keyword> <keyword>DestDeathInRegionEvent</keyword> <keyword>DialogButtonEvent</keyword> <keyword>DialogEvent</keyword> <keyword>DistanceBetweenUnits</keyword> <keyword>EnterRectSimple</keyword> <keyword>EnterRegion</keyword> <keyword>EnterRegionSimple</keyword> <keyword>FilterUnitEvent</keyword> <keyword>GameEvent</keyword> <keyword>GameStateEvent</keyword> <keyword>GameStateEventTimeOfDay</keyword> <keyword>LeaveRectSimple</keyword> <keyword>LeaveRegion</keyword> <keyword>LeaveRegionSimple</keyword> <keyword>PlayerAllianceChange</keyword> <keyword>PlayerChatEvent</keyword> <keyword>PlayerEvent</keyword> <keyword>PlayerEventAllianceChanged</keyword> <keyword>PlayerEventDefeat</keyword> <keyword>PlayerEventEndCinematic</keyword> <keyword>PlayerEventLeave</keyword> <keyword>PlayerEventVictory</keyword> <keyword>PlayerStateEvent</keyword> <keyword>PlayerUnitEvent</keyword> <keyword>PlayerUnitEventSimple</keyword> <keyword>TimerEvent</keyword> <keyword>TimerEventPeriodic</keyword> <keyword>TimerEventSingle</keyword> <keyword>TimerExpireEvent</keyword> <keyword>TrackableHitEvent</keyword> <keyword>TrackableTrackEvent</keyword> <keyword>UnitEvent</keyword> <keyword>UnitInRange</keyword> <keyword>UnitInRangeSimple</keyword> <keyword>UnitLifeEvent</keyword> <keyword>UnitManaEvent</keyword> <keyword>UnitStateEvent</keyword> <keyword>VariableEvent</keyword> </context> other good prefixes would be: Get... Set... Add... Unit... Destroy... Convert... Create... you get the idea ...

Glad to hear it =D

If I understood correctly, your solution is "divide" everything into several contexts right?
Well, if that is the case, I am sorry to inform you, I tried that solution before, and it didn't work at the time. It was one of my first tentatives to fix the problem, and it didn't work, at least not for me.
I don't understand how it is possible to work for you ... do you still have that error if you add ALL other functions withing other contexts?
That is weird....

Anyway, unlike most people, you criticized my resource, but you also tried to find a solution. Although it doesn't work (at least it didn't at the time I was creating this) our action is correct, and you deserve a reward.
rep++

you didnt notice that PREFIX-thingy didnt you ????
That cuts downt he size of the actual keywords...
(with Prefix TriggerRegister: "TriggerRegisterPlayerUnitEvent" will result in "PlayerUnitEvent" .. and that will cut down the size of the regular expression, which raises the limit ...for a pretty good ammount)