<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6002.18100" name=GENERATOR></HEAD>
<BODY bgColor=#ffffff>
<DIV>I install some of my scripts. </DIV>
<DIV>Not sure if anyone else uses them.</DIV>
<DIV> </DIV>
<DIV>Nonetheless, I know that for me some of these scripts make cm3 easier to use on Windows.</DIV>
<DIV>For example, I have scripts that:</DIV>
<DIV>1. Start the IDE.</DIV>
<DIV>2. Set up all the paths and environment variables for operating cm3 and Microsoft linker / Visual Studio at the command shell.</DIV>
<DIV>3. Open a cm3 command shell window in a particular folder. I've integrated this with the Explorer context menu for even greater utility.<BR>4. Automate building of multiple packages based on the concept of a project.</DIV>
<DIV>etc.</DIV>
<DIV> </DIV>
<DIV>Perhaps others would have similar scripts that should be available as part of the install.</DIV>
<DIV> </DIV>
<DIV>So, I'm suggesting here that we make a conscious choice on a standardized way for folks to contribute such scripts with the intent that when the installs are built that these scripts get included. End users are free to use the scripts, not use them, or even remove them after the product is installed.</DIV>
<DIV> </DIV>
<DIV>What do others think?</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy Coleburn</DIV>
<DIV><BR>>>> <jay.krell@cornell.edu> 10/27/2009 4:02 AM >>><BR></DIV>
<DIV>None of the scripts are installed.<BR><BR> - Jay (phone<SPAN class=Apple-style-span style="-webkit-composition-fill-color: rgba(175, 192, 227, 0.231373); -webkit-composition-frame-color: rgba(77, 128, 180, 0.231373)">)</SPAN></DIV>
<DIV><BR>On Oct 26, 2009, at 10:10 PM, "Randy Coleburn" <<A href="mailto:rcoleburn@scires.com">rcoleburn@scires.com</A>> wrote:<BR><BR></DIV>
<DIV></DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>I would like to better understand the rationale behind the "scripts" folder in terms of how it is organized and supposed to be used.</DIV>
<DIV> </DIV>
<DIV>Here is the current folder structure:</DIV>
<DIV> </DIV>
<DIV><FONT face="Courier New" size=3>scripts<BR>+---config<BR>+---doc<BR>+---examples<BR>+---iphone<BR>| \---1<BR>+---python<BR>+---regression<BR>\---win</FONT></DIV>
<DIV> </DIV>
<DIV>In the past, I had put some BAT/CMD scripts in the "scripts" folder with the intent that these would be placed in the "bin" folder of the target install. Later, the other subfolders were added, including the one named "win".</DIV>
<DIV> </DIV>
<DIV>It seems there are perhaps multiple intentions for the scripts folder. For example, there are scripts that one would use mainly in setting up, maintaining, or administering cm3. There are other scripts that would be useful for certain target platforms as part of the installed system. There may be other scripts useful for testing.</DIV>
<DIV> </DIV>
<DIV>I am almost finished with testing of a new script I want to be included in the "bin" folder of the installed system on Windows platforms. This script will replace some of the old ones I have out there. It is designed to work with Win2000, WinXP, and Vista, whereas my old scripts don't work well on Vista. I also have some scripts I've built that aid in rebuilding package sets based on the PkgInfo.txt file.</DIV>
<DIV> </DIV>
<DIV>Before I remove my old scripts and replace them with the new ones, I thought it best for us to think about how the scripts folder should be organized.</DIV>
<DIV> </DIV>
<DIV>As a first cut, I propose something along the following lines:</DIV>
<DIV> </DIV>
<DIV><FONT face="Courier New" size=3>scripts</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+---doc = documentation for stuff in the "scripts" folder tree</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+---dev = scripts used for system development, maintenance, admin</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+ +---windows = dev scripts written for Microsoft Windows (BAT, CMD)</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+ +---posix = dev scripts written for unix shell (sh, bash, etc.)</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+ \---python = dev scripts written in python</FONT></DIV>
<DIV>
<DIV><FONT face="Courier New" size=3>+---install = scripts that should be put in "bin" folder of target install</FONT></DIV>
<DIV><FONT face="Courier New" size=3>
<DIV><FONT face="Courier New" size=3>+ +---common = scripts common to all target platforms</FONT></DIV>+ +---windows = BAT/CMD scripts for Microsoft Windows</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+ +---posix = shell scripts for POSIX platforms (sh, bash, etc.)</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+ +---python = scripts written in python (applicable to any platform with python)</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+ \---XXX = scripts for target platform XXX (XXX is name of platform)</FONT></DIV>
<DIV><FONT face="Courier New" size=3>+ (assuming XXX needs something special not covered above)</FONT></DIV>
<DIV>
<DIV><FONT face="Courier New" size=3>\---test = scripts used for regression testing</FONT></DIV>
<DIV><FONT face="Courier New" size=3> +---windows = test scripts written for Microsoft Windows (BAT, CMD)</FONT></DIV>
<DIV><FONT face="Courier New" size=3> +---posix = test scripts written for unix shell (sh, bash, etc.)</FONT></DIV>
<DIV><FONT face="Courier New" size=3> \---python = test scripts written in python</FONT></DIV>
<DIV><FONT face="Courier New" size=3></FONT> </DIV></DIV></DIV>
<DIV>What do you think?</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy Coleburn</DIV>
<DIV> </DIV>
<DIV> </DIV></DIV></BLOCKQUOTE></BODY></HTML>