Portable Code Editors question

[cmorgan]

I think I tried this a few years ago, but I might as well give this another shot.

Challenge - a single code editor that can be installed as a portable app to an 8GB flashdrive and run on both Win7 and a Snow Leopard Mac machine.

Caveats - no software can be installed on the mac (networked machine).

Scope of Use: simple editing, searching, multi-file search|replace, syntax highlighting, limited column editiong (or line prefixing|suffixing), bonus for line joining and splitting and line numbering. I do not need to compile, run, test, use VMs, or decompile, as this is strictly manual editing and checking weidu and html based files (.d,.tp2 ,.htm, .html, .xml, all the baby stuff that goes along with making and distributing i.e. mod files, minus the actual packaging or referencing BG2/Tutu).

Current workaround - data files only on flashdrive; TextWrangler used on mac, Notepad++/Crimson Editor/Textpad/Wildedit/ConTEXT/PSPad available and utilized at different times on Win7 at home.

This setup is OK, but in the best of all possible worlds I would focus on one editor that I could build auto-completion, customized syntax, etc. for and use on one low-footprint "modding stick" that would go between platforms anywhere I go, and be of use. (Actually, in the best of all possible worlds, someone would make a version of NotePad++ that would run on both sides of the Win/Mac fence, portably!)

Ruled out - no "cloud computing" internet connection-required apps, because (quite rightly) work does not want to open a loophole for access to such things at my school just so I can play around during my lunch time or down-time.

Does anyone have a creative solution or ideas?

[the bigg]

jEdit is written in Java, and might be more portable (if Macs have Java installed out of the box). I don't know how many advanced features jEdit has, though.

[Miloch]

(Actually, in the best of all possible worlds, someone would make a version of NotePad++ that would run on both sides of the Win/Mac fence, portably!)

Doesn't it? It claims to, though that probably just means it runs through wine or something.

Otherwise yeah, maybe jEdit, though you'll probably need separate installers/instances for both OSes.

[cmorgan]

jEdit looks good, thanks - I am still working on getting the Mac side fully portable, but the OSX version opens fine on Win7  ( rather, the .jar seems to be able to find all the paths it needs without any hassles) and the syntax highlighting is very configurable. I think I can get this rolling.

[cmorgan]

these are now all valid, right?

READ_STRREF_F
READ_STRREF_S
READ_STRREF_FS
GET_STRREF_F
GET_STRREF_S
GET_STRREF_FS
RESOLVE_STR_REF
THIS
STHIS
FILE_IS_IN_COMPRESSED_BIF
SOURCE_BIFF
IS_COMPRESSED_BIFF

[the bigg]

Yes. FILE_IS_IN_COMPRESSED_BIF has a synonim in FILE_IS_IN_COMPRESSED_BIFF, which is in fact the form I'd recommend (mostly because all other commands use BIFF and not BIF).

[cmorgan]

way cool - one more check (and i am still missing some of the new stuff, as i am running through this just to get my feet wet):

SAY UNHAPPY_BREAKING_POINT as a declared value?

(I will make BIFF instead of BIF the value, as if someone is actually using a syntax highlighter, it probably ought to reinforce the usage you want. Going back for more of the things like ASCIIT and ASCIIE.)

[the bigg]

Self-initialized variables is the union of stuff at the bottom of src/var.ml and the result of grep Var.set src/* | grep [A-Z][A-Z] | sed -es'/[^"]*\"\([^"]*\)\".*/\1/g' | grep -v KITLIST | grep -v PROJECTL | sort | uniq (unsorted, some variables will only be printed if you ran the compile process).
D keywords are near the top of src/dlexer.mll (unsorted).
TP2 keywords are somewhere in src/tlexer.mll (right after 'PUT LEXICON *)'; again, unsorted). tlexer.mll is only created during the compile process.

If this was too easy to follow I'll make sure to post a procedure that requires the sacrifice of a goat to complete.

[devSin]

Don't forget the built-in macros!

[cmorgan]

I think I almost understand - but let me mess with it anyways, as I am learning and having fun!

(And this editor is pretty easy to reconfigure. I am liking <KEYWORD1><![CDATA[<MONTH>]]></KEYWORD1> and simple xml stuff allowed in the processing; also, with a quick .bat on Win7 of  java -Xmx2048M -Xms2048M -jar jedit.jar this puppy just id a grep of every .d file in every subdirectory of my testing install pretty darned quickly. I know that is resource dependent, o no way it ill work loading all that stuff into memory at work, but on my machine, it is darned quick).

[cmorgan]

@devSin - working on 'em, too - still trying to sort all that out using the docs and checking against the in-progress stuff and such. So far, some of them have ended up in the same keyword group as WRITE_*  ADD_* REMOVE_* instead of the <FUNCTION> set, like DEFINE_ASSOCIATIVE_ARRAY  FOR OUTER_FOR etc. - trying to make it easier for beginners to see READ stuff in one color like green, and WRITE stuff in red, and things that require heavy duty specific additional input defined as <FUNCTION>. (Silly, i guess, because beginners aren't likely to use this editor in the first place ).

I'll post so you can pick at it - I'd rather have a general usable form and make my own edits for my own misunderstandings.

[Mike1072]

You're already familiar with the different groupings I tried to achieve in my Notepad++ .tp2 highlighting:

* TP2 actions (COPY)
* TP2 patches (SAY)
* "patch expressions" - commands that return a value (STRING_EQUAL)
* control flow statements (FOR)
* parameters for actions or patches (EXACT_MATCH)

I find the code easiest to understand when it is highlighted according to how it is interpreted.

I wouldn't highlight the built-in macros or variables, but that's a matter of taste.  The WeiDU constants should probably be highlighted, but I didn't bother to do so in my N++ stuff because I had limited room and I never use them.

jEdit's custom syntax highlighting looks more powerful than any other I've seen.  .baf and .d could have separate definitions, and .d could potentially look up .baf's list of triggers and actions just for the text within IF ~blah~ and DO ~blah~.  I'll continue looking into this, maybe port my definitions over....

[cmorgan]

I just found yours again, and I agree - I am rebuilding accordingly. I have been plating with the scope definitions, and I bet with your skills, you could breeze through a really strong one. I have been looking at the C one, where combining scope and regexp looks like it might be possible to have one set of definitions... Never mind, you will see it when you look! I like everything possible highlighted, to catch typos in standard resources, but I would rather expand extra stuff from a base that makes sense from a programming perspective more advanced than my own ( it helps me learn).


Have you taken a look at the autocomplete and abbreviation materials? I am ok with the manual folding, as trying to fold weidu is not going to really be able to be accomplished without creating some sort of dummy token (BEGIN with no END for components, for example) so I'm not investigating that right now. Right now, I am still trying to get it to use case sensitivity for one set of keywords but not for another, so things like resources that don't need it don't have to have two entries, one uppercase and one lower.

[cmorgan]

OK, puttering -

first try at  this xml file for weidu_tp2, based on Mike1072's organization

firts try at this xml file for weidu_dbaftra, based on my own meanderings

still missing some stuff (I will try to sit down this weekend and figure out what did not make it in).

The good news - even though I can't run terminal at work, the .jar loads fine, and works well. It dumps a small .ini file in a user library/subdirectory, but other than that, no footprint to speak of. I have been able to work back and forth cross-platform with only one silliness (I have not yet figured out how to remap the settings folder so that once I set syntax highlighting colors it will remain in effect between sessions, but eventually I will figure it out).

I like the (mis-)use of the different defined highlighting groups; I was able to separate BG2 from ToB materials, though that needs a second pass on the actions and triggers that are ToB specific since I only separated the areas, scripts, and dialogs.

The really good news for true programmers, not poke-abouts like me, is that if you are good at regexp you might be able to make a decent context-sensitive syntax highlighter which can do things like only highlight your variable when the scope is correct, if you have defined it -

so
"c-aranvisits","GLOBAL"
gets highlighted only if you type that, not
"c-aranvisits","LOCALS"

or perhaps inlined files are parsed with weidu_dbaftra within your .tp2 (the html parser sent already does this for Java, so that java script within html is recognised and highlighted accourding to its own rules).

Way too much for what I need, but I can see how to approach it. I was even able to use them to find a few areas in code where I had mismatched scope or mismatched variable name, just by a glance through the colors. Seems pretty cool.

[devSin]

You could put Near Infinity on the drive too. We use only the system java.util prefs (registry on Windows, and a plist in ~/Library/Preferences on Mac OS X).

[Mike1072]

.tp2 definition here

Updated with indenting, strings, array highlighting, inlined files, proper number recognition (binary/octal/decimal/hex).  No folding stuff done (not sure if possible without a plugin; default indentation method does a great job if code is properly indented - except we don't usually indent entire components).  Also added case insensitivity for the MODDER options, set up so they work if specified all on one line (since MODDER doesn't have an END signifying the end of the option list).  Might be possible to do case insensitive resource names fairly easily (providing modders aren't lazy and actually use string delimiters).  Added hopefully all of the WeiDU commands not accounted for, but haven't yet checked to see if everything's in the best group (I had to move some things out of LITERALs because rules weren't registering them properly there).

I think .tra could use a separate definition - it's extremely easy to import rules from one to another, and the separation allows for greater control.  So, I renamed the dbaftra one to dbaf (relevant because of inlined files).

[cmorgan]

Nice! I am poking at yours, learning your rules sequence. I agree on the .tra split, too - he only .tra specific stuff are the tokens, anyways. No need to fight to add them, when it would be the simplest defiinition file ever.

[cmorgan]

the "Clipper" plugin tursns out to be so simple even I can customize it - | is where the cursor ends up, and you just write the code out with \n for newline, and spaces for spacing:

a quick and dirty application of it I threw together t play with this afternoon:

Code: [Select]

#
# WeiDU dialog clip library
#

@title=WeiDU Dlg
@sortClips=true
@caseSensitiveSort=false

# comment
(/**/)=/* | */

# standard blocks
ARAN_VARSTART=IF ~CONDITION~ THEN BEGIN statename\n  SAY ~[ARAN] |~\n  ++ ~[PC] narcissistic~ + reply_1\n  ++ ~[PC] compassion~ + reply_2\n  ++ ~[PC] practical~ + reply_3\n  ++ ~[PC] inappropriate~ + reply_4\n  ++ ~[PC] exit_talk~ + reply_5\nEND
ARAN_REPLY=IF ~~ statename\n  SAY ~[C-ARAN] |~\n  ++ ~[PC] narcissistic~ + reply_1\n  ++ ~[PC] compassion~ + reply_2\n   ++ ~[PC] practical~ + reply_3\n  ++ ~[PC] inappropriate~ + reply_4\n  ++ ~[PC] exit_talk~ + reply_5\nEND
TELDRA_REPLY=IF ~~ statename\n  SAY ~[C-AW01TL] |~\n  ++ ~[PC] narcissistic~ + reply_1\n  ++ ~[PC] compassion~ + reply_2\n  ++ ~[PC] practical~ + reply_3\n  ++ ~[PC] inappropriate~ + reply_4\n  ++ ~[PC] exit_talk~ + reply_5\nEND
ARAN_EXIT=IF ~~ statename\n  SAY ~[C-ARAN] |~\n  IF ~~ THEN EXIT\nEND
TELDRA_EXIT=IF ~~ statename\n  SAY ~[C-AW01TL] |~\n  IF ~~ THEN EXIT\nEND
SAGE_REPLY=IF ~~ statename\n  SAY ~[C-AWSAGE] |~\n  ++ ~[PC] narcissistic~ + reply_1\n  ++ ~[PC] compassion~ + reply_2\n  ++ ~[PC] practical~ + reply_3\n  ++ ~[PC] inappropriate~ + reply_4\n  ++ ~[PC] exit_talk~ + reply_5\nEND
ARAN_CHAIN=CHAIN C-ARAN statename\n~[C-ARAN] |~\n== CERNDJ IF ~InParty("Cernd") InMyArea("Cernd") !StateCheck("Cernd",CD_STATE_NOTVALID)~ THEN ~[CERND] ~\n== EDWINJ IF ~InParty("Edwin") InMyArea("Edwin") !StateCheck("Edwin",CD_STATE_NOTVALID)~ THEN ~[EDWIN] ~\n== HAERDAJ IF ~InParty("HaerDalis") InMyArea("HaerDalis") !StateCheck("HaerDalis",CD_STATE_NOTVALID)~ THEN ~[HAERDALIS] ~\n== JAHEIRAJ IF ~InParty("Jaheira") InMyArea("Jaheira") !StateCheck("Jaheira",CD_STATE_NOTVALID)~ THEN ~[JAHEIRA] ~\n== JANJ IF ~InParty("Jan") InMyArea("Jan") !StateCheck("Jan",CD_STATE_NOTVALID)~ THEN ~[JAN] ~\n== KELDORJ IF ~InParty("Keldorn") InMyArea("Keldorn") !StateCheck("Keldorn",CD_STATE_NOTVALID)~ THEN ~[KELDORN] ~\n== KORGANJ IF ~InParty("Korgan") InMyArea("Korgan") !StateCheck("Korgan",CD_STATE_NOTVALID)~ THEN ~[KORGAN] ~\n== MAZZYJ IF ~InParty("Mazzy") InMyArea("Mazzy") !StateCheck("Mazzy",CD_STATE_NOTVALID)~ THEN ~[MAZZY] ~\n== MINSCJ IF ~InParty("Minsc") InMyArea("Minsc") !StateCheck("Minsc",CD_STATE_NOTVALID)~ THEN ~[MINSC] ~\n== NALIAJ IF ~InParty("Nalia") InMyArea("Nalia") !StateCheck("Nalia",CD_STATE_NOTVALID)~ THEN ~[NALIA] ~\n== VALYGARJ IF ~InParty("Valygar") InMyArea("Valygar") !StateCheck("Valygar",CD_STATE_NOTVALID)~ THEN ~[VALYGAR] ~\n== VICONIJ IF ~InParty("Viconia") InMyArea("Viconia") !StateCheck("Viconia",CD_STATE_NOTVALID)~ THEN ~[VICONIA] ~\n== YOSHJ IF ~InParty("Yoshimo") InMyArea("Yoshimo") !StateCheck("Yoshimo",CD_STATE_NOTVALID)~ THEN ~[YOSHIMO] ~\n== IMOEN2J IF ~InParty("Imoen2") InMyArea("Imoen2") !StateCheck("Imoen2",CD_STATE_NOTVALID)~ THEN ~[IMOEN] ~\n== AERIEJ IF ~InParty("Aerie") InMyArea("Aerie") !StateCheck("Aerie",CD_STATE_NOTVALID)~ THEN ~[AERIE] ~\n== ANOMENJ IF ~InParty("Anomen") InMyArea("Anomen") !StateCheck("Anomen",CD_STATE_NOTVALID)~ THEN ~[ANOMEN] ~\n== C-ARAN ~[ARAN] ~\nEND\n++ ~[PC] narcissistic~ EXTERN C-ARANJ reply_1\n++ ~[PC] compassion~ EXTERN C-ARANJ reply_2\n++ ~[PC] practical~ EXTERN C-ARANJ reply_3\n++ ~[PC] inappropriate~ EXTERN C-ARANJ reply_4\n++ ~[PC] exit_talk~ EXTERN C-ARANJ reply_exiting

# conditions
ARAN_OK=InParty("c-aran") InMyArea("c-aran") !StateCheck("c-aran",CD_STATE_NOTVALID) |

# special blocks
EVIL_LEATHER=/* LEAT21 - Human Flesh +5 evil armor equipped complaints */\n  IF ~HasItemEquiped("LEAT21",Player1) Global("c-arskinarm","LOCALS",0)~ THEN GOTO a1799\n  IF ~HasItemEquiped("LEAT21",Player1) Global("c-arskinarm","LOCALS",1) GlobalTimerExpired("c-aranskin","GLOBAL")~ THEN GOTO a1798\n  IF ~HasItemEquiped("LEAT21",Player1) Global("c-arskinarm","LOCALS",2) GlobalTimerExpired("c-aranskin","GLOBAL")~ THEN GOTO a1797|
ARANS_CLASS=  + ~Class("c-aran",THIEF_ALL)~ + ~[PC] |~ + reply_aran_thief\n  + ~Class("c-aran",MAGE_ALL)~ + ~[PC] ~ + reply_aran_mage\n  + ~Class("c-aran",CLERIC_ALL)~ + ~[PC] ~ + reply_aran_cleric\n  + ~Class("c-aran",FIGHTER_ALL)~ + ~[PC] ~ + reply_aran_fighter
PC_RAND3=\n  + ~RandomNum(3,1)~ + ~[PC] |~ + rand_reply_31\n  + ~RandomNum(3,2)~ + ~[PC] ~ + rand_reply_31\n  + ~RandomNum(3,3)~ + ~[PC] ~ + rand_reply_33
PC_RAND4=\n  + ~RandomNum(4,1)~ + ~[PC] |~ + rand_reply_41\n  + ~RandomNum(4,2)~ + ~[PC] ~ + rand_reply_42\n  + ~RandomNum(4,3)~ + ~[PC] ~ + rand_reply_43\n  + ~RandomNum(4,4)~ + ~[PC] ~ + rand_reply_44
PC_RAND5=\n  + ~RandomNum(5,1)~ + ~[PC] |~ + rand_reply_51\n  + ~RandomNum(5,2)~ + ~[PC] ~ + rand_reply_52\n  + ~RandomNum(5,3)~ + ~[PC] ~ + rand_reply_53\n  + ~RandomNum(5,4)~ + ~[PC] ~ + rand_reply_54\n  + ~RandomNum(5,5)~ + ~[PC] ~ + rand_reply_55


[cmorgan]

...and with the TextAutoComplete plugin, if you configure the settings to remember 5000 words and click on the box that checks the buffer for existing highlighting, then you have an automatically populated autocomplete of all of your predefined weidu keywords, etc. - so no separate auotcomplete editing or creation necessary. Add your mod stuff to the standard highlighter, and when you load up your .d file and start typing, everything you thought was important enough to add to the syntax highlighting operates like modern mobile OS stuff, only better - it works as a programmer's editor, so you get options. Start typing Gl, and all the weidu stuff that starts with those letters pops up underneath your typing - keep typing and it refies it, or simply hit the number key listed next to the one you want.

Now if only I could get my brain to move as fast as the tool supports, and I could *really* crank along. Thanks for the reference, guys - I am very impressed. It might not autocode SSL and drop predefined recursive iterative PATCH_IF statements, but as a dialog coding tool it is just absolutely out-of-this-world easy to set up and customize. For incredibly slow typo-prone typers like me, this completely rocks.

devSin, you are right about NI, too - I can confirm drag'n'drop of a BG2 directory and the newest nearinfinity.jar operate crossplatform on a flashdrive. So I can install a test version onto a vanilla game, drop the copy onto the flashdrive, and then if i get 5 minutes at school to just poke about,  I can search for whatever I need in terms of troubleshooting, even though i am working with Win7 as a primary system and snow leaopard as a primary work system.