From: Steven D. A. <st...@ne...> - 2001-09-06 02:00:36
|
Hi Kevin, On Tuesday, September 04, 2001, at 2:56:12 PM, you wrote: KA> Kevin: Anyway, I would like to give it a shot, but I will not be KA> locked into the GPL. KA> Riaan: That's why I mentioned the MPL, if there was some sort of KA> collaboration, I could relicense those core Boa files under the MPL KA> which means those core files are 'like' GPL files (you have the KA> make changes to those files available for free) but with the MPL KA> you can integrate very easily to the core with code from any license. KA> It only 'infects' things in the core. Not things that just use or KA> integrate with it. So this sounds much like the LGPL. The core itself is open-source and must remain so -- any modifications must be released. But projects that are built with it would not be GPL or MPL, nor would tools that merely work with it or link it. Is that the basic idea? On another note, I don't really like Riann's approach of using Python code itself to generate interfaces. It seems a lot more general to use some flavor of XML to describe interfaces, and sharply distinguish this from the user code. This kind of separation/abstraction allows one to easily modify the way interface elements work in one's code without worrying about the IDE overwriting one's changes or making other undesirable changes. To put the policy in a sentence: anything that is automatically generated by the IDE should not be modified by the user (this would no doubt include the final code/binary as well as interface template files). Has anyone else experienced this kind of issue with Boa (or maybe found a workaround that obviates it as a problem)? ------------------------------------------------------------------------ Steven D. Arnold st...@ne... AIM: abraxan ICQ: 73804392 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |