Curry Kenworthy wrote:

> Although it's quite possible to save data in stack file(s) if you do
> it properly, people who follow that route often have trouble, so I
> discourage it.

Depends what's in the stack file.

The traditional factoring of code, UI, and data became a best practice for good reason.

But stack files can be very versatile storage containers, offering many of the benefits of LSON (LC encoded arrays) but with the addition of being able to contain LC objects as well.

LSON's generally my go-to unless I have a specific need for something else, but once in a while stack files have been a good solution for storage.

There are many storage formats to choose from, and stack files have a place among them. For keeping with the tradition of separating code, UI, and data, it's not the format but how it's used.

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 ____________________________________________________________________
 ambassa...@fourthworld.com                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to