Plus you can put any included library files or stacks outside the webserver document root so they can only be hit indirectly.
Be careful if you use a library stack made with 5.5 and save it in the legacy format. I don't believe the current lc server can load up 5.5 stacks. On Sat, Apr 21, 2012 at 12:19 PM, Richard Gaskin <ambassa...@fourthworld.com > wrote: > Gregory Lypny wrote: > > > In developing a site using LiveCode server, I’d be interested in your > > thoughts on keeping prying eyes away from LiveCode scripts. I > > imagine that keeping the scripts in files and stacks, as opposed to > > embedded in web pages, is the best thing. > > Why not? > > Jacque's right about the difference between the raw page and what the user > gets, but personally I find embedding tons of LiveCode into my HTML > distracting; I prefer to put simple function call in HTML and let libraries > handle the rest. > > -- > Richard Gaskin > Fourth World > LiveCode training and consulting: http://www.fourthworld.com > Webzine for LiveCode developers: http://www.LiveCodeJournal.com > LiveCode Journal blog: > http://LiveCodejournal.com/**blog.irv<http://LiveCodejournal.com/blog.irv> > > ______________________________**_________________ > 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<http://lists.runrev.com/mailman/listinfo/use-livecode> > _______________________________________________ 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