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

[Konovalov, V. <vko...@sp...>]

> > As another point, CMD.exe is not supported on (very) old WinCEs
> 
> I know and I understand, but since it is supported on (most commonly 
> used, I guess) non-very-old PocketPC devices, it makes lot of 
> sense to 
> have proper CMD.exe interaction. at least as an option, 
> either at build 
> time or at runtime.

I also think so.
More to say, I think it will be better when PerlCE port will be greatly
reorganized, may be dropping obsolete configs and agreeing on supported
ones...

Yet ruby on WinCE could be happily used from CMD.exe.
Don't know of other languages.

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...


> > IMO,  using PerlIDE is probably a way to make sutuation easier.
> 
> hrm. not quite. I mean, PerlIDE is fine, but I _do_ want 
> PerlCE to be a 
> command line friendly executable. the biggest use I see for Perl on a 

....

I agree with you.


> on the other hand (and on a completely unrelated topic) "real world" 
> applications on a PDA need a GUI very badly. for example, I think 
> porting Win32::GUI on PerlCE should not be terribly hard. at least, 
> should be more light-weight than Perl/Tk. and we all know 
> that weight is 
> an issue here :-)

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

Of course native widgets will help.


> 
> > it can be avoided but this is not largest problem, unfortunately :)
> 
> so let's talk about the largest problems first, and my 
> problem then :-)

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.  

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 :(

> 
> seriously, I have a good knowledge of the Perl codebase, internals, 
> build process, etc. as well as good experience on the Win32 
> platform. I 
> have very little spare time at hand, but if there's something 
> I can do 
> for PerlCE, just let me know. eventually, post a todolist on the wiki 
> and I'll see if I can do something.

I have no single doubts about your excellent experience in Perl internals,
externals and surrounding environment!

In case you'll make additions - of course they will be greatly appreciated
by following PerlCE users.

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.

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

Best regards,
Vadim.