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

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

Konovalov, Vadim wrote:
> its own window will not show up if -nocolsole option is used
> I am not exactly sure for spelling, but I will be more precise after RTFSing
> a bit.

you're right, I didn't noticed (the option is --noconsole, BTW). this is 
fine, but still output is placed in /perl_stdout.txt, not emitted on the 
command line.

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

> 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 
little device, except for prototyping algorithms, is to script small 
sydadmin tasks (such as backing up important files on a storage card, 
for example), for which a command line interface is much, much better 
than using PerlIDE.

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

> it can be avoided but this is not largest problem, unfortunately :)

so let's talk about the largest problems first, and my problem then :-)

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.

cheers,
Aldo