Hi Gabrielle, > S> either of those. And here's a third that could help us small > S> developers. We submit code to RT for "encapping" and sale. If > S> they like the code, they'll "encap" it and offer it for > S> paid-download from their site. They take a cut, the Rebol > S> world gets a new tool, and you get some money from it! > > That makes me think, anyone could do that, not only RT! Someone > just buys /Encap, puts up a site and start accepting scripts. 10% > of the sale goes to RT, say 5% to the site and the rest to the > developer. (Well, things aren't so easy, probably, but it can be > done.) I've not used or evaluated Encap so I was a little hazy about how it works. Which is why I kept writing "encapped" to show I was just analogising.
For your idea to work, several separately distributed Encap applications would have to be able to work with each other and non-encapped code. That way my code (clear source) could call your encapped applications that I've bought. Does anyone know if encap works that way? Or if it is (as I'd assumed) monolithic: one encapped application being a world on its own. (Thinking allowed here again, even encap application are monolithic, we could organise intercommunication via Rugby) Sunanda. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
