Script editor

I'm glad that somebody tried it at least. I feared that there wasn't much trust in a newcomer like me who suddenly distributed an exe.

If there are any comments, any requests for changes, or any bugs (not with PN itself ofcourse ), just let me know here. I've already said that it's still crude. It's colorcoding is somewhat limited because I used the default cpp lexer, which didn't like many different keyword classes. So, if there are request to have more different colors for more things (example: now, variable definitions and function definitions are in the same keyword class, it can be splitted to have 2 sorts of keywords classes) or when I find it would be much better to have more keyword classes, I'll attempt to write a new lexer.

Okay, I guess that unzipping it worked just fine? I assumed that it didn't need a registry entry to be able to run, but I wasn't really sure. I did a test when I unistalled PN and unzipped it. It worked, but there is a chance that that is because my first PN version was a version without uninstall information (aka: some lost registry entry). Or did you just download PN from it's official site and putted the scheme file in it's right dir? If so, then I can better distribute a zip with the installer and the scheme file.

Now that I come to think of it, PN can use tools. So, perhaps it's possible to configure it so that the scriptparser will be used by it? Then you've one integrated development platform, writing and compiling code in the same program. But that's something that I need to figure out how to. I suppose that I also need commandline parameters to make it run, but these arn't really available, are they? Oh well, it's something that *could* be possible, but I never did something like that before. I'll take a look into it.

Annyway, thanks already for trying it out

EDIT: Blasted! I just tried out to use the scriptparser as a tool. It works, but it only takes a relative path (=> \blabla\script.txt) as a parameter, not an absolute (=> C:\yadeyade\blabla\script.txt). Or I'm doing something wrong, but I doubt that . Oh well, I'll experiment a bit further now.

Hehe, I did it! I wrote a simple batch file that integrates the ScriptParser into Programmers Notepad. I uploaded PN with scheme and now with the batch file again [URL=http://rapidshare.com/files/13044029/PNForSEV.zip.html]here[URL]. Pitty enough I don't have the time currently for making a quickinstaller, I hope I will do soon, when I've more time. So, that's why I give here step by step instructions *with* pictures

Step 1: put the SEV.bat file in the Utilities\scriptparser directory (the same directory as the scriptparser)

Step 2: We are going to add a tool (the scriptparser). Goto the "tool" menu and select the "options" tab.

Step 3: Goto the tool entry (circled by red) make sure that the scheme is set to the SEV Script scheme (if not, the tool is used by another scheme, you can however make it a global tool, but since I didn't wanted to mix my SEV tools with my more profesional toosls, I only made it a scheme local one) and click then on "Add" (circled by red).

Step 4: The most difficult step: Give it a name (I gave mine the name "Compile SEV Script", at command, click on the button with "..." on it, locate the SEV.bat file that sits in the scriptparser directory, and use it. Then, goto the Folder line, and enter there the same path as above, but without the SEV.bat. Then, enter with parameters "-s %d %f %n" and click ok

Step 5: Use your new SEV Scripting IDE. it can compile from annywhere and will give feedback in the output window.

I hope you'll enjoy it! And I hope that I can find the time to make a one click installer that does everything for you. But for now, this has to work.

Oh, and if somebody finds a bug with it, or when the batch doesn't want to run, let me know it. I can test it only on 1 computer here, so I don't know if it will run everywhere. And of course I can always have made a mistake.

Hehe, thanks! It's just that when I seek for a tool, most of the times it's usage and setting the right settings is so obscure/not documented that I ditch it. Now, since I do know that this is far from an open source users/writers community, I assume that they are less willing to spend much time in figuring out how it works, that's why I make that step by step guide.

Annyway, I'm currious what the experiences are with the 'IDE' (PN + Compile anywhere batch file)? If someone who uses (if annyone for that matter) would be so kind to say if it works like it should be (editing + using the compiler without hassle) or if something is broken (I'm not very good with batch files, so, I could perhaps have used commands that are only supported by win XP, etc) or if something needs improvement (more colors for different keywords for example).

Annyway, I hope I'll recieve some feedback on it's use. I did spend some time to get it working here, now I would like to know if it works over there