Re: [perlce-user] PerlCE and "real" console

[Aldo C. <da...@pe...>]

Konovalov, Vadim wrote:
> It was in my plans to look closer but, once again, my weak efforts were just
> not enough.
> Also, I asked for an advice in wince-developers ML but no good from that
> side either...

I know the feeling :-)

> You're right, and having Win32::GUI will be a real advantage there...
> 
> But Perl/Tk is very special on WinCE: ported by Rainer Keuchel is only older
> version without unicode, which is noticeable long to start, but another
> approach makes this situation considerable better. I use Tcl::Tk module, so
> things are more lightweight. See URL at
> http://perlce.sourceforge.net/cgi-bin/perlce-tcltkce-wiki.pl?Happy_Screensho
> ts for such screenshot examples

by "weight" I mean mostly "size". the Perl tree on my iPAQ is 10.68 mb, 
which means that I must put it on a Storage Card (not a big deal, as I 
have an SD card that fits inside the iPAQ main body; but my first iPAQ 
only had a Compact Flash jacket, which made it bigger :-). I guess the 
Perl/Tk distribution weights some mb more. compiling  Win32::GUI for the 
CE platform shouldn't (I hope) add much more to the desktop version, 
which actually is ~800kb DLL. but I don't have time to work on it right 
now, so this isn't really an issue.

> One is
> http://perlce.sourceforge.net/cgi-bin/perlce-tcltkce-wiki.pl?Be_Aware,_WinCE
> ,_PocketPC_Have_Serious_Design_Limitations which most often appears on
> devices with GSM radio stack, when many processes are always exist to
> support a phone.  

I don't see how this one is related to PerlCE (more than any other WinCE 
program, I mean). is there any special reason to consider this as a 
problem for Perl? and if this is a design limitation, I think there's 
very little to do, except maybe sign a petition and send it to Microsoft :-)

> Another one is - probably latest patches to WinCE made some bad changes and
> now script often sporadically exits with a message "Exit code 14".
> 
> Probably my bad :(

well, right now I'm trying to run the whole perl test suite on my iPAQ. 
should take quite a while, but, well, while I'm at the office the iPAQ 
sits on its cradle doing nothing but sync most of the time; battery 
time, at least, is not a problem :-)

I encountered some problems with @INC, but if I come up with something, 
I will post the results and write an how-to for the wiki.

I hope that running the test suite should help isolate problems.

> When I did my changes, I sent patches to p5p. I think it is still reasonable
> to do same way. There's no WinCE pumpking.

but maybe a CVS repository on sourceforge could help, don't you think?

> Inserting all kind of information to Wiki  - I am sure all people who have
> usefull things to say - they should share those useful bits.

I will, definitely.

cheers,
Aldo