Andre, Thanks for sharing. As your revletobject.load script has 'src', 'stack' and 'id' parameters, it looks like I can get 'inside' the revlet, to open on a specific stack - that makes the single revlet with multiple start-points seem feasible. Great!
If I understand this correctly, if I place this javascript into a holding page for a demo revlet - and then hard-code the stack parameters - the page will launch the demo revlet, focused on the desired stack - nice! Furthermore, a single demo page could be used to dynamically launch the revlet with the desired stack focus. If I create my functional specification in a spreadsheet or database, with columns for the demonstration revlet & stack parameters, a formula can generate the 'demo' URL with these parameters after a '?' character. Then, I can add to your Javascript, some code that extracts the URL parameters into variables and then launches the demo revlet into the correct stack. I'm off to learn a bit about Javascript URL extract functions! Thanks, Keith.. On 31 Jan 2011, at 13:33, Andre Garzia wrote: > Keith, > > The revlet is hosted at a web page, you can have different web pages > for each revlet so they will have unique urls. If doing revlets, check > out my library at http://hg.andregarzia.com/revletobject (check the > wiki) it has some nice loading routines for revlets, easier than using > the one RunRev is using. > > Andre > > On Mon, Jan 31, 2011 at 11:27 AM, Keith Clarke > <keith.cla...@clarkeandclarke.co.uk> wrote: >> Andre, Thanks for responding. The question isn't about whether revlets can >> access other revlets but whether specific revlet stack/card/pages have >> externally available URLs to open them directly. >> >> I'm collaborating on a functional specification document (probably in a >> Google Doc) and would like to embed hyperlinks to specific cards within a >> 'wire-frames' revlet that I upload onto my VPS. I therefore need either: >> 1. A single revlet, with externally addressable URLs for each page that it >> generates - if page-specific URLs are created and available outside the >> revplayer; >> 2. Separate revlets for each wire-frame or demo environment - if each revlet >> is self-contained; >> >> I'd prefer option (1) if it is possible, so that requirements can be linked >> to different start-points within a single prototype application, but can I >> access multiple URLs within a revlet - or pass parameters after a single >> main URL to open a specific stack or card? >> Best, >> Keith.. >> >> On 31 Jan 2011, at 13:01, Andre Garzia wrote: >> >>> 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 >> >> >> _______________________________________________ >> 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 _______________________________________________ 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
