My co-worker just forwarded me this parallel inquiry about the status of wxPyCE on the wxpython-users list. Let's keep it rollin'.
Matt ------- Original Message -------- Subject: Re: [wxpython-users] WinCE port Date: Sun, 20 Apr 2008 15:18:53 +0200 From: Paul Sijben <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] All, I have been looking into the local mobile web alternative for a bit and I found that it will not solve my problem. My project needs a WM6 client that can update the screen in response from asynchronous events from my server. The mobile internet explorer is based on IE4 and then restricted. This means that clever AJAX-like things do not work. For me this means I am back in the position that I need a client on windows mobile. An available wxPython port for windows mobile would be the shortest route (1). Another python-based GUI tool (2) or re-implementing my client in Java (3) would be alternatives. ad 1) Now the wxPython CE port is dead correct? What would it take to resurrect it? Anyone has any ideas? ad 2) alternatives, euhm. Venster CE was abandoned by its creators for something new (PocketPyGui) but that hasn't materialized as far as I can see. I just sent an email to the developer of that project so let's see what happens. ad 3) that seems like a lot of work but at least there is a known path forward. Does anyone have any input on this? Maybe interested parties could pool resources? I certainly have an _immediate job opening for someone who can solve this problem for me_ and would certainly be willing to donate code and binaires back to the community if we can resurrect wxPyCE for instance so I can have my client on Windows Mobile 6 sooner rather than later. Paul Sijben -- Paul Sijben tel: +31334566488 Eemvalley Technology fax: +31334557523 the Netherlands http://eemvalley.com On Mon, Apr 21, 2008 at 10:52 AM, Stef Mientki <[EMAIL PROTECTED]> wrote: > I'm too very interested, > not specially for the 2.5 but I expect a better wxPython implementation. > Unfortunately I'm just a simple *user *and besides that too busy with some > other (very large) Python projects. > Wouldn't it be a good idea to post this also in wxPython discussion list ? > > cheers, > Stef > > Matt S. wrote: > > > Hi everyone, > > > > Hope you're well. This past week I tried building wxPyCE for Python > > 2.5. The directions for building wx for 2.4 are at, > > > > http://wxpyce.wikispaces.com/Build > > > > I succeeded at building for 2.4 but not for 2.5. After catching up on > > PythonCE emails over the past year it seems that wxPyCE has lost its mojo. > > Ingmar Steen, who did a really nice job porting for 2.4 and documenting it, > > seems to have lost interest. Alexandre mentioned he would compile... but > > it's not clear that he has done so. I don't know the least about compiling, > > SWIG, etc... and I don't really have time to master these tasks. Has anyone > > ported wxPythonCE to Python2.5? If someone wants to give me guidance on how > > to get wx running for 2.5 I'd be happy to try to compile it/document how to > > do it/etc. > > Why am I interested in wxPyCE? I've been able to make a pretty cool wx > > app for the PPC2003. Two things motivated me to update my app to 2.5. > > First, I wanted to pickle a class object (that holds all my data and is > > pretty complicated). This works fine in 2.4 on the PC but not on the > > PocketPC. I was hoping updating to 2.5 would solve my problem. > > Unfortunately, just trying out 2.5 has snowballed into a major effort. In > > going to 2.5 I was also looking forward to ctypes being included in the > > distro. An additional motivation was just to keep my app current. Well, > > any help is greatly appreciated. > > > > Here's a little info on my failed hack attempt: > > When I tried to compile for 2.5 I had to rename /python/lib/python25.lib > > to python24.lib. Somewhere in the wxpyce.vcw project, when trying to > > compile _core_files, etc. there is a dependency on the lib being name > > python24.lib. So I tried to hack this by renaming 25 to 24. Things then > > compile alright. But when I start up PythonCE 2.5 and import wx I get > > _core_ errors. It seems that wx is looking for _core_ but there is only > > _core. I just tried replacing "import _core_" to "import _core as _core_" > > but then I get a _core_.wxPySetDictionary error. I'm guessing this method > > doesn't exist in the 2.4 wx source. Clearly my hacking skills have hit a > > ceiling. > > Best regards, > > Matt > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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
