Board Thread:Suggestions and Ideas/@comment-24191375-20141119065634/@comment-24191375-20150101171716

Lumage wrote: If it's supposed to be a desktop environment for PTC, why would it have commands or features that PTC doesn't fully support?

As for shortening variables: what if you wanted the code to be readable when exported? A finished product doesn't need as much readability (you'd keep the other copy around for bugfixes), but you can't assume that people would rather have the tiny efficiency boost. At any rate, http://www016.upp.so-net.ne.jp/Khnum/petitcom/SBReduce.html is already there for shortening (but not at the variable level).

Besides the program editor, all the development features in PTC are written in SmileBASIC. You could easily make more advanced versions of them in PTC. My idea is that the code used in the environment should be easy to read, but sacrifice the exported code's readability for space saving, and efficiency, even if it's a small amount, I thought this could add up in large programs. The code you should share is the original code, but the QRs will be of the exported code. There could be a checkbox to disable the variable shortening and altering. There could be other features in the environment that it coulde be used for instead, or just code straight up SmileBASIC. Oh, and the main purpose of the shortened variables isn't for the effiiciency boost, it's for space saving.

I don't have any idea of how much this would help, though. It makes me wonder how much this is worth trying to make.