Andre, My primary target market involves existing users of SaaS solutions, where any installation of plugins or net-savvy windows stand-alones (however good) would be a really hard sell.
Indeed, during market-testing discussions with potential customers before I decided on my development platform, the use of any locally installed components was a definite no-no. This is why I invested in LiveCode and the revServer pre-release programme and why now - three months later with no launch, no progress, no roadmap, no news - I am forced to rethink my technology strategy. Still that's my problem, not a 'How to use LiveCode' issue ;-) On 18 Feb 2011, at 11:53, Andre Garzia wrote: > Keith, > > Talking about RevLets, how is your experience with them under windows? > do you think your user base would install the plugin with no fuss? > > andre > > On Fri, Feb 18, 2011 at 7:10 AM, Keith Clarke > <keith.cla...@clarkeandclarke.co.uk> wrote: >> Thanks for the clarification Jaque. >> >> So, my expectations for the shipping version weren't too far off - as it >> would allow development using stacks (as with the desktop apps) and upon >> deployment to the server, a standard browser would be able to interact with >> the UI-specific, stack pages on the server, without the need for the rev web >> plugin. Revlets could be deployed in place of Flash/Air to add capabilities >> not supported by the HTML+CSS+irev feature set. This is the specific set of >> capabilities I wanted when I decided to invested in LiveCode and revServer >> to develop web-based applications last autumn. >> >> <rant>Still, this talk of the mythical shipping version is all rather >> academic as the state of the art is that against the product spec, revServer >> simply doesn't exist - it's less functional than the old 3.5 CGI. There have >> been no new versions released, the current engine is still dated June 2010 >> and the mothership is very quiet on the subject, other than 'jam tomorrow' >> when tomorrow has passed. From bitter experience, I'm not going to build my >> customer-facing services or products on vapourware technology that may never >> reach launch. From where I sit - as a so would love to be active LiveCode >> web apps developer - it seems that the revServer early adopters have been >> funding iOS development.</rant> >> >> Still, I live in hope... >> >> On 17 Feb 2011, at 19:38, J. Landman Gay wrote: >> >>> I just re-read the product page and think I see now where the >>> misunderstanding happens. The server product does currently do HTML + CSS + >>> irev. The mention of stacks at the bottom of the product page could be >>> misleading though. >>> >>> There have been requests that irev should use stacks as code libraries, >>> just as we can on the desktop with "start using stack x" or "library stack >>> x". The intention is to add that ability so that you can drop a library >>> stack onto the server, start using it, and it's stack script will be >>> available to irev handlers. Currently we need to write LiveCode scripts as >>> text files and use "includes" for that. So that's what they mean by >>> "LiveCode stack support intended for the first shipping version." >> >> >> _______________________________________________ >> 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
