ambassador at fourthworld.com
Wed Feb 27 10:36:38 EST 2008
Dale Pond wrote:
> Thanks to all of you for your suggestions and detailed discussion on
> the Auto Save feature.
> I did implement it (save this stack) into my stack indexing scripts
> and it works perfectly. The stack is now auto saved after indexing
> all the cards in the stack which is done after I add a new card(s).
Glad that worked out.
> Reckon I feel a bit sheepish after that simple script command -
> probably still have my head up HC's ...
No need to feel sheepish. When I first started using Rev in '97 (back
when the engine was called "MetaCard") I was convinced it was wrong
wrong wrong on so many counts. In my book, if it didn't work like
SuperCard it was just stupid. :)
Thankfully the good folks on the list helped me understand the "why"
behind the differences, and with their patient assistance I came to not
only understand how to use Rev well, but also to appreciate that in many
ways it's a more flexible tool.
Perhaps the only thing harder than learning is unlearning. With the
varied experience of the folks on this list, this is a valuable resource
for both processes.
> PS: Filemaker also auto saves...
Yes, most apps that page portions of the file from disk have no choice,
and so they can't offer that choice to the developer. There are many
more, including SuperCard.
For apps like iTunes auto-save is a good fit, and as you've seen you can
have that behavior with minimal effort.
But if you're making something like TextEdit you'll want traditional
document behaviors, and with Rev you can have those too.
I know it sounds awfully trite, but in my experience it's true: with Rev
you can pretty much have it all.
Like Rule #1 in Apple Human Interface Guidelines: the user is in control.
Managing Editor, revJournal
Rev tips, tutorials and more: http://www.revJournal.com
More information about the Use-livecode