Keith, One revlet will not be able to access other revlet unless you load them all in the same page and use something like "do ... in browser" to communicate which would be hard since you would need to create all the communication channel.
Why not loading all the stacks in the same revlet? Andre On Sun, Jan 30, 2011 at 1:39 PM, Keith Clarke <keith.cla...@clarkeandclarke.co.uk> wrote: > Hi Folks, > I'm looking to pull together various rev wire-frame/prototype/experiment > pages for a web app project into a more structured development environment. > If I migrate my various experiments into sub-stacks of a single GLX framework > app (and then save this as a revlet) would individual revlet pages be > externally addressable via urls within a requirements mgt database? Or does > revweb work as a self-contained 'player', suggesting that I'd need to keep > the various pages separate? > TIA, > Keith.. > _______________________________________________ > 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://www.andregarzia.com All We Do Is Code. _______________________________________________ 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
