Aldo -
Has anyone volunteered to help with the Win32::GUI::JPEG addition yet?
I would like to help, but my C/C++ experience isn't current, as my
familiarity with today's compilers. It's been over 5 years since I have done
any serious C programming. Let me know what your expectations are of someone
to help with this issue.
I am quite interested in seeing this part of Win32::GUI done as I REALLY
need it for a program I have been working on.
Let me know how I can help.
Tim
----------------------------------------------------------------------------
---------------------
Tim Thomas
Unix Systems Administrator
Lockheed Martin EIS ยท Denver Data Center
303-430-2281
mailto:[EMAIL PROTECTED]
----------------------------------------------------------------------------
---------------------
-----Original Message-----
From: Aldo Calpini [mailto:[EMAIL PROTECTED]
Sent: Monday, March 19, 2001 10:12 AM
To: perl-win32-gui-users@lists.sourceforge.net
Subject: [perl-win32-gui-users] .plan
hello perl-win32-gui-users,
this is my dot plan about Win32::GUI, what I'm doing and what
I plan to do. please note that everything here may change (without
further notice) depending on my other activities (namely job and
'real life' :-).
it would be kewl if you could 'prioritize' the list based on
what you find more useful (or funny :-), and above all (pardon
the caps): IF YOU CAN HELP ME WITH SOMETHING, PLEASE DO!
that said, this is the list:
**** NEM (New Event Model)
I'm almost done with this, but there are still some flaws.
I will also define the API to manage events (eg. AddEvent
or BindEvent or ResetEvent or something like this...).
I'm also adding the possibility of 'shortcut' options a la
Javascript, like:
-onClick => \&DoSomething
**** Event Queues
this is something I didn't really explored yet, but I would
like to process a list of events. should look somehow like
this:
-events => { Click => [ \&DoSomething, \&DoSomethingElse ] }
in other words, when a Click events occur first DoSomething
is executed, then DoSomethingElse. the main purpose for this
is to allow subpackages to define their own event handlers
which can be 'overriden' by the implementation in the program.
(if it doesn't sound clear, don't worry, is still mainly obscure
to me too :-)
**** Win32::GUI::JPEG
allow *read* support for JPEG images, using libjpeg (see
ftp://ftp.uu.net/graphics/jpeg). JPEG files can be converted
to in-memory bitmaps and then used as regular Bitmap objects.
(NOTE: I'm *not going* to develop Win32::GUI::GIF. GIF is
absolutely deprecated, I'll look into PNG support eventually).
**** Win32::GUI::Scintilla
(see http://www.scintilla.org); to revive pride.pl! :-)
these are the main points... for now, I will post a followup
if I forgot something :-)
cheers,
Aldo
__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;
_______________________________________________
Perl-Win32-GUI-Users mailing list
Perl-Win32-GUI-Users@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
