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:: = ...". 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 [EMAIL PROTECTED] -----Original Message----- From: Robert May [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 19, 2006 3:51 PM To: Brian Millham Cc: perl-win32-gui-users@lists.sourceforge.net 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:: = \%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. --- 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
