On my wishlist for it is a completed Doors CS GUI editor (the current one is incomplete, right?) plus new GUI editing features for Doors CS 8, should that prove feasible. Everything else seems pretty polished to me for now.

On my wishlist for it is a completed Doors CS GUI editor (the current one is incomplete, right?) plus new GUI editing features for Doors CS 8, should that prove feasible. Everything else seems pretty polished to me for now.

Well it is incomplete in the fact that it lacks Linux support, but I don't know of any missing features beyond that.

"Always code as if the person who will maintain your code is a maniac serial killer that knows where you live" -Unknown

"If you've done something right no one will know that you've done anything at all" -Futurama

"Have a nice day, or not, the choice is yours." Tom Steiner

<Michael_V> or create a Borg collective and call it The 83+
<Michael_V> Lower your slide cases and prepare to be silent linked. Memory clears are futile.

Oh, since I've opened up the SourceCoder API and will be expanding it even further sooner, I'd love to see some sharing of projects between SC2 and Tokens. I know that Shaun had asked me for that API back in the day, so hopefully it is still useful to him.

The biggest feature I want to get working is the projects. However, I over-engineered it a bit, so I'm basically starting over. I'll start out with a very basic infrastructure and add more as I need it, rather than try to cover all corner-cases. There are also some various bug-fixes I want to get in there. Once those things are done, that'll be a 1.0 release. From there it's improving the DCS GUI editor, adding more file-type support, and finally more calculator support. Along the way I'd also like to learn Axe and Grammer so I can provide tools to facilitate development in those areas, since that seems to be the direction we're headed.

I also want to add some tools (either within tokens or as a stand-alone tool) to facilitate editing the Tokens files; the XML can be kind of a bear to comb through. I also want to move some config into an ini file (such as fonts etc.).

Also also, some sort of integration with SC is indeed something I would like to implement.

Alright, I've made a small update:
- Fixed saving error where it wouldn't save if it was a new file
- Fixed error where if you had a preprocesser directive that was shorter than the replace string it would crash (now it just highlights the line incorrectly )
- Moved some settings to INI file: Font and default tokens file.
- Grammer XML file included in download

I have another update:
- Fixed bug where shift+backspace did not backspace
- Added options dialog to set default tokens file when starting, and to set font:
Startup:
Options dialog (under tools):
After you choose a new font:
Hitting save:
It also saves the INI file so that this persists across instances.

edit by comic: changed [link] to [url]. GinDiamond, you can click the buttons between the post subject and the post message to add proper BBCode to your posts. You can click on "Post Reply" to get to the proper page since "Quick Reply" doesn't have those.

Here's what it looks like, you can see a bit of syntax highlighting, #Axiom and inData(, and perhaps most importantly, the full catalog of Axe commands on the left:

And here's a list of every bug report/feature request I compiled while making it:

▪The second expr( token at 5DF5 should not be included in the xml files
▪Tokens could have multiple groups
▪Closing parentheses, braces, and brackets could match the style of their matched opener
▪Auto-indenting as an option, and some way to make statements like Else indent properly
▪Alt strings do not work if the token has a child token, and giving the child token an alt string throws an ambiguity error
▪Do not open assembly programs (they start with BB 6D)
▪Put site tag hyperlinks in the group/token information pane

Thank you so much for this, Runer, it's great! I've included it in the download as well as addressed a couple of your suggestion:
- Removed the [expr(]
- Fixed alt-strings, I hope
- Prompts if you try to open an ASM program
- Site tab hyperlink in group pane, as well as a tooltip:
- Added commentString and directiveString to XML definition, defaults to "//" and "#", respectively. In AxeTokens.xml I set it to "//" and "@".

Do you mean that when you go through options it doesn't save the INI? Keep in mind that it won't load up that tokens file when you change it through there. If you want it to change for the currently open document, you have to go to File -> Change Token File.

Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.