this is wonderful! Y'know... given that Win32::GUI is on Source-forge, these kinds of bug-fixes and upgrades really should be committed directly into the distributed code, rather than (or as well as) sent out to the group. I see a lot of interesting ideas and bits and pieces of documentation etc. flow through this mailing list, but the code itself remains broken and/or badly documented in parts (eg. Menu's). Is there anyone on the list whose responsibility it is to incorporate these snippets into the source code? Is there anyone out there with cvs write access?...Is there anyone out there who can give *me* cvs write access?? I would be willing to take up some of the slack myself if I had write access to the source.
Mark Ami Bar-Yadin wrote: > I just joined the list, and a search of the archive does not show any > messages about the msk.pl program in the samples folder. > > As my first project to get familiar with Win32::GUI I finished msk.pl, > implementing the functionality it seemed to be aiming at. I thought I'll > share it with the group. I also extended it a little, and I include a > slightly modified test.msk. I use "usage.pl" to process command line > options, and I've included my copy of it. > > I think the original msk.pl and my version of it are just the beginning. > I'm going to take a look and see if I can read Visual Basic 6 form files > (.frm) and create Win32::GUI forms from them. Leaving any VB code out, of > course. > > Thanks, > -- > Ami Bar-Yadin ([EMAIL PROTECTED]) > > ------------------------------------------------------------------------ > Name: usage.pl > usage.pl Type: Perl Program (application/x-perl) > Encoding: base64 > > Name: msk.pl > msk.pl Type: Perl Program (application/x-perl) > Encoding: base64 > > Name: test.msk > test.msk Type: unspecified type (application/octet-stream) > Encoding: 7bit
