Well, I've implemented all the easy parts and all the really important parts of the 
PicoGUI C API as a Perl XS module. There's not a lot of example code for it yet, but 
the 'test.pl' file contains some tidbits. The following is an overview of the 
differences in the Perl library, excerpted from README. Let me know if you need any of 
the functions on that list implemented.

-----8<------

For the most part, the perl client library is just like the C client lib.
The following lists all exceptions to this rule:

- The *Fmt functions like pgMessageDialogFmt are not implemented because
  they are unnecessary in perl
  
- Functions that accept a variable-length param list do not need to specify
  the number of args (pgWriteCmd) or zero-terminate the list (pgSetWidget
  and others)
  
- Trailing optional parameters (like in pgNewWidget) may be omitted

- pgInit is called automatically, but does not yet support command-line
  arguments (you can still set the server using the pgserver environment var)

- pgRegisterApp does not support APPSPEC parameters yet

- pgBind's 'extra' parameter is not supported because it is used
  internally to associate the C event handler and Perl event handler

- pgFrom* are gone, and pgmemdata has been replaced by a simple string scalar

- The folowing functions are unsupported so far but are planned:

pgSetErrorHandler
pgSetIdle
pgCustomizeSelect
pgGetVideoMode
pgSetWidget
pgNewBitmap
pgSizeText
pgLoadTheme
pgWriteData


--
perl -e'socket S,2,1,tcp;connect S,pack(H16,"0200029a80692d32").\0x8;print 
grep!/=/,<S>'


_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel

Reply via email to