I started to work on a project involving server stacks and had to stop full stop... here is why :
Servers stacks are designed as SCRIPT CONTAINERS, allowing to password protect scripts on the server and develop libraries. Card creation, field creation and navigation are crippled and do not allow a more standard use of stacks, as a structured data container. Re-use of standard stacks will fail for many reasons with the command go stack. Loading stacks as libraries with the "start using.." threw the same error on loading when first card had a button or fields on it. So id' rather call'em server LIBRARIES than stacks. details : http://runtime-revolution.278305.n4.nabble.com/file/n3728748/revServer-MEMO-server_Stacks_v1.rtf revServer-MEMO-server_Stacks_v1.rtf of course it would be great for some of you to counter test these findings, update this memo and let us know, and communicate with mothership those who are in close contacts. It would be great to know what these server stacks are aimed at, will they gradually (..years!) come to par with standard stacks or are they INTENDED as stack libraries full stop!? Thanks, RObert. -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Server-create-stack-trouble-tp3721781p3728748.html Sent from the Revolution - User mailing list archive at Nabble.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
