I am currently working every other evening on either Script Edit or FSM Edit. It may sound like I really don't get alot done. I can see how this is perceived when others can produce small applications or missions in a few weeks, but it takes a month for me to fix many bugs.

The truth is quite different "behind-the-scenes" and I will give everyone a quick tour of some of the things I have been working on just to prove how deep this application intends to go.

First, I have been in the process of building a fully object-oriented abstract syntax tree for class-based files. What does that mean, you ask? Well, it basically means I will be able to read (or parse) and class file used in ArmA without the overhead of using complex regular expressions and reading line-by-line. The advantages to this method are that I can read any file and instantly detect problems in the structure and behave responsibly when it comes to either correcting the error or displaying the error. The goal is that I can turn around and read cpp files, fsm files, ext files, etc.. all using the same language tree and develop all sorts of editing capabilities. Others may have produced applications which parse a file and display them fancily in some graphical editor. They then output the edited data into either another file or over-write the existing file. Script Edit is quite different. It can respect comments and user-edited code and even perform undos very effectively. I will agree it is far quicker to make something that simply "parses" a file and then spits out the edited data again... but it is far better to have an editor that works with the file rather than consuming it. it also opens far more doors with far less "bugs".

This has been the bulk of my work. It is a very complex topic and something new to me. The SQF and SQS languages do not perform any syntax checking and thus were far less difficult. Perhaps one day I can extend this concept to SQF and SQS, but I fear that might be beyond my control for now.

Secondly, I have been trying to design an intuitive layout for performing some easy "wizard-driven" editing. For example, the ability to simply drag-drop weapons and ammo into the description.ext file seems like a very cool concept! However, designing a working method that allows for flexibility can take some time. I would seriously like to get things done "right" the first time rather than simply shoving it off until "version 2" as other software vendors might do.

Finally, I have been pretty worn down from coding for another business application at my regular job. It can get really confusing walking from one job to the next and realizing that the code you are thinking of actually belongs in the other program!! Would you believe me if I told you I had nightmares about coding?

I *want* to work on Script Edit/FSM Edit, but it just doesn't pay my bills. So unfortunately, until then.. I am placing it at the bottom of the list even though I wish it were at the top! The reality is that I am pushing forward on it every day regardless. I will not rest until it is finished! I can guarantee everyone that!

Sincerely,

CD

Interesting fact:

The last build of Script Edit consisted of 498 source files in 70 folders at a total of 45mb. This does include icons and images.