Atlanta ColdFusion User Group hosts Preview of upcoming ColdFusion and Flex releases
ColdFusion , Flex / AIR , Flash , Web Tech. No Comments »The Atlanta ColdFusion User Group (www.acfug.org) has just announced their June Meeting: Ben Forta will be discussing new features of the impending release of ColdFusion and Flex.
The meeting will be held in the echoEleven facilities in Buckhead. Rumor has it that there will be an after-party for those interested, complete with Wii, Karaoke and adult beverages.
Usually, eLearning courses are deployed in SCORM 1.2 format. One of the features of this format is that it can easily determine which files are necessary to run the course. Often, I see this data placed into the manifest in an incomplete format. For example, only the .htm file will be listed in this section, but not the supporting files (.css, .js, etc.).
In searching for a way of quickly knowing which files are used, I have come across the following shell command (sorry PC users) which will read out the entire directory contents and format it correctly for SCORM 1.2:
find ./html -type f -exec echo "<file href=\""{}"\" />" \;
This simply lists out all the files in the directory tree, and surrounds them w/the appropriate XML so that they can be dropped into the manifest. (It also assumes that all your files in are the "html" subdirectory, relative to your manifest. Adjust accordingly for your setup.)
What this will not do is provide you with knowledge of which assets really are used; if you have extra files inside the course directories that are not used (e.g. storyboards, thumbs.db, .DS_Store), they will also be listed. Best to purge those before running the script, unless you really intent to package them with your corse. (Listing them in the manifest, but not packaging them results in an invalid SCORM package.)
Often when developing, I want to see exactly what Coldfusion is doing in real time w/o having to trace this out to the command line. This is particularly usefull when developing Flex apps, where you cannot see what the server is doing.
Unfornutately, I keep losing the instructions on how to start up CF in OS X. There are a lot of other postings out there, but many of them are using the multiserver installation of CF.
So here it is (more for my reference, but perhaps someone else will find it useful:
sudo /Applications/ColdFusion8/runtime/bin/jrun -start coldfusion
2-18-2009
11-17-2008
8-11-2008
7-6-2008
7-6-2008