>BSD means...? >How different is it from GNU? Not that I want to make this difficult for anyone wishing to move to a new license, but I think switching to a new license is not something that should be taken lightly. I have had a series of exchanges with Dan about his reasons for wanting to change to a BSD. Some of his reaons may be valid, but still workable in the current GNU license. Here is my last comunication with Dan that I am still waiting for a response on:
Under a BSD license, will the core files be still free to use, maintain, and modify. Or will you take total control of what gets included and changed in the core? >For example, a client I'm trying to work with right now needs to include the >core dynapi files in a Windows executable program that uses an IE-embedded >component for display. I believe you can do this with the current license, as long as you are not trying to make money off of the DynAPI files. You can include DynAPI in any media, along with "your extensions" and any other executable program that is "work that uses the Library". Section 5 of the license covers your concerns quite well: 'A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.' I believe that the statement "compiled or linked with it" covers your Windows executable program. Your widgets are also now officially considered extensions, therefore they are also not covered by this license, thus allowing you to include it in any type of media. >There are some exceptions (section 6) in the LGPL that allows you to use the >files, but they are not acceptable (such as displaying a prominant logo or >notice for DynAPI). Section 6 would only apply if you intend to mess with the core files outside of the Official DynAPI Distro, and include only portions or your own derivative of the core files as referred to by the license: "portions of the Library". I don't think this is what you intend to do. I believe what you are trying to do is rewrite the core to make it more stable. Once that is done, you want it to be adapted as a standard, and then include these newly accepted core files as a whole in your distro. I don't think you want to use "portions of the library". If this is indeed the case, there are no problems doing what you are doing under the current license. We would all share the same core files. You would have your own copyrighted widgets. Other people can write similar widgets. And every one is happy. >Also, with regards to my widget pack, a move to a BSD license would allow me to >distribute with my widgets a pre-compressed single js file containing the >latest stable version of the core DynAPI files. This makes it easier and more >simple for users. I don't have a problem with this, and I don't think anyone else would either. So why don't we add a clause to the current license, that would allow anyone "to distribute with 'my widgets' a pre-compressed single js file containing the latest stable version of the core DynAPI files". As a matter of fact, I believe people are already doing similar things in order to save a "precious few bytes". Not my style, but I don't have a problem with that. >My preference would be to go with a BSD license because it prevents a major >code-fork that will inevitibly be worse for the LGPL version. I think it is in everyone's interest not to have a major code-fork. We don't have hundreds of dedicated coders to maintain two distros. I have been warning that this will be the end of DynAPI if we are not careful. It is easier to learn other client side Dynamic programs such as flash, than to have to worry about this distro, that distro, etc. If we are silly enough to allow two major distros, we may as well say goodbye to DynAPI. If I have to pay for DynAPI, I might as well be paying Macromedia for their support and tools on using flash. DynAPI will slowly evaporate. But what exactly is your intent with the 2.6 core files? Will you take total control of it, so you can make sure that it works with your private widgets? I don't think it is healthy for one person to be in charge of the ultimate destiny of DynAPI. After all the reason that DynAPI moved to sourceforge was because you were to busy to maintain the original DynAPI. Please explain your intent with the 2.6 core. Regards, Laszlo Teglas ----Original Message Follows---- From: Dan Steinman <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Dynapi-Dev] New DynAPI Stuff - Documentation Date: Fri, 28 Dec 2001 13:19:59 -0500 I've attached my document explaining all the new features of DynAPI. It should give everybody a clear explanation of what to change in their code to make it compliant. It might take a while until I can get the rework of the events complete, so I'd be a go for getting this codebase as-is into the Sourceforge CVS as a new tree. I just have to work in Robs changes to my latest code. I'll get together a package with all the other files, and examples to promote to Sourceforge. Also, with regards to license issues, I'd still like to go ahead with a switch to the BSD license. If anyone who wrote portions of this code objects we take a look through and remove that code. Notable sections that I did not write are some of the Mozilla and DOM support. Loadpanel was largely written by others, but I had trouble with it in this version, and will be including IOElement which can be used as an alternative. BTW - what's gonna be the version number? 2.6? 2.7? 3.0? Regards, Dan Steinman On Thu, Dec 27, 2001 at 01:19:04PM -0500, Robert Rainwater wrote: Content-Description: Mail message body > > I've been messing with Dan's new dynapi code and have made a few minor updates. Dan posted a > url to his new code base a while back. I thought I would attach it so people could start looking at > how the new structure will be. This will give widget developers a chance to begin working on the > new widget structure. I've attached a simple button widget that could be used as a guide to > creating a widget. > > Here are the few changes I've made to dan's code: > - Replaced the is object with DynAPI.ua across the board > - Fixed DynLayer constructor (test for null not same as undefined in mozilla/was causing setHTML > to print undefined in mozilla) > - Removed DynImage crap. You can still use the trimmed down version the same way (may need > some work) > - Moved addpackage/library to dynapi.js. You can now use package files to set the library names > (look at package.dynapi.js) > - Added test in debug.js to keep from throwing error > - maybe something else too ? > > I believe Dan is going to rewrite the events in the next release, but this should give you a good start > to start working with the next release. The only major problem needed to be addressed is the > offsetWidth/Height problems in Mozilla. This is the main reason why the current widgets don't work > in mozilla/ns6. > > Rob << changelog.html >> _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/ _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
