finding revlet limits in a controlled environment
revdev at pdslabs.net
Mon Dec 7 13:54:10 EST 2009
Richard Gaskin wrote:
> Andre wrote:
> > Phil Davis wrote:
> >> My client wants to sell revlet-based software to his customers in
> >> a large US govt agency. If they are able to download & install the
> >> revweb plugin, we don't know what limitations to a revlet's
> >> capabilities might be enforced by IT in their computing environment.
> >> To answer this question, we've built a web site his customers can
> >> use in their world that steps them through a series of revlets that
> >> each try different kinds of activity. The activities
> >> include:
> >> * load the plugin and do nothing
> >> * create, read, rename, delete a file on the local HD
> >> * get a web URL (google.com)
> >> * run a shell command ("dir" or "ls")
> >> * create, delete a stack in memory; get a stackfile from a web
> >> server
> >> * print to their printer
> >> Those are all the tests so far. The test web site emails the revlet
> >> test results back to me.
> >> Now my question:
> >> Are we testing the right things? If not, what else should we test
> >> for?
> > many of those commands might not work if the user do now click the "I
> > allow" dialog thinghy which might give false results for you. I don't
> > know how introspective rev can be, can revlets return if the user is
> > allowing acces to that kind of stuff or not?
> Sounds like a good argument for a standalone in this case.
> Phil, what objections does this agency have to a standalone?
Their IT dept doesn't allow 'unapproved' installs of executables (which
may exclude browser plugins, but we'll see)! And the approval process
is, well, difficult. I think you have to know someone. As I [very
limited] understanding of it, they use mostly COTS software (at least in
the area where my client has customers). Actually I may have heard the
COTS part from someone on this list a few months ago.
> If it were net-savvy and auto-updated itself you could provide the
> benefits of the browser plugin without the limitations or guesswork.
I suspect ultimately we'll have to go with an irev-enabled site to
deliver the goods, which won't be a bad thing at all - we're just trying
to avoid the refactoring of existing desktop app functionality at that
> Richard Gaskin
> Fourth World
> Rev training and consulting: http://www.fourthworld.com
> Webzine for Rev developers: http://www.revjournal.com
> revJournal blog: http://revjournal.com/blog.irv
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
Professional Software Development
More information about the Use-livecode