I am inclined to vote against this project. One tool for one
job and all that unixy type stuff. Palm database / PDB
encrypters already exist (I think) and they should be used
for this task. Of course, this comes from an emacs user,
which has been known to contain some amount of bloat...
Anyway, what exactly should be encrypted? The source code?
The UI (Rsrc file)? Probably not the .proj file? All of the
above?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was thinking that just the Source Code Files would be
Encrypted by SrcEdit if a user turns the option on.
Then, SrcEdit would ask for a password (probably the palms
password) to open the file. When Compiling, Onboard ASM
could check to see if the source file was encrypted and then
if it was it could ask for the password and compile if true and
exit if false.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree with mankoff: seems like bloat. However a lesser
option does seem useful: how about a menu option in OnBoardC
that sets/unsets the read-only flag of all the files in a
project? This way you can be reasonably sure your code is
safe when you aren't working on it.... or would that be a
false sense of security and bloat at the same time?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=192791
I am inclined to vote against this project. One tool for one
job and all that unixy type stuff. Palm database / PDB
encrypters already exist (I think) and they should be used
for this task. Of course, this comes from an emacs user,
which has been known to contain some amount of bloat...
Anyway, what exactly should be encrypted? The source code?
The UI (Rsrc file)? Probably not the .proj file? All of the
above?
Logged In: YES
user_id=1058616
I was thinking that just the Source Code Files would be
Encrypted by SrcEdit if a user turns the option on.
Then, SrcEdit would ask for a password (probably the palms
password) to open the file. When Compiling, Onboard ASM
could check to see if the source file was encrypted and then
if it was it could ask for the password and compile if true and
exit if false.
Logged In: YES
user_id=705725
I agree with mankoff: seems like bloat. However a lesser
option does seem useful: how about a menu option in OnBoardC
that sets/unsets the read-only flag of all the files in a
project? This way you can be reasonably sure your code is
safe when you aren't working on it.... or would that be a
false sense of security and bloat at the same time?