Win32::GUI

Hi all,
I created a web page where you can download the Win32::GUI::Skin module and
example.  You will also get the scripts used to create your own skin files.

The site is: http://www.millham.net/perlskin

If you are interested in creating a skinned application, please give this a
try, and let me know if it works for you!

Brian Millham
This message traveled at least 44,000 miles to reach you!
Creator of the DW6000 Monitor
http://www.millham.net/dw6000
bmillham@...

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0615-1, 04/11/2006
Tested on: 4/11/2006 9:15:34 PM
avast! is copyright (c) 2000-2003 ALWIL Software.
http://www.avast.com

RE: [perl-win32-gui-users] The skin module From: Brian Millham <bmillham@hu...> - 2006-04-13 00:01 Hi again, I see the quite a few people checked out my page about creating a = skinfile for use with my Skin module. I realize that the documentation needs a = lot of work... Has anyone tried to play with this yet? Have some of you who are more familiar with creating modules looked at = the code in Skin.pm. Am I on the right track here for creating a true Win32::GUI::Skin module? If you've looked at the sample script, Skin.pl, did I do a good job of making it easy to create a skinned application? (as long as you have a skinfile)? The reason I'm asking is that I'd like to proceed making the module Win32::GUI::Skin. I'd also like to start adding more controls. I don't want to do this until I know that the basic module is looking good. Brian Millham This message traveled at least 44,000 miles to reach you! Creator of the DW6000 Monitor http://www.millham.net/dw6000 bmillham@... -----Original Message----- From: perl-win32-gui-users-admin@... [mailto:perl-win32-gui-users-admin@...] On Behalf Of = Brian Millham Sent: Tuesday, April 11, 2006 9:16 PM To: perl-win32-gui-users@... Subject: [perl-win32-gui-users] The skin module Hi all, I created a web page where you can download the Win32::GUI::Skin module = and example. You will also get the scripts used to create your own skin = files. The site is: http://www.millham.net/perlskin If you are interested in creating a skinned application, please give = this a try, and let me know if it works for you! Brian Millham This message traveled at least 44,000 miles to reach you! Creator of the DW6000 Monitor http://www.millham.net/dw6000 bmillham@... --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0615-1, 04/11/2006 Tested on: 4/11/2006 9:15:34 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting = language that extends applications into web and mobile media. Attend the live = webcast and join the prime developer group breaking into this new coding = territory! http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 _______________________________________________ Perl-Win32-GUI-Users mailing list Perl-Win32-GUI-Users@... https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users http://perl-win32-gui.sourceforge.net/ --- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0615-1, 04/11/2006 Tested on: 4/11/2006 9:22:45 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0615-2, 04/12/2006 Tested on: 4/12/2006 8:00:21 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com

RE: [perl-win32-gui-users] The skin module From: Jeremy White <jez_white@ho...> - 2006-04-13 06:32 >The reason I'm asking is that I'd like to proceed making the module >Win32::GUI::Skin. I'd also like to start adding more controls. I don't >want to do this until I know that the basic module is looking good. I had a quick look and it seems fine - although I didn't have time to do a proper look. I did raise a tracker item for ExtCreateRegion, SetWindowPos functions so future versions of Win32::GUI::Skin don't have a dependency on Win32::API. If you need more functions, just add them to this item. Hopefully I'll have some spare time to implement them before V 1.4. http://sourceforge.net/tracker/index.php?func=detail&atid=366572&aid=1469648&group_id=16572 Cheers, jez.

RE: [perl-win32-gui-users] The skin module From: Brian Millham <bmillham@hu...> - 2006-04-14 02:48 Thanx for looking at it Jez, and for opening the tracker item. Should I consider adding Win32::GUI::Skin to Sourceforge, or is it to = early for that? Has anyone else looked at it yet? This is my first real attempt to = create a module, so I don't know it I really did things right. I know that the = code works, but could I have done it better?? I've made the changes to allow Skin.pm to be placed in the Win32/GUI directory. I haven't placed the new version on my site yet. I'm not = going to make any more updates, until several people have tested this, and = think that I'm on the right track. I will work on creating some documentation over the next few days... = I'll let everyone know once I've done that. Brian Millham This message traveled at least 44,000 miles to reach you! Creator of the DW6000 Monitor http://www.millham.net/dw6000 bmillham@... -----Original Message----- From: Jeremy White [mailto:jez_white@... Sent: Thursday, April 13, 2006 2:32 AM To: bmillham@...; perl-win32-gui-users@... Subject: RE: [perl-win32-gui-users] The skin module >The reason I'm asking is that I'd like to proceed making the module >Win32::GUI::Skin. I'd also like to start adding more controls. I = don't >want to do this until I know that the basic module is looking good. I had a quick look and it seems fine - although I didn't have time to do = a=20 proper look. I did raise a tracker item for ExtCreateRegion, SetWindowPos functions = so=20 future versions of Win32::GUI::Skin don't have a dependency on = Win32::API.=20 If you need more functions, just add them to this item. Hopefully I'll = have=20 some spare time to implement them before V 1.4. http://sourceforge.net/tracker/index.php?func=3Ddetail&atid=3D366572&aid=3D= 1469648 &group_id=3D16572 Cheers, jez. --- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0615-2, 04/12/2006 Tested on: 4/13/2006 6:02:58 AM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0615-2, 04/12/2006 Tested on: 4/13/2006 10:46:09 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com

Re: [win32-gui] RE: [perl-win32-gui-users] The skin module From: Robert May <rmay@po...> - 2006-04-18 19:41 Jeremy White wrote: > I did raise a tracker item for ExtCreateRegion, SetWindowPos functions > so future versions of Win32::GUI::Skin don't have a dependency on > Win32::API. If you need more functions, just add them to this item. > Hopefully I'll have some spare time to implement them before V 1.4. I've got a SetWindowPos patch from Reini sitting here, so will tidy that up and apply it. That just leaves the ExtCreateRegion work. Regards, Rob.

Re: [win32-gui] RE: [perl-win32-gui-users] The skin module From: Robert May <rmay@po...> - 2006-04-18 20:24 Brian Millham wrote: > Hi again, > I see the quite a few people checked out my page about creating a skinfile > for use with my Skin module. I realize that the documentation needs a lot > of work... > > Has anyone tried to play with this yet? I've just run it up. Win98, AS Perl 5.8.7 (build 813). Looks pretty! > Have some of you who are more familiar with creating modules looked at the > code in Skin.pm. Am I on the right track here for creating a true > Win32::GUI::Skin module? Looks good so far ... some comments from a very quick skin of the code, and in no particular order: (1) Use the Carp module, rather than warn/die in your PM file, so that warnings are reported from the user code perspective (if it's a user problem, of course. If it's a module problem then warn/die are fine) (2) It looks like your SetEvent('Paint', ...) call in the constructor cause a closure over $self, and does a GetDC that gets a DC that is not released until the program finishes. You may have intended this for speed, but if so it would be better to create a new class with the calss style CS_OWNDC, rather that hogging a shared resource. (3) When storing your own instance data in the module I'd start the hash variable names with something other than '-' (I tend to use '_') to avoid any possible future clash with Win32::GUI instance data. See also my (to be written) response to Jeremy about instance data. (4) You don't need to provide a Version function - you'll get one automatically inherited from 'Universal' - you just need the $Skin::VERSION variable set.. Change my $VERSION = eval("0.1"); to our $VERSION = 0.10; 2 decimal paces on $VERSION is more CPAN friendly. Additionally, you don't need the eval, unless you want to use the CPAN 'alpha' notation with versions like 0.10_01, in which case do: our $VERSION = "0.10_01"; # for MakeMaker $VERSION = eval $VERSION; # for Perl (See perldoc perlmodstyle. perlnewmod, perlmod, perlmodlib are also good reading) (5) You'll need a Makefile.PL eventually (I can help here if you need it) so that the standard perl Makefile.PL make make test make install incantation works. This also makes it easy to generate a PPM for easy distribution to ActiveState perl users. (6) Tests? At least test that the module loads with no errors - I guess that testing much else will be hard. (7) Documentation - but I see you already chastised yourself on this one. (8) name class private methods starting with an underscore - Test::Pod::Coverage ignores such functions and doesn't insist you write documentation for it. Regards, Rob.

RE: [win32-gui] RE: [perl-win32-gui-users] The skin module From: Brian Millham <bmillham@hu...> - 2006-04-19 01:57 Thank you for the suggestions Rob! I'm working on incorporating the suggestions that you made. Once I'm to the point of creating the Makefile and PPM, I'll probably = need some help. I'll also have to do some reading up on testing... BTW, when I made the change to allow the module to be true = Win32::GUI::Skin, I had to add: *Skin:: =3D \%Win32::GUI::Skin::; to make it work. (I figured that out from looking through GUI.pm) Why? About documentation. I've created separate POD documents. I've noticed that GUI.pm doesn't contain the POD. It this something that happens = during install (POD is extracted and removed from the original code), or just = the way the GUI.pm was done? I realize that it's a basic question, but this is my first attempt at a = real module. Brian Millham This message traveled at least 44,000 miles to reach you! Creator of the DW6000 Monitor http://www.millham.net/dw6000 bmillham@... -----Original Message----- From: Robert May [mailto:rmay@... Sent: Tuesday, April 18, 2006 4:24 PM To: Brian Millham Cc: perl-win32-gui-users@... Subject: Re: [win32-gui] RE: [perl-win32-gui-users] The skin module Brian Millham wrote: > Hi again, > I see the quite a few people checked out my page about creating a = skinfile > for use with my Skin module. I realize that the documentation needs a = lot > of work... >=20 > Has anyone tried to play with this yet? I've just run it up. Win98, AS Perl 5.8.7 (build 813). Looks pretty! > Have some of you who are more familiar with creating modules looked at = the > code in Skin.pm. Am I on the right track here for creating a true > Win32::GUI::Skin module? Looks good so far ... some comments from a very quick skin of the code, = and in no particular order: (1) Use the Carp module, rather than warn/die in your PM file, so that=20 warnings are reported from the user code perspective (if it's a user=20 problem, of course. If it's a module problem then warn/die are fine) (2) It looks like your SetEvent('Paint', ...) call in the constructor=20 cause a closure over $self, and does a GetDC that gets a DC that is not=20 released until the program finishes. You may have intended this for=20 speed, but if so it would be better to create a new class with the calss = style CS_OWNDC, rather that hogging a shared resource. (3) When storing your own instance data in the module I'd start the hash = variable names with something other than '-' (I tend to use '_') to=20 avoid any possible future clash with Win32::GUI instance data. See also = my (to be written) response to Jeremy about instance data. (4) You don't need to provide a Version function - you'll get one=20 automatically inherited from 'Universal' - you just need the=20 $Skin::VERSION variable set.. Change my $VERSION =3D eval("0.1"); to our $VERSION =3D 0.10; 2 decimal paces on $VERSION is more CPAN friendly. Additionally, you=20 don't need the eval, unless you want to use the CPAN 'alpha' notation=20 with versions like 0.10_01, in which case do: our $VERSION =3D "0.10_01"; # for MakeMaker $VERSION =3D eval $VERSION; # for Perl (See perldoc perlmodstyle. perlnewmod, perlmod, perlmodlib are also=20 good reading) (5) You'll need a Makefile.PL eventually (I can help here if you need=20 it) so that the standard perl Makefile.PL make make test make install incantation works. This also makes it easy to generate a PPM for easy=20 distribution to ActiveState perl users. (6) Tests? At least test that the module loads with no errors - I guess = that testing much else will be hard. (7) Documentation - but I see you already chastised yourself on this = one. (8) name class private methods starting with an underscore -=20 Test::Pod::Coverage ignores such functions and doesn't insist you write=20 documentation for it. Regards, Rob. --- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0616-2, 04/18/2006 Tested on: 4/18/2006 5:05:29 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0616-2, 04/18/2006 Tested on: 4/18/2006 9:55:59 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com

Re: [win32-gui] RE: [perl-win32-gui-users] The skin module From: Robert May <rmay@po...> - 2006-04-19 19:51 Brian Millham wrote: > Thank you for the suggestions Rob! You're welcome. Thank you for the interest in furthering the Win32::GUI cause. > Once I'm to the point of creating the Makefile and PPM, I'll probably need > some help. No problems - contact me off list when you are ready for this. > I'll also have to do some reading up on testing... perldoc Test::Tutorial is a good starting place. > BTW, when I made the change to allow the module to be true Win32::GUI::Skin, > I had to add: > *Skin:: = \%Win32::GUI::Skin::; You shouldn't need to do this. It aliases everything in the Win32::GUI::Skin package into the Skin package. The entry in GUI.pm is historical - I assume that the module was originally called GUI, and there was legacy code to support. It's one of (many) things that I want to remove from Win32::GUI. What errors do you get if you don't do this? > About documentation. I've created separate POD documents. I've noticed > that GUI.pm doesn't contain the POD. It this something that happens during > install (POD is extracted and removed from the original code), or just the > way the GUI.pm was done? Just the way GUI.pm is done - the source for the POD is extracted by a script from a number of locations (GUI.pm, GUI.xs and some C source files) and built into GUI.pod. Either is acceptable, but it's more usual to include the pod documentation near the code it documents in the PM file. Regards, Rob.

[perl-win32-gui-users] fonts and menus From: darrik <darrik@my...> - 2006-04-23 05:06 most win32::gui objects take the -font option. wondering if there's a way to set menu fonts, especially popup menus. i've tried specifying the -font option to individual menu items, a la: my $menu=Win32::GUI::Menu( "file" => "fileMenu", ">exit" => { -name => "fileExit", -font => $fontObject... ); i've tried $menu->SetFont($fontObject); i've tried $menu->Change(-font => $fontObject); nothing seems to work and i wondered if the font was hard-coded into the menu-object or something. what ridiculously easy thing did i overlook this time? ;) any help? ~darrik

RE: [win32-gui] RE: [perl-win32-gui-users] The skin module From: Brian Millham <bmillham@hu...> - 2006-04-27 01:02 I've got the Makefile ready to go, and have created the POD = documentation (in Skin.pm), and all the suggested changes. I've also taken care of the problem with "*Skin:: =3D ...". It's no = longer in the module Now, should I just put the file created by "nmake dist" on my site, or should I try and put it on CPAN? Or should I create a PPM? (probably = the best option, since not everyone has make/nmake) Making the Skin module CPAN compatible required me to make changes to my = CVS environment, so the CVS revisions changed. I don't see this as a = problem, since the module is new. (How do you decide on version numbers with Win32::GUI? Do you use the CVS revisions, or do you create a tag in = CVS?) We probably need to take this off-list at this point (with Rob), unless others are interested. BTW, no-one answered my way off topic question: Anyone a Doctor Who fan? Brian Millham This message traveled at least 44,000 miles to reach you! Creator of the DW6000 Monitor http://www.millham.net/dw6000 bmillham@... -----Original Message----- From: Robert May [mailto:rmay@... Sent: Wednesday, April 19, 2006 3:51 PM To: Brian Millham Cc: perl-win32-gui-users@... Subject: Re: [win32-gui] RE: [perl-win32-gui-users] The skin module Brian Millham wrote: > Thank you for the suggestions Rob! You're welcome. Thank you for the interest in furthering the Win32::GUI = cause. > Once I'm to the point of creating the Makefile and PPM, I'll probably = need > some help. No problems - contact me off list when you are ready for this. > I'll also have to do some reading up on testing... perldoc Test::Tutorial is a good starting place. > BTW, when I made the change to allow the module to be true Win32::GUI::Skin, > I had to add: > *Skin:: =3D \%Win32::GUI::Skin::; You shouldn't need to do this. It aliases everything in the=20 Win32::GUI::Skin package into the Skin package. The entry in GUI.pm is=20 historical - I assume that the module was originally called GUI, and=20 there was legacy code to support. It's one of (many) things that I want = to remove from Win32::GUI. What errors do you get if you don't do this? > About documentation. I've created separate POD documents. I've = noticed > that GUI.pm doesn't contain the POD. It this something that happens during > install (POD is extracted and removed from the original code), or just = the > way the GUI.pm was done? Just the way GUI.pm is done - the source for the POD is extracted by a=20 script from a number of locations (GUI.pm, GUI.xs and some C source=20 files) and built into GUI.pod. Either is acceptable, but it's more usual to include the pod=20 documentation near the code it documents in the PM file. Regards, Rob. --- avast! Antivirus: Inbound message clean. Virus Database (VPS): 0616-2, 04/18/2006 Tested on: 4/19/2006 5:03:12 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0617-2, 04/26/2006 Tested on: 4/26/2006 9:01:04 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com

4 messages have been excluded from this view by a project administrator.