Ok, Aaron and others, When downloading a package from script central, I found out that the case of the package that is downloaded is preserved.
When, However, downloading the same package with Jamal's Install Packages script, the script name is changed to lower-case. I did not know that these .wepm package names were case sensitive. Further, it appears to make no difference to the end user of the packages, but only to the script author who will later modify the package. Does this seem to be correct? Jeff Weiss From: Aaron Smith [mailto:[email protected]] Sent: Tuesday, October 26, 2010 12:49 PM To: [email protected] Subject: Re: re-naming script packages Because, as you might have guessed, things are case sensitive. A is not a, and so on. Aaron On 10/26/2010 1:26 PM, Jeff Weiss wrote: Then let me clarify: The only thing that I changed was small letters to capitals. Why should this make any difference? Jeff From: Aaron Smith [mailto:[email protected]] Sent: Tuesday, October 26, 2010 12:09 PM To: [email protected] Subject: Re: re-naming script packages You answered your own question. <grin> The name of your package is stored internally in the package information, so if you rename it, the package no longer matches. Aaron On 10/26/2010 12:03 PM, Jeff Weiss wrote: I would like to ask Aaron and others if there is any reason not to rename script packages? As you know, when you download a script package, at least with Jamal's script, the package name is all in small letters. I often rename my script packages, starting each word with a capital so that it sounds better. Is there a reason not to do this? The reason I ask, when I went to update my TextToClip package, it would not update the version number correctly. Even though I entered 1.4 in the script package, and I had 1.4 in the xml file, it kept showing 1.3. I ended up deleting the package, and creating en entirely new package and now all of the info is correct. I just don't understand why I couldn't update a package which had been renamed by me. Any suggestions or explanations would be appreciated. Thanks, Jeff Weiss -- Aaron Smith Product Support Specialist * Web Development GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 260-489-3671 * gwmicro.com To insure that you receive proper support, please include all past correspondence (where applicable), and any relevant information pertinent to your situation when submitting a problem report to the GW Micro Technical Support Team. -- Aaron Smith Product Support Specialist * Web Development GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 260-489-3671 * gwmicro.com To insure that you receive proper support, please include all past correspondence (where applicable), and any relevant information pertinent to your situation when submitting a problem report to the GW Micro Technical Support Team.
