As some of you may already be aware, we have begun construction of a new forum as a rebirth of PHO and continuing on into future projects.
This forum is called Silph Co., and can be found by clicking the banner below. We are in the process of transferring some of our old resources, and the forum is open for posting. It will be sad to see PHO go, but we look forward to a bright future with Silph.
The forums here will be moved to an archive, and the url will redirect to the new site in the coming days/weeks.

This is yet another tool made by me, Shiny Quagsire. It's a simple yet powerful script editor designed to be fast, speedy, and cross-platform.

^ That's Linux by the way. ^

Why?
Because the support for Linux, Mac, and BSD's sucks. That's my honest reason for making this (and for porting NSE 2.x to Mono). Also, I prefer working on familiar code, which is why I didn't just port some other scripting editor. Not to mention I wanted to craft an editor from the viewpoint of a programmer/scripter, and thus my editor was born.

How?
SEA is currently written in Java, and uses an SQLite database with information on each individual scripting command available to our current knowledge, which information like it's name, bytecode, description, number of arguments, argument lengths, etc. Using this, it makes compiling, (soon) decompiling, and error checking fast, and efficient.

(Planned) Features

Cross-Platform using Java

Open-Source!

Fast Compiling using SQLite

Error checking

Easy command aliases - Shorten your code to help readability!

Intuitive syntax

and more!

How's Progress?

Compiling - [|||||||||-] 90%, just need to check for bugs!

Error checking - [||||||||||] 100%

Live Error Checking (in text, like a spell checker) [----------] 0%, not too much of a priority, but I'd like some Eclipse/Visual Studio style error checking since I'm going to be using this.

Q&AQ: That sure looks a lot like XSE...A Yes, yes it does. I designed it to be as familiar as possible while still providing useful additions.

Q: When will this be available?A: As soon as I finish the decompiler, and add ROM Writing/Reading

Q: Have you even tested this at all, and how do you test it if you can't write to the rom?A: Yes, I have. Currently it just dumps some bytecode to the console as well as some debugging informations/errors:

then I just copy+paste it into the ROM itself. Here's a pic of the script shown in the screenshot in action!
The newest build supports saving (I think, unless it's bugged...). Just use the Save button and test it in the game.

Q: What's up with the calculator?A: Copy and paste... Copy and paste...

Q: Your editor sucks. Can I suggest something to fix it?A: Sure! I'm always open to suggestions, and if you feel that something in my scripting syntax or UI isn't right, I'll be more than happy to fix it.

Source Code
Currently, the source code is hosted on my GitHub account. You can visit it here.

Ok, so I did a lot of work on the compiler and the decompiler, and I believe it's finally as an "Earlier Than Usual" Alpha stage (That's ETU for short.) The entire source code has been pushed to the GitHub Repository. Some things you need to know when testing:

This is a DEBUGGING ALPHA. Use at your own risk on your hacks.

Freespace checking has NOT been added yet, so it'll just overwrite at it's pleasure.

The logger - This can save a log with VERY useful information to me or any other bugfixers.

The debugger - The little VBA icon will save your ROM with the byte modifications to a temporary location so you can test it without writing. The changes will NOT be written until you press the Save button. It opens it with the default emulator for your system, so you must have it set to VBA by default.

The decompiler - This can give some useful output as well. Since the decompiler doesn't have hardly as many bugs as the compiler, you can often determine if the script will work just by decompiling.

And since this is a new script editor, feel free to ask questions! If something confuses you, I'll be happy to help.

This is cool and looks much simplifier than XSE I will try to use this when it's released.

I'm noticing something and all te Icons look like the one's from XSE haha, but those are ok.

And if you're looking for suggestions why not something like just clicking a button to make the script you just have to type in the pointer of the script and the things in it like the text and movements.

And a test button should be great you click it and opens up the Emulator and plays your game...

Still, it's progress! I just need to parse and format the msgbox command, as well as text, sections, and other things of that sort.

Quote:

Originally Posted by tajaros

This is cool and looks much simplifier than XSE I will try to use this when it's released.

I'm noticing something and all te Icons look like the one's from XSE haha, but those are ok.

And if you're looking for suggestions why not something like just clicking a button to make the script you just have to type in the pointer of the script and the things in it like the text and movements.

And a test button should be great you click it and opens up the Emulator and plays your game...

Suggestions noted. For applymovement I'll have something that makes it more automated. The test button isn't too hard to add, and I can probably add that while I still have Eclipse open.

And also why not have in game notes or something? Like there's a part in the program where the pokemon list is and the scripter can just look on that and copy the value. Or make things like RBH files...

Very very nice. I plan to try this out, although XSE is doing everything I need. This editor you are working on really looks like it will go a very long way though in which case it will be my new default script editor.
Also looks like I will have to re-learn a few terms script-wise but that is no problem. Good luck, although I'm sure you won't need it!