At 11:49 AM -0700 8/7/2001, Carsten Levin wrote:
>1) Are there any crucial arguments against saving as files?
Only that it's a less (for lack of a better word) encapsulated solution.
Providing a runtime with a program file can sometimes confuse users more
than providing a double-clickable app.
>2) Is it legal and is it technically OK to use the free downloaded
>Revolution as the distributed engine for those solutions?
I think so, so long as you're not selling it, but Kevin will have to give
the definitive answer on this.
>But we need to be able to retain new information in the solution - which
>is not possible when saving everything as a runtime stack with substacks.
Have you thought about storing the information in a separate file (text or
stack, depending on your needs) and reading it in on preOpenStack when your
application starts up? The external, changeable file can be stored
somewhere handy (in a "Data" folder in the same folder as your app, etc.)
and written and read as needed. This would let you distribute as a
standalone application while still retaining the ability to save settings
and information that will affect the app.
--
Jeanne A. E. DeVoto ~ [EMAIL PROTECTED]
http://www.runrev.com/
Runtime Revolution Limited - Power to the Developer!
