Prev: high-water-mark memory management
Next: TCL scripting help
From: Donal K. Fellows on 2 Mar 2010 10:47
On 1 Mar, 19:36, drscr...(a)gmail.com wrote:
> When I distribute a script and the end users receive it, I want to
> discourage them from editing it.  Plain ascii just challenges the users
> to open and hack things.  So, I can give them just the compiled script
> without any concern.  (Not as app's either because these are small
> scripts, there are many of them and by themselves alone they do nothing.)
>
> So, it is not possible to compile scripts and splice them together?

The easiest way (if you only want "light" protection) is to make a
starkit out of your sources. Like that, they need a somewhat
specialist tool (sdx) to get the sources, so keeping grubby fingers
out of where they don't belong; anyone who knows how to take things
apart is probably able to take being told "you broke it, you get to
keep the pieces". You can even combine the starkit with a tclkit
binary to make a starpack single-file executable, which is quite
possibly the neatest way of all to distribute to users. If your users
are going to have ActiveTcl installed, that also knows how to run a
starkit (with .kit extension) directly without starpack-ing.

If you need heavier protection than a starkit/starpack, go for the
products that ActiveState sell. (Some of what they offer is actually
based internally on the tclkit/starkit technology, but with additional
steps.)

Donal.
From: drscrypt on 2 Mar 2010 10:58
ddd wrote:
>
> You can also have a look at http://pdqi.com/w/pw/pdqi/Wize/Wize , which
> includes a compiler (http://pdqi.com/w/pw/pdqi/Wize/Compiler) for Tcl in a
> kind of kit distribution for Tcl.
>
>
>


Thanks, this comes very close to what I had in mind.


DrS

From: drscrypt on 2 Mar 2010 11:04
Donal K. Fellows wrote:
> The easiest way (if you only want "light" protection) is to make a
> starkit out of your sources. Like that, they need a somewhat


Thanks to all who responded. I am familiar with the starkits and AS
products - I am actually using TDK. I just wanted to be able to ship or
rather to include tclcompiler it comes with in my editor app - but I
believe it is not allowed. The starkits or starpacks are not suitable
here because the ultimate choice of what proc get included is up to the
user. No big deal.


DrS

From: MSEdit on 3 Mar 2010 03:24
On Mar 2, 5:04 pm, drscr...(a)gmail.com wrote:
> Donal K. Fellows wrote:
> > The easiest way (if you only want "light" protection) is to make a
> > starkit out of your sources. Like that, they need a somewhat
>
> Thanks to all who responded.  I am familiar with the starkits and AS
> products - I am actually using TDK.  I just wanted to be able to ship or
> rather to include tclcompiler it comes with in my editor app - but I
> believe it is not allowed.  The starkits or starpacks are not suitable
> here because the ultimate choice of what proc get included is up to the
> user.  No big deal.
>
> DrS

How does the choice by a user stop you using starkits ?

A starkit is just a "zipped" archive of a filesystem, it could contain
several different copies of a proc which are used depending on what
the user does.

On the Wiki someone has a starkit that autoconfigures its contents
over the internet depending on what options the user has used (a sort
of prefetch proc cache) which guarantees that the user always has the
latest version of the procs.

People have even used sqlite as a back end to store the procs used in
the application, and use 'unknown' to fetch them out.

TCL is limited only by your imagination.


Martyn
From: Larry W. Virden on 3 Mar 2010 07:11
On Mar 3, 3:24 am, MSEdit <mse...(a)gmail.com> wrote:
>
> TCL is limited only by your imagination.
>

And that's an important point to remember. Many time, a developer
would rather not have to imagine a new deployment mechanism, but
instead, use something already implemented, tried and tested and shown
to work in the field. While various people may have implemented a
variety of dynamic deployment, this developer may not know where to
find code to do that sort of thing. It would be great if code, or URLs
to code, implementing such techniques were to become generally
available.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: high-water-mark memory management
Next: TCL scripting help