Jan Schenkel wrote:
With revMedia 4.0 being free, why would we still need a Player?
The whole idea of giving revMedia away for free, is to let everyone share in 
the fun - running stacks, deploying them in webpages and letting others take 
them apart without the ability to password-protect your scripts.
Don't panic, revStudio and revEnterprise can still password-protect scripts and 
these stacks will work just fine in revMedia. But revMedia is about sharing 
with the rest of the world, and getting more people to try out the revPlatform 
for themselves.

I can think of one reason why one might want a Player:

Imagine a cash-strapped teacher designing a stack with revMedia;

they might think it a bit too much to expect students to go through
the whole jingbang of registering for revMedia, downloading it
and installing it a bit of a clunky way to deliver a "quick-n-dirty"
educational "media-bite".

this might also be applied in situations where there are a number of
students with computers who do not have internet access (this, oddly
enough, is always overlooked when these arguments come up).

A Player/Runner + stack will have less of a footprint than revMedia
+ stack

As an advocate of equipping the under-privileged in this world with
old computers I believe that a Player/Runner is essential; especially
one that will run stacks on forms of Linux.

---------------------------------------------------------------------------------------
To personalise this I would like to point out that, while I own
Rev Studio 4 it does not work on my Pentium 3s running Ubuntu 5.10;
nor does revMedia 4.

I have yet to find out how standalones made with 4 'do' on these computers;

It may well be that they are just too RAM-hungry to function;

a Player/Runner might solve this problem.
_______________________________________________
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

Reply via email to