We author batch files that our Build Managers can use to compile all of our binaries, but I recently ran into a issue where I wanted to give them an option of providing some, or all, of the arguments needed to run the batch file.  If some were left out, then I would use some kind of default values.

Because of this, I wanted to use the command line pattern of -arg1=value1 -arg2=value2, which is not natively supported in a simple batch file.  Furthermore, I didn’t want to force a set sequence, so they could also use -arg2=value2 -arg1=value1.

It took some creative license (i.e. hacks) to get this to work correctly, but now I can use a standard command line argument pattern when creating these batch files.

Here’s the complete solution.

************************
UPDATE: I also added in the ability to provide option flags in addition to name/value pairs.

Syntax:  BATCH -project=MyProject -target=compile -sdkpath=C:\Flex\sdk -e -o
************************

ECHO OFF
CLS

REM =============================================================================
REM  Set default (empty) values for the variables that will be used to hold the
REM  values specified in the command line arguments.
REM =============================================================================
SET PROJECT=
SET TARGET=
SET SDKPATH=
SET EMAILLOG=
SET REMOTE=false

:PARSEARGUMENTS

REM =============================================================================
REM  Concatenate arguments 1 and 2 with an equals sign unless it is an option
REM  flag which we determine by looking at %2 and seeing if it starts with -
REM =============================================================================
SET ARGUMENT2=%2
if "%ARGUMENT2:~0,1%" == "-" (
    SET commandline=%1=
    SET ARGUMENTTYPE=single
) else (
    SET commandline=%1=%2
    SET ARGUMENTTYPE=double
)

REM =============================================================================
REM  If the first argument is just an equals sign, we've parsed all the arguments
REM =============================================================================
IF "commandline%" == "=" GOTO DONEPARSING

REM =============================================================================
REM  Clear out the values for the switch and the value
REM =============================================================================
SET SWITCH=
SET VALUE=

REM =============================================================================
REM  Using the equals sign as the delimiter, set the SWITCH variable to the
REM  argument name, and the VALUE variable to the argument value
REM =============================================================================
FOR /f "tokens=1,2 delims==" %%a IN ("%commandline%") DO SET SWITCH=%%a&SET VALUE=%%b

REM =============================================================================
REM  Put an IF condition for each command line argument that you are expecting
REM  on the command line, and set the corresponding variable to what's contained
REM  in the VALUE variable.
REM
REM  Then use the SHIFT command twice to move to the next name/value pair.
REM =============================================================================
IF "%SWITCH%" == "-sdkpath" (
    SET SDKPATH=%VALUE%
    GOTO SHIFTER
) 

IF "%SWITCH%" == "-target" (
    SET TARGET=%VALUE%
    GOTO SHIFTER
)

IF "%SWITCH%" == "-project" (
    SET PROJECT=%VALUE%
    GOTO SHIFTER
)

IF "%SWITCH%" == "-e" (
    SET EMAILLOG=yes
    GOTO SHIFTER
)

:SHIFTER
IF "%ARGUMENTTYPE%" == "single" (
    SHIFT
) ELSE (
    SHIFT
    SHIFT
)

REM =============================================================================
REM  Start the parsing process all over again.
REM =============================================================================
GOTO PARSEARGUMENTS

:DONEPARSING

I’m trying to build a master configuration with an Ant script that will automatically build several child modules. First thing I realize is that I have to override the path properties of the child Ant script with relatives paths from the parent script. Ok, that makes sense since it’s a subtask being called from the scope of the parent, so the paths have to be from that directory.

Then I try to call COMPC in the child Ant script. It chokes hard with:

[compc] command line: Error: unable to open 'api/src/Manifest.xml'

“That’s odd,” I think. I know I’m passing it the right path (contained in the ${src.dir} property). However, just to check, let’s echo out the contents of the path I’m sending to the child script.

<fileset id="dir.contents" dir="${src.dir}" includes="*"/>
<property name="file.name" refid="dir.contents"/>
<echo>${file.name}</echo>

I run the script again, and lo and behold, guess what echoes out?

 [echo] Manifest.xml

wtf?

Ant says that the file exists in the path contained in the ${src.dir} property, but the COMPC task says it doesn’t exist?

<compc output="${build.dir}/${build.file}" debug="false">
	<include-namespaces uri="${namespace}" />
	<namespace uri="${namespace}" manifest="${src.dir}/${manifest.filename}" />
   ...

Still haven’t figured this one out, because I’m now stuck in the process of throwing darts with a blindfold on, simply guessing which directory COMPC thinks it’s starting from, because, of course, there’s no way to output anything from inside the COMPC task.

ARGH!!!

I’ve used several automated build tools over these many years, and even though I’ve only been using TeamCity for <24 hours, I can honestly say it's the easiest one I've ever used.

During 2 hours last night, and 3 hours this morning, I was able to set up every project we have, convert the Ant scripts, establish the proper dependencies, and have build triggers set up for each one.

Additionally, the Eclipse plugin they made is professional and bug-free. Here's a quick screenshot I took last night while I was getting all the projects configured.

It even includes support for Jabber, so I’m installing a test server on my machine to see how that works. Hard to imagine that I could have a complete build management server set up, including notifications, and integration with task management within 48 hours – cuz that’s how long I think it’s going to take.

Those are the two things I’ve always wanted from a wireframing tool. I just want to sit down, and with the image in my head, be able to dump it on the screen in a matter of minutes. No tool – and I’ve looked at many tools over the years – provided me with both features. Most often, it was the “do it fast” that failed.

Finally!

Not so with Balsamiq Mockups. This is a tools written by people who use it and you can tell. It’s got a good, if not exhaustive, library of elements. It’s got a highly intelligent editor. The properties are minimal, but on target. Most importantly, you can export/save the wireframe in the formats that architects and interactive engineers use.

Example

The folks internally wanted me to throw together a quick Flex app for effort metrics on our team. After talking about basic requirements, I had an image in my head of what the UI might look like. Nothing is more frustrating that having this image in your head and (unless you use paper and pencil) not being able to realize it for 45 minutes.

I did this mockup in just around 8 minutes.

Recommend

I very rarely endorse a product publicly, and I really have to love it to do so. This is one of those cases. I highly recommend that you demo this product, and if you are ever responsible for coming up with wireframes, conceptual designs, or just any kind of visual aid for architecting applications, you will love this app.

Open Resource (CTRL+SHIFT+R)

This shortcut opens a dialog where you can type in the first few letters of a filename you want to open and a list of matching filenames show up beneath. Alternatively, you can highlight a filename in your code, and it will be pre-populated in the dialog search field.

Working Sets

If you work in an environment with many projects going on at once, your Navigator window can quickly get cluttered and confusing. The best way around this is working sets. You can group 1 or more projects into a working set that, when chosen, will only show those projects in the Navigator.

Outline View

Have large XML or Javascript files? Having a hard time finding methods or elements in the haze of code? The Outline view will save you plenty of time.

Quick Switch (CTRL+E)

Whether you’re working on fixing a system-wide bug, or making style changes to many pages in your site, sometimes you just can’t help having 10 files open at one time. Since Eclipse will only show 6 of those in the tabs, you can easily switch to any of the files with this handy shortcut.

Granted I’m still running the 2001 version of Visio for Enterprise Architects, so I’m sure that recent releases have more formats in which to view an object model. However, for the time being, I’m having fun with opening all my old schemas and changing their format.

To get your model in this format, you choose the following menu option:
Database > Options > Document…

Then in the General tab, select IDEF1X as the symbol set.

Check out the YSlow Firefox Add-On

In conjunction with the Firebug Add-On (please tell me you’re using Firebug) your arsenal for speeding up your web pages just got bigger.  Below is a screenshot of some of the things it exposes for you.

People don’t switch development tools for two reasons.

1. It’s time consuming
2. It requires you to wipe your habitual slate clean

The majority of people that I have worked with over the years don’t switch because their current tool, “gets the job done”. They have structured their workflow in such a way to, in their minds, maximize their usage of the tool. If they can do their job right now with no impediments, and get everything done on time, then what’s the point in trying something new?

Perfectly valid point. If you have no interest in learning a new tool for development, why the heck should you?

Unfortunately, there is the small, but vociferous group of developers that DO try out something new, find one or two roadblocks and then rant and rave about how bad the tool is. For example, I worked with a fellow that was still using CF Studio in 2006. It worked for him. He saw my Eclipse installation and thought it looked cool because of all the plugins I was using. He decided to give it a try, so he installed Eclipse and started downloading the list of plugins that I had provided to him.

After only 24 (3 days) hours of experience with Eclipse, he declared that it was the worst tool he had ever used. He was frustrated with the unfamiliar UI, the endless options that could be configured, the new key mappings that he was forced to learn, and lack of features. I spent a day trying to show him how easily these perceived hurdles could be overcome, but he had already made up his mind.

Many of his complaints are mirrored in some of the comments I hear people say about any tool that they “hate”.

I’m one of a, apparently, small group of people who actually take the time to work with a tool for weeks, or even months before I make up my mind about it. I’ve tried a plethora of tools over the years – starting with CF Studio, I’ve tried HomeSite, Dreamweaver, Eclipse, Code Chameleon, and a few others that I’ve forgotten about. I’d pore over every feature of these tools, trying to squeeze every ounce of productivity that I could out of them. I’d install plugins, extensions, helper tools, wizards, you name it. I’d never say die in the hopes that I have finally found a tool that fits how I want to work.

At this point in time, Eclipse is that tool. I’m able to get to it work the way I want, instead of the other way around much more so than anything I’ve used in the past. Admittedly, I do a lot more than ColdFusion development, so my opinion probably isn’t worth as much as someone who does only that.

I have the following features installed.

• Java Development (default installation)
• JSEclipse
• CFEclipse
• QuickREx
• SQL Explorer
• Subclipse
• Mylyn
• Aptana HTML Editor
• SWeDE
• XML Buddy

I use all of the plugins every day and having them all contained within one IDE is perfect for how I work. There are people within my company right now that would absolutely hate Eclipse. It doesn’t fit their work style or their (simplistic?) needs.

The point I’m clumsily trying to make is that before you degrade into saying what you don’t like about Tool X, try stating humbly what you do like about Tool Y and why it’s a great idea for a new IDE. Brush that chip off of your shoulder and remember that there is always someone smarter/wittier/more productive/more inventive/more creative than you.

http://extjs.com/blog/2007/09/06/ext-20-a-preview/

Bad News

As of 09/29/2007, Mylyn will only integrate with Trac 0.9 or 0.10. If you install the latest dev version of 0.11, you won’t be able to get Mylyn to connect to the Trac repository. I use Trac 0.10

Install Trac

1. Install Python 2.4.4
2. Install ez_setup.py
3. Via command line get to the Scripts directory of your Python installation and execute the following command:

   easy_install http://svn.edgewall.com/repos/trac/trunk/

4. Execute the following command

   easy_install pysqlite

5. Execute the following command:

   easy_install -Z http://subversion.tigris.org/downloads/svn-python-1.4.2.win32-py2.4.exe

6. Create a directory at the root of the work drive named TracProjects
7. Create a subdirectory for your first project
8. Go back to your command prompt and execute the following command:

   trac-admin.py D:\\TracProjects\\{project directory} initenv

9. Fill out project name, then defaults for the rest until asked for path to SVN repository. Fill that in.

Your Trac environment is now set up, but you need to install Apache to serve up the site for your project. Well, need is a strong word since Trac has a built-in server, but it’s only recommended for testing.

Install and Configure Apache

1. Install Apache 2.2
2. Download and install mod_python. Be sure to grab the right version for your Python/Apache versions: mod_python-3.3.1.win32-py2.4-Apache2.2.exe
3. Add the following configuration to Apache

   LoadModule python_module modules/mod_python.so

4. Add the following configuration to Apache

    <Location /projects>
       SetHandler mod_python
       PythonInterpreter main_interpreter
       PythonHandler trac.web.modpython_frontend
       PythonOption TracEnvParentDir D:\\TracProjects
       PythonOption TracUriRoot /projects
    </Location>

5. Add the following configuration to Apache

    <LocationMatch "/projects/[^/]+/login">
       AuthType Basic
       AuthName "Trac"
       AuthUserFile D:\\TracProjects\\{project}\\{project}.htpasswd
       Require valid-user
    </LocationMatch>

Configure Apache Based Security

1. Create the .htpasswd file, referenced in the previous step, by using Apache\bin\htpasswd.exe at the command line:

   htpasswd -c D:\\TracProjects\\{project}\\{project}.htpasswd {username}

2. Add any additional users with the same command without the -c switch

   htpasswd D:\\TracProjects\\{project}\\{project}.htpasswd {username}

You’re all set at this point, just restart Apache so that the configuration changes and security take effect. After it restarts, try to hit your project URL.