27 Sep
2004
27 Sep
'04
4:36 p.m.
I suggest that you use RuntimePackager. Stripping need not be painful if
you decide on a conservative strip i.e. force the stripper to keep all of
your packages. However, once you have configured the RuntimePackager for
your specific project i.e. whether you had decided on an aggressive strip
strategy or a conservative one the result is an *.rtp config file, that
file from hence on can be loaded into RuntimePackager and then running
through the stripping is simple and fast.
If deploying on Windows one can then use the Reshacker tools to create a
single executable i.e. combining the vm and image and which can be
compressed by usually 50%. For Linux, Mac and the rest of the other 11
platforms that are supported by VisualWorks you will have to deliver both.
The cool thing about running headful is that one does not have to spend
time building tools to support things. Why, because one can use
workspaces, inspectors. For my wikis I use workspaces to do all sorts of
admin stuff , creating users, changing paswords, forcing snapshots, soon
garbage collection of the wiki, etc. If I had to run headless , I would
have to build all sorts of tools. Not to mention, that I can fully debug
and fix issues live. Not bad. Saves me a lot of time. Not every app needs
to run headless and many apps that usually do run headless could run
headful.
VisualWorks has quite a bit of OS support for Windows, just load the
appropriate goodies.
Finally, VisualWorks is more akin to Java i.e. in the sense that there is
the notion of a runtime environment. Dolphin does not. There is only one
environment with them and that is Windows. In the case of VisualWorks it
is possible to create a generic runtime environment (SRE - Smalltalk
Runtime Environment) with the appropriate basic support and then load the
parcels needed at runtime. I had that for something I had built that
allowed one to find parcels in a p2p network and then load them and run.
Cincom will be releasing an SRE in the next official rev, I believe.
RuntimePackager allows one to create custom environments that are specific
to the app in question, that is somewhat less useful because of the amount
of memory and disk storage that modern computers have but I guess if one
is deploying on a pocket pc device perhaps more applicable.
-Charles
On Sun, 26 Sep 2004 20:58:03 +0200, stéphane ducasse
<ducasse(a)iam.unibe.ch> wrote:
On 26 sept. 04, at 20:47, Eric Tanter wrote:
But stripping in VW works we already did that but this can be painful.
No this is a pity because they have Windows native widgets and MS
close
integration. Ok they have 90% of the market with them
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
stéphane ducasse wrote:
We use VNC to connect and then on unix I imagine that exec does that for
you, running a process that is not killing when you exit
your session
Yes this is something called ImageStriper. Look
in the doc they
explain how to deploy an application.
Ok I'll have a look.
Eric you do not have to have all the cincom
distro but I would suggest
you not to strip the image
and keep the UI so that you can access SmallWiki and load update or
other stuff with the debugger and soon.
Yes but then how do I let smallwiki run in the background, even when
I'm logged out ? Watch out this is not always as we would like it
to be :)
it seems :( By the way I saw how to deploy an app with
dolphin Smalltalk and this
is was great:
click on button
click on some button
wait 2 min and boom you get either a dll starting at 256k or an exe
Nice! but this is only for windows, right? something similar for
unix/mac/linux?
-- Eric