I already posted this as a comment to http://wiird.l0nk.org/wp/archives/63 (http://wiird.l0nk.org/wp/archives/63) but Link recommended that I post it on the forums. I figured this would be the best place to post it. Ahem:
Quote from: meI have some suggestions.
The text file has poor syntax to the point that it can confuse itself. For example, if you make a comment under a code that reads like a code (though it does have to be the first thing), then when you save the changes, export as text, and import the new text file, that comment you just made is now interpreted as part of the actual code. So if they have a code that has XXXs and such in it, and I want to copy+paste that part to the comments and then make changes, I have to first prefix it with “code to be changed is†or something of that sort in the comments. I would recommend making all comments have some sort of a // or something in front of it, to make sure that never happens.
Speaking of the XXXs, it could be far more sophisticated in that manner. Whenever it detects that there is an abnormal letter in it, it could open up a “variable†text input for that string of letters (it’s pretty much always the same string of letters; if they’re different, they’re different variables) that would be stored in the text file; the code itself would not be modified, rather it would apply the changes when exporting it to GCT; in this way, the variables themselves would never have to be modified out of the code by hand.
One more thing: Often I’ll get a notification about codes being changed and a prompt for whether or not I would like to keep them or some such. “Yes†is pretty much always the answer; I’ve never seen a reason why not. Perhaps allow an option to “always use this answer†so it will just assume I confirm.
Thoughts? Comments? Other ideas?