From: Aldo C. <da...@pe...> - 2001-03-19 17:04:12
|
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; |
From: Laurent R. <ro...@cl...> - 2001-03-20 18:52:14
|
hello > > 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! > > **** 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 Good. > **** 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 :-) Not obscure at all ;-) but a very difficult point. I have think a little about this and i have notice 2 things. * With only one event fonction (actual NEM) it's possible to call the DoSomethingElse function in the DoSomething function. And in case of 'overriden' a sub package event, just need to call the event function. sub overriden_OnClick { my $self = shift; # do something before $self->OnClick(); # or in inherited package $self->SUPER::OnCLick(); # do something after } The package use the \& syntax and not sub { } in the event option. But for instanced object, it's possible to use sub {}. * With event queue Problem for the new package method. For example : - the package need to add a click event function - the user create an object with a click event function How create the click event array ? - order problem between user event and package event. - If user don't want default package click event. > **** 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). After some search about this point, I found a free open source code project named FreeImage. It's a library for loading and writing different file format (JPEG, PNG,BMP, PCX, TIFF, TGA). I have look some example, it's look easy to use. It's possible to read the data image not only from file (just need to code an io-handler). It can be usefull for read image from perl variable (no tempory file in the BitmapInline.pm or interface with perl GD module). FreeImage Web Site : http://home.wxs.nl/~flvdberg/index.html I can help you for this point. > > **** Win32::GUI::Scintilla > (see http://www.scintilla.org); to revive pride.pl! :-) > This text control look very nice. Laurent. |
From: Aldo C. <da...@pe...> - 2001-03-22 12:42:39
|
Laurent ROCHER wrote: > hello hi Laurent! >> -onClick => \&DoSomething > > Good. yup :-) > Not obscure at all ;-) but a very difficult point. > I have think a little about this and i have notice 2 things. > > * With only one event fonction (actual NEM) > > it's possible to call the DoSomethingElse function in the > DoSomething function. yes, I know, but in your example the 'implementer' is responsible for calling the package event (eg. $self->OnClick), which is not a good way to create subpackages... so I don't like this approach. > * With event queue > > Problem for the new package method. > > For example : > - the package need to add a click event function > - the user create an object with a click event function > > How create the click event array ? yes, that's the problem. I haven't figured yet a 'package-writers' API... I should think of a real world example of this and try to model in pseudocode first :-) > - order problem between user event and package event. package event should always come first and decide what to do (eg. do some stuff, then cal user event, then do some other stuff... or don't call the user event at all, if it so decides). > - If user don't want default package click event. this should be left as an option to the package writer. for example, s?he could relay on the user event's return value. 0 == don't process default (package) event, 1 == process it. this is the way Win32::GUI actually works with DefWindowProc() after all. >> **** 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). > After some search about this point, I found a free open source > code project named FreeImage. way cool, I will implement this. seems lot easier than libjpeg (even the installation is much easier and it comes with binaries too). BTW, I will also try to release a standalone Perl module for this library (eg. Image::Free :-). > I can help you for this point. you're welcome! let's discuss it on Perl-Win32-GUI-hackers. cheers, Aldo __END__ $_=q,just perl,,s, , another ,,s,$, hacker,,print; |
From: <fe...@fr...> - 2001-03-20 22:14:27
|
Dear Aldo I'd love to help because Win32::GUI is a marvelous tool and it enabled me to develop a real nice perl app on the PC. I could offer my help for working on the documentation, code some perl examples, and summarize the tricks discussed in the user group. Time available depending on my 'other activities' (see below)... Best Regards, Felix ----- Original Message ----- From: "Aldo Calpini" <da...@pe...> To: <per...@li...> Sent: Monday, March 19, 2001 6:11 PM 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 > Per...@li... > http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users |
From: Aldo C. <da...@pe...> - 2001-03-22 12:29:27
|
fe...@fr... wrote: > Dear Aldo > I'd love to help because Win32::GUI is a marvelous tool and it > enabled me to develop a real nice perl app on the PC. I could > offer my help for working on the documentation, code some perl > examples, and summarize the tricks discussed in the user group. > Time available depending on my 'other activities' (see below)... you're very welcome Felix! I think that the most helpful thing you can do (that's one that I forgot to include in the .plan) is to build a Win32::GUI FAQ based on the experience of this mailing list. you can prepare the base document if you can, then submit it to the list so that everyone, me included, can comment/add stuff/trim stuff/etc. we all count on you for this! :-) cheers, Aldo __END__ $_=q,just perl,,s, , another ,,s,$, hacker,,print; |
From: <fel...@fr...> - 2001-03-22 17:57:09
|
Hello Aldo in order to get started, where can I find the most up-to-date WIN32::GUI documentation version? I probably have a very outdated one on my PC. And a second question, is there any model FAQ document you recommend as a basis? Otherwise, I would just take the "perlfaq.html" document of the core perl documentation as a basis and adopt it. Is that fine for you? Best Regards Felix Gaehler Zurich, Switzerland ----- Original Message ----- From: "Aldo Calpini" <da...@pe...> To: "fe...@fr..." <per...@li...> Sent: Thursday, March 22, 2001 1:34 PM Subject: Re: [perl-win32-gui-users] .plan > fe...@fr... wrote: > > Dear Aldo > > I'd love to help because Win32::GUI is a marvelous tool and it > > enabled me to develop a real nice perl app on the PC. I could > > offer my help for working on the documentation, code some perl > > examples, and summarize the tricks discussed in the user group. > > Time available depending on my 'other activities' (see below)... > > you're very welcome Felix! > I think that the most helpful thing you can do (that's one that > I forgot to include in the .plan) is to build a Win32::GUI FAQ > based on the experience of this mailing list. you can prepare > the base document if you can, then submit it to the list so > that everyone, me included, can comment/add stuff/trim stuff/etc. > > we all count on you for this! :-) > > > cheers, > Aldo > > __END__ > $_=q,just perl,,s, , another ,,s,$, hacker,,print; > > > > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Per...@li... > http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users |
From: Aldo C. <da...@pe...> - 2001-03-27 14:30:56
|
fel...@fr... wrote: > Hello Aldo > in order to get started, where can I find the most up-to-date > WIN32::GUI documentation version? I probably have a very > outdated one on my PC. I'll send it to you. > And a second question, is there any model FAQ document you > recommend as a basis? Otherwise, I would just take the > "perlfaq.html" document of the core perl documentation as a > basis and adopt it. Is that fine for you? completely fine. cheers, Aldo __END__ $_=q,just perl,,s, , another ,,s,$, hacker,,print; |