From: Erik Veenstra <google@...>
Date: 2005-06-24T00:35:37+09:00
Subject: Re: Packaging dillema

> > I just realized that using Rubyscript2exe with sqlite
> > probably isn't a good idea, since the database disappears
> > once the application gets shut down, and I need the
> > database to persist between application launches. Hm.

Don't mix user files with application files. A lot of Windows
application do this, but it is imply bad behaviour. Both worlds
(user space and application space) have to be seperated.

> My solution was to create the exe, and bundle it in a zip
> file with sample scripts and a default config file. The
> installation was basically to unzip the bundle to create the
> application directory structure and default files, then just
> run the main app exe.

Or create a user directory full of templates, simply by
unzipping an embbeded ZIP file. Or use Tar2RubyScript to create
an RBA which includes the application and the templates
directory (but not the shared objects!...) and copy this
template directory to user space the first the application is
started.

> I believe that the executable created by Rubyscript2exe knows
> from what directory it is launched, so the code kicked off it
> could figure out where to look for script files relative to
> its execution point, and where to write out any logs.

This is correct. The internal command "ruby app.rb" is started
in the same directory as the user started "app.exe".

gegroet,
Erik V. - http://www.erikveen.dds.nl/