Luis wrote:
Andre Garzia wrote:
well, this topic has been touched before. Many times. :-)
I suppose that indicates it's need... ;)
What people want is not always what they need. :)
The attraction of a browser plugin is ubiquity -- all you'd need is a
URL and you can deliver to goods. Or see it seems at first glance.
In practice, of course this would mean locating, downloading, and
installing yet another plugin, in a world where Flash is already
pre-installed.
At that point, authoring for a plugin other than Flash becomes about as
much of an issue for IT managers and end-users as locating, downloading,
and installing the Rev player or your own custom player, so much of the
primary benefit of ubiquity is lost in real-world deployment scenarios.
These snippets from previous discussions may be of interest:
Background on the nature and scope of the problem:
<http://lists.runrev.com/pipermail/use-revolution/2006-July/084230.html>
<http://lists.runrev.com/pipermail/use-revolution/2006-July/084259.html>
Options for solutions:
<http://lists.runrev.com/pipermail/metacard/2006-August/009590.html>
<http://lists.runrev.com/pipermail/use-revolution/2006-June/083882.html>
<http://lists.runrev.com/pipermail/use-revolution/2006-June/083891.html>
My personal fave, not yet built but could be at any time:
<http://lists.runrev.com/pipermail/use-revolution/2006-June/083955.html>
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
