Unacceptable File Size Increase

[Dan Shafer]

I'd echo Bill's design suggestion for using a single-card stack which
replaces field contents by reading in a file or database. That file can be a
text file or a MySQL database (flavor depending on your needs) or, as Bill
says, a FileMaker Pro database. That would be a much cleaner solution than
the one you're using, I suspect, and result in an absolutely tiny app.

On 6/28/06, Bill Marriott <wjm at wjm.org> wrote:
>
> Blair,
>
> I am not sure I understand completely what you're doing with your stack,
> but
> two thing pop out at me.
>
> The first is: Have you considered using a database like FileMaker Pro to
> manage the information in your system? This will impose some structure and
> order on what you're doing. It will separate the information you're
> storing
> from the presentation. (So you don't have to go in and "manually" update
> the
> design of all the substacks, for example.) You will still be able to
> script
> things, but you'll find the need for scripting diminished greatly. A free,
> fully-functional 30-day trial is available from
> http://www.filemakertrial.com
>
>
>
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Shafer, Information Product Consultant and Author
http://www.shafermedia.com
Get my book, "Revolution: Software at the Speed of Thought"
>From http://www.shafermediastore.com/tech_main.html