Legacy stack woes II

Rob Cozens rcozens at pon.net
Thu Jun 7 10:39:57 EDT 2007

Hi All,

New issue:

Standalone settings for Legacy stacks are stored in separate "Config" 
stacks, while those settings are internal in the current stack format.

If one is distributing a stack to be used by developers to build 
standalones (eg: SDB_Server, SDB_Utilities):

* If saved in legacy format, standlone settings are lost regardless 
of stack format

* If save in current format, the stack is unusable to Linux developers

* If the config stack is included, Legacy developers can build 
standalones immediately, whereas developers working in current stack 
format must convert the stack to current format, open & interpret the 
config file, and add the settings to the stack.

* The best solution requires maintaining different download archives 
for each stack format, and including the config stack with the Legacy 
download  (or providing both stack formats in the same archive for 
stacks that are standalone templates).

Suggestions or comments?

Any clue when Linux developers will be able to work in the current 
stack format?

Rob Cozens CCW
Serendipity Software Company

"And I, which was two fooles, do so grow three;
  Who are a little wise, the best fooles bee."

  from "The Triple Foole" by John Donne (1572-1631)

More information about the Use-livecode mailing list