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

[REBOL] Re: Encap

From: greggirwin:mindspring at: 20-Oct-2001 11:38

I spoke with Cindy recently and she said the new license agreement is almost done for encap. Beyond that, and with the caveat that I may mis-state things, here's my understanding. You can use encap to protect your source, by binding it to the REBOL runtime, but you don't have to. The Alliance (now called REBOL Royalty I think she said) is required if you want to sell your apps commercially even if you don't encap them. If you don't use encap on them, you may distribute the free versions of Core and/or View with your app, but not the pro versions. I didn't ask about encap'd code loading external code/data but I think that would have to be allowed because otherwise you couldn't deal with persistent data in native REBOL format, could you, and that would severely limit what kind of apps you could write. Again, without knowing the details, my guess is that an encap'd app doesn't provide access to the console. The licensing agreement, when it becomes available, should be clear on what you can and can't use it for. Building an app that provides significant functionality beyond REBOL itself should be allowed, but something like vconsole might be questionable. An IDE for REBOL should be allowed but there will be some gray areas to muddle through to be sure. At one point, MS had a clause in the VB license that said you couldn't use it to create a "database application" (can't remember the exact wording). Their intent was to say that you couldn't create an app competetive with Access using VB but it wasn't *clear* that was what they meant. As I think Carl said before, the legal side of things seems to take longer than the coding side. :) Remember that I could be wrong about all this and, if so, that's my fault. No gospel spoken here. --Gregg