[Seaside] Options to distribute Squeak (Seaside) app
carlg at libertybasic.com
Tue Dec 4 02:51:57 UTC 2007
But if you strip out the right development tool stuff when you package your
app that can make it very hard for people to look at the decompiled
bytecode. Remove inspectors, browsers, the decompiler, etc. and also make
sure that no Smalltalk code can be filed in so that the tools can't be added
back in. You should be okay in theory against most would be hackers. The
only way to examine the application then would be to have some sort of image
file browsing tool.
-Carl Gundel, author of Liberty BASIC
From: "David Mitchell" <david.mitchell at gmail.com>
> FAQ: Distributing Squeak Programs
> Omitting the source is easy, don't distribute the .sources and
> .changes. But, someone with Squeak can get at your "bytecode" and look
> at it in a code browser. The variable names all get dropped, as do the
> comments, but the code is easy to read.
> You can preview this by removing your .sources and .changes file.
> Back when Smalltalk was more commercially successful, you'd see ads
> for Smalltalk obfuscators. I haven't seen such a thing for Squeak.
> On Dec 1, 2007 11:32 PM, itsme213 <itsme213 at hotmail.com> wrote:
>> I will have a Squeak app that uses Seaside. It will not be offered
>> but users will get a copy of it in some form to install and use.
>> Starting with my working Squeak image, what options do I have to:
>> - make the source code hidden (byte-code level stuff is fine)
>> - optionally: offer it to them as a single Windows executable
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside