I think those are very valid points Jeff. thanks for reminding us. Chip
_____ From: Jeff Weiss [mailto:[email protected]] Sent: Wednesday, March 31, 2010 12:32 AM To: [email protected] Subject: script file naming conventions I would like to mention a possible problem that I am seeing with naming files associated with scripts. The McTwit and Skype packages seem to have a file naming conflict. Both scripts have a file called history.txt. When I attempt to install one package, I am informed that the other package must be removed. Do you wish to continue? I would like to propose, that as a naming convention, wherever possible, all files in a script package have the same base name. Such as: SkypeHistory.txt and McTwitHistory.txt. I would like to propose that we do this for all .wav files, etc. This is already being done with the .vbs, .xml, and .ini files--why not extend this concept to other files as well. I know that this might not always be possible, say for example some of the tools that Jamal has added to the HomerSharedObject package are utilities which are included and therefore, should probably keep their original names. Another naming problem which I have seen is that both the Skype script and the SkypeInternational script both seem to have the same Package name of Skype.wepm. If people do like I often do and use the installPackages script to download all of the new and updated packages, both are downloaded. Since the Skype script name is alphabeticly before the SkypeInternational script name, I was ending up with the international version instead of the newer English version that I wanted. I would appreciate your comments, and my only goal here is to see that all of your hard work can be put to best use by the end users. Jeff Weiss No virus found in this outgoing message Checked by PC Tools AntiVirus (6.1.0.25 - 6.14580). http://www.pctools.com/free-antivirus/
