brahma at hindu.org
Fri Nov 25 05:34:36 CET 2016
I too never quite understood why the RevWeb Plugin was abandoned. The old issue that users resist such downloads, never, IMHO, really materialized… just look at the kJillion extensions for FireFox or Chrome, there is no end in sight.
So the plugin was abandoned, but in the end, hasn't the team has built the same thing?
Enscripten with a wrapper for LC?
But instead of being able to deliver that as a "player" … now the user is forced to download that entire source code with each and every Html5 app built with LC.
I get of course that the framework of the RevWeb Plugin was a completely different architecture… and moving to JS means the browser as an "OS" will be more "at peace with the code," so to speak, but yet, why could it not be externalized as a plug-in/helper/player?
I must be very naïve and missing something….perhaps security issues require us to bundle the code with each app, so that 3rd parties can't hack the player for nefarious ends… as Mark says: legions are trying to find ways to break through to your HD…
On 11/24/16, 10:42 AM, "use-livecode on behalf of Roger Eller" <use-livecode-bounces at lists.runrev.com on behalf of roger.e.eller at sealedair.com> wrote:
I disagree that you might as well be running a desktop app. The download
of the helper would only be necessary once (like the old RevWeb plugin).
Back when we had the RevWeb plugin, my browser based apps just worked.
Being in a position where localized automation is primarily what I create
for in-house users, this would allow me to update/maintain to a single
code-source, but without having my hands tied capability-wise by the
More information about the use-livecode