Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

Upcoming /View and /View/Pro

 [1/6] from: gjones05:mail:orion at: 5-Apr-2001 6:22


The website refers to /View as being for personal use, and, thereby, not redistributable. On my initial take several days ago, I assumed that /View/Pro would be, presumably with a runtime. Why I thought this, I have not a clue (mind you, I also "bought" the Parrot language piece). It seems to me upon rereading what is available, that /View and /View/Pro will only exist for the pleasure of the interested developer, and not available as an end-user product, for all intents and purposes. Please correct me if I am wrong. I'm also curious what others may think about this situation. --Scott Jones

 [2/6] from: rgombert:essentiel at: 5-Apr-2001 16:28


> The website refers to /View as being for personal use, and, thereby, not > redistributable. On my initial take several days ago, I assumed that > /View/Pro would be, presumably with a runtime. > > Why I thought this, I have not a clue (mind you, I also "bought" the
Parrot
> language piece). It seems to me upon rereading what is available, that > /View and /View/Pro will only exist for the pleasure of the interested > developer, and not available as an end-user product, for all intents and > purposes. > > Please correct me if I am wrong. I'm also curious what others may think > about this situation.
My opinion is /View should not be another toy... if i can just play with it (and surely have some fun) but can't provide /View based applications to my clients, the value of /View as a product is near zero. Renaud

 [3/6] from: holger:rebol at: 5-Apr-2001 8:39


Some clarifications, based on our current plans. Please keep in mind that licensing conditions are always subject to change. On Thu, Apr 05, 2001 at 06:22:58AM -0500, GS Jones wrote:
> The website refers to /View as being for personal use, and, thereby, not > redistributable.
No, that is not what it means. View and View/Pro will both be freely downloadable and redistributable. After downloading, View/Pro initially behaves just like View, i.e. the advanced features (Shell, Library and Encryption) are not available. To be able to use these features you need to buy a separate license key from us that unlocks those features. We will try to make this as easy and quick as possible, with a "turnaround time" from online ordering of the license key to email delivery within just a few minutes. The only restriction on distribution with View/Pro is that it contains encryption code and that redistribution therefore has to comply with legal restrictions regarding the use, redistribution and export of encryption code. It is the responsibility of the person redistributing View/Pro to ensure compliance. The phrase "single user license for personal use only" refers to two issues: 1. The license agreement for View and View/Pro. The current versions of View and View/Pro along with their licenses and pricing are intended for individuals, in non-commercial environments. Use in commercial environments requires separate licensing from us, at different conditions. 2. The personalized View/Pro license key. That key is not transferable, assignable or redistributable. If you would like to redistribute View or View/Pro along with a script you have written then you have the following options: 1. Your script only needs View, not View/Pro, and you do not mind other people seeing your code: Just distribute View and your script. No restrictions. 2. Your script only needs View, but you would like to keep your script secret: You need View Runtime. No information on pricing or release date yet. 3. Your script needs View/Pro, you do not mind other people seeing your code, and you do not want to pay for Runtime: Distribute View/Pro and your script, but without your license key. In order for users to be able to run your script they first need to buy a personalized license key from us for View/Pro. Until they obtain the license key their copy of View/Pro will only have View features, so your script may not work correctly. 4. Your script needs View/Pro and you want to keep it secret or you want users to be able to run it without having to obtain their own license first: You need View/Pro Runtime. No information on pricing or release date yet. -- Holger Kruse [holger--rebol--com]

 [4/6] from: gjones05::mail::orion::org at: 5-Apr-2001 10:58


From: "Holger Kruse"
> Some clarifications, based on our current plans. Please keep in mind > that licensing conditions are always subject to change.
Thanks, Holger, this certainly clarifies my previous misconception. --Scott Jones

 [5/6] from: petr:krenzelok:trz:cz at: 5-Apr-2001 20:36


----- Original Message ----- From: "Holger Kruse" <[holger--rebol--com]> To: <[rebol-list--rebol--com]> Sent: Thursday, April 05, 2001 5:39 PM Subject: [REBOL] Re: Upcoming /View and /View/Pro
> Some clarifications, based on our current plans. Please keep in mind > that licensing conditions are always subject to change.
<<quoted lines omitted: 19>>
> View and View/Pro along with their licenses and pricing are intended for > individuals, in non-commercial environments. Use in commercial
environments
> requires separate licensing from us, at different conditions. > 2. The personalized View/Pro license key. That key is not transferable,
<<quoted lines omitted: 18>>
> license first: You need View/Pro Runtime. No information on pricing > or release date yet.
Those are not all the options. What about following one group of conditions? - I am not interested in hiding my code from the eyes of users = no runtime - I want them to use /Pro capabilities - I don't want them to bother with downloading/unlocking their View/Pro distribution of unlocked View/Pro with granted licence to user Few possible solutions/questions arise. Could you please comment? - will it be possible to distribute unlocked View/Pro along with my scripts (=no runtime), with licence granted to the user? - if RT feels I am asking too much of openess, maybe it would be possible to grant special kind of licence, locking such product combination to certain device/area of usage? - One other question - what will be pricing for corporate sphere? Thanks, -pekr-

 [6/6] from: holger:rebol at: 5-Apr-2001 16:18


On Thu, Apr 05, 2001 at 08:36:59PM +0200, Petr Krenzelok wrote:
> Those are not all the options. What about following one group of conditions? > > - I am not interested in hiding my code from the eyes of users = no runtime > - I want them to use /Pro capabilities > - I don't want them to bother with downloading/unlocking their View/Pro > distribution of unlocked View/Pro with granted licence to user
One solution is View/Pro Runtime, bundled with the source code of the script, if you want users to see it.
> Few possible solutions/questions arise. Could you please comment? > > - will it be possible to distribute unlocked View/Pro along with my scripts > (=no runtime), with licence granted to the user?
Unlikely.
> - if RT feels I am asking too much of openess, maybe it would be possible to > grant special kind of licence, locking such product combination to certain > device/area of usage?
That may be possible. If you have a particular (commercial) use in mind please contact us directly.
> - One other question - what will be pricing for corporate sphere?
Has yet to be determined. -- Holger Kruse [holger--rebol--com]

Notes
  • Quoted lines have been omitted from some messages.
    View the message alone to see the lines that have been omitted