Uploading from a RF Engine with password

[RFAndy]

It would be nice if there is a capability to restore the RF Engine image file to a source file by uploading to portal. Password protected on the RF engine would prevent "source code leakage" due to unauthorized personnel.

[kbanks]

The RF Engine does not have the source code to upload.

It only has the compiled binary.

[RFAndy]

I realize that the RF Engine image is binary. It took a compiler to compile a "source code file" into the binary image used by the RF Engine.

Through "creative programming" this process can be reversed. That is, to take the binary image file from the RF Engine and reproduce the image into a source file. (Of course, the source comments won't be there)

PLC's (Programmable logic controllers) had this capability for years!

[glitch]

I realize that the RF Engine image is binary. It took a compiler to compile a "source code file" into the binary image used by the RF Engine.

Through "creative programming" this process can be reversed. That is, to take the binary image file from the RF Engine and reproduce the image into a source file. (Of course, the source comments won't be there)

PLC's (Programmable logic controllers) had this capability for years!

With high-level languages, it will depend on the complexity of the language and compiler. There is not necessarily a 1:1 relationship between a source line, and the sequence of instructions produced, especially if an optimizer is involved. As such it can be very difficult [if not impossible] to reproduce the source form the resultant binary. While you can reverse to some form of source, that will represent the same overall program, the resultant source may not look anything like the original source, in sequence, or individual operations.

PLC's are a quite different scenario. The language is low level, and defines a specific sequence of logic steps. This is quite easily reversed back into source. This would be more akin to programming in assembly language where there is a 1:1 relationship between the source, and the resultant binary.

[RFAndy]

I still believe it could be done but only with considerable effort and resources. It is not that I wanted this feature as a "cool Synapse addition" but to restore any source code files inadvertently destroyed by an overwrite on the PC.

Another way is for Synapse to create a "special upload folder" that would be never be overwritten and would contain every source file uploading into a RF Engine. This way, a user would have a running backup of all of his files. Since the file size is very small, this could be easily accomplished. Just make sure a new upgrade "Install" never overwrites or destroys this folder. Even with a Portal uninstall this folder would still be on the PC to safeguard a users source code.

[mgenti]

Just to clarify to other readers, this thread is what he is referring to where if Portal is installed to My Documents/Portal instead of Program Files/Portal, files will get removed when Portal is un-installed. In the officially released version of Portal 2.4 we plan to have a check to prevent Portal from being installed into the same directory as your scripts. This should prevent this from occurring to any other users.

If users are concerned about losing scripts we would highly recommend using a version control system for any important SNAPpy script.

[RFAndy]

My suggestion, along with your new release, could compliment each other.
You can never have too much "source code protection":):):)