Hi Sarah - I've not done much more than experiment with revWeb yet, but now with the "do as JavaScript" feature, and a client that can use that, I'm looking to set up an agile deployment prototyping the eventual AJAX front end in revWeb. As the app will be deployed to the test site every 2 weeks to be tested by the client and every day by the development team, I'm looking to automate that.
I understand the approach you describe for desktop apps - but you are saying you can use it for revWeb stacks as well - or not? That is a plain rev stack can be loaded dynamically with a "go to stack url ..." call and opened as a substack - just like with a desktop app? That would be great.. but.. how? So you would: 1. build the main app as a splash / glxApp application and then 2. store the body of the app as plain stacks on the server to be loaded by the revWeb app as needed? Each substack is usually in it's own div - right? So this would be the case here as well, and in a way you are loading stacks from the internet as you would AJAX calls? Sound like a great hack - or am I making something weird up here? On 29 March 2010 09:00, Sarah Reichelt <[email protected]> wrote: > Sounds like a job for a splash screen app that opens a separate sub-stack. > If you build the splash screen once, then in future, you just need to > save & upload the sub stack(s) to update the app. > The HTML wouldn't even need to be changed unless you wanted it to show > a version number or something like that. > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
