Re: [PythonCE] VensterCE release
[EMAIL PROTECTED] wrote: > Brian Brown <[EMAIL PROTECTED]> a écrit : > > >> On Jan 30, 2007, at 8:55 AM, [EMAIL PROTECTED] wrote: >> >> I'm curious. The original Venster was published under the MIT license. Why have you published Venster-CE under the GPL license? Alan. >>> Well, I thought that the most important was to use an OSI compliant >>> license and I personnaly prefer GNU/GPL. I'am no license-expert, so if >>> you see any problem with this, tell me, and I could change the >>> licensing. >>> >>> Alex. >>> >>> >> Hello Alex, >> >> >> I was under the impression that MIT is quite OSI compliant. I prefer >> MIT/BSD licensing and have published a great deal of code under that >> license (http://techgame.net/projects/Framework). >> >> I personally believe there is a great synergy between commercial and >> open source entities; for example, all the code we have created as >> expressly open source were completely funded by commercial entities. We >> make it as free as we can (MIT/BSD) for commercial or non-commercial >> use. The GPL typically bars commercial use because you can't keep any >> part of your system proprietary. >> >> Basically, If a toolkit is GPL, I typically won't use it when doing >> development of my own stuff, although there are lots of other licenses, >> such as MPL, APL and others that are less restrictive that the GPL. >> >> That's my 2 cents :) >> >> - Brian >> >> >> >> >>> ___ >>> PythonCE mailing list >>> PythonCE@python.org >>> http://mail.python.org/mailman/listinfo/pythonce >>> > > Hello Brian, > > Well, since I'm a student, I didn't really take into account > commercial use. I ideally thought that GPL gives a lot of freedom for > free or commercial development. > If it encouranges python ce users to choose venster as their gui > toolkit, in free or commercial products, I will release the upcoming > version under a MIT license. > > Anyway, have you tried venster-ce ? > I'll be glad to have comments or (constructive :-) criticism ! > I'd be keen to try it but would only be able to use LGPL / Python / MIT license Cheers David ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] VensterCE release
On Mar 5, 2007, at 9:11 AM, David Fraser wrote: >> >> Hello Brian, >> >> Well, since I'm a student, I didn't really take into account >> commercial use. I ideally thought that GPL gives a lot of freedom for >> free or commercial development. >> If it encouranges python ce users to choose venster as their gui >> toolkit, in free or commercial products, I will release the upcoming >> version under a MIT license. >> >> Anyway, have you tried venster-ce ? >> I'll be glad to have comments or (constructive :-) criticism ! >> > I'd be keen to try it but would only be able to use LGPL / Python / > MIT > license > I think he may have already released it under MIT... Brian > Cheers > David > ___ > PythonCE mailing list > PythonCE@python.org > http://mail.python.org/mailman/listinfo/pythonce ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
[PythonCE] Building under Visual Studio 2005 for Devices
Hi, I am keen to start contributing to the Windows CE/Windows Mobile port of Python. I have a lot of commerical development experience in this environment. I would like to understand the build process for Python in a lot more detail than I currently do. I thought an ideal way to do this would be to have a goal of making PythonCE compilable under Visual Studio 2005. Is anyone able to give me any starting tips on how I might approch this? Should I look at modifying the SCONS scripts to be able to detect and make use of Visual Studio 2005 instead of EVC, or should I go the route used by the PCBuild and PCBuild8 directories (i.e. desktop versions) where (I assume) someone has manually created a bunch of suitable project and solution files? Thanks. Christopher Fairbairn ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] Building under Visual Studio 2005 for Devices
Christopher Fairbairn wrote: > Hi, > > I am keen to start contributing to the Windows CE/Windows Mobile port of > Python. I > have a lot of commerical development experience in this environment. > > I would like to understand the build process for Python in a lot more detail > than I > currently do. I thought an ideal way to do this would be to have a goal of > making > PythonCE compilable under Visual Studio 2005. > > Is anyone able to give me any starting tips on how I might approch this? > Should I > look at modifying the SCONS scripts to be able to detect and make use of > Visual > Studio 2005 instead of EVC, or should I go the route used by the PCBuild and > PCBuild8 directories (i.e. desktop versions) where (I assume) someone has > manually > created a bunch of suitable project and solution files? > > PythonCE is a port of the standard CPython project. As it happens there is thread going on *right now* on the Python-dev mailing list on what it takes to make CPython compilable with VS 2005. The same techniques would have to be applied to the PythonCE project which is essentially just a patched version of vanilla CPython. Worth browsing the Python-dev mailing archives for this month... Fuzzyman http://www.voidspace.org.uk/python/index.shtml > Thanks. > Christopher Fairbairn > > > ___ > PythonCE mailing list > PythonCE@python.org > http://mail.python.org/mailman/listinfo/pythonce > > ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
