[PythonCE] Re : numarray or numpy for WinCE

2007-01-30 Thread alexandre . delattre
Hello,

You can download a pre-compiled release of numarray 1.5.2
for python ce 2.4 at  
http://sourceforge.net/project/showfiles.php?group_id=104228

Alex.

___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce


Re: [PythonCE] Bluetooth

2007-01-30 Thread Thomas Heller
Ruben Miguelez Garcia schrieb:
>   Hello to all,
>   I am new on the list. 
>   Firstly I will share all my experiences until now.
>   Then I am going to explain some research that I did about bluetooth 
> on "Windows CE" because that is my main problem now.
> 
> == Some experiences ==
> 
> 1- After read many mails on the list, I decided to use the server & client 
> connection programs provided on the thread "How do you develop on the 
> PocketPC?"
> 
> 2- The first execution raise the error "ImportError: No module named ctypes". 
> Then I updated the windows version inside the PDA to 2.5 and everything fine.
> 
> 3-On the beginning, click on the client.py only opened a Python session 
> without connect to the server. Then I discovered that with the PDA connected 
> to the laptop by USB with ActiveSync running, the wifi was not working. After 
> unplug the USB cable, wifi works fine and one click over the client.py 
> connect to the server.
> 
> PD: Of course, I had to modify the IP inside the client.py to point to my 
> laptop.

I'm afraid I cannot help with the bluetooth stuff,  but I have worked somewhat
on the server&client connection program.

A much improved version is available here:

http://ctypes-stuff.googlecode.com/svn/trunk/wince/remote-console/

The console.py script is thought to be run on the workstation.  Editing
the client.py script (which is transferred automatically to the PDA) is no
longer needed.

console.py accepts some command line options which can also be used for
Python itself:  -m 'package', -c 'Python commands',  other options are
accepted but don't do anything: -i, -u.

Thomas

___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce


Re: [PythonCE] VensterCE release

2007-01-30 Thread Thomas Heller
[EMAIL PROTECTED] schrieb:
> 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 !
> 
> Alex.

I have tried a version that I pulled from CVS (or was it SNV?) some days
ago.  I was quite impressed, although I had problems understanding
the menus in french ;-).

Thomas

___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce


Re: [PythonCE] VensterCE release

2007-01-30 Thread alexandre . delattre
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 !

Alex.

___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce


Re: [PythonCE] VensterCE release

2007-01-30 Thread Brian Brown

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

___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce


[PythonCE] VensterCE release

2007-01-30 Thread alexandre . delattre
> 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.

___
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce