AJAX: just another buzzword

[Update 2011: OK, so back in 2005 I was skeptical of AJAX. At the time you needed to truly be able to write javascript in order to deal with the browser compatibility issues. The situation with the GAP site failing was a major foobar on their part and showed how much effort it took to do AJAX appropriately with things like graceful degradation. Today of course we have one of the most awesome libraries in jQuery. Which handles all the nastiness of browser problems for the most part. Today it is possible to do things with jQuery that really lead to fantastic interaction experiences. There are many other fine JS libraries and frameworks, but jQuery has really solved the problem in a way that simplifies and yet still provides powerful control to the designer/developer.]

Original Article:
Recently, I’ve had conversations with a few of my developer friends who are all a twitter about AJAX. Saying how great it is and all the cool things Google is doing with it. Honestly, after taking a real close look at it, I find it to be hardly more than another buzzword. It simply does not offer anything of real value for web development. Yes, it can make interfacing with certain web applications smoother, and it solves some problems inherent in web applications. However, it introduces a whole set of other problems, that in my opinion, make it widely unsuitable for most work.

Continue reading

More Automator

I worked a little more with automator (when I should have been studying regression analysis)… and have come up with a cool new automator. This incorporates an undocumented aspect of automator, so it took some trial and error to figure out. Basically, I wanted something that would allow me to turn a request to view a man page into a pdf file for easy printing and viewing in the gui side of Mac OS X. Only a unix geek could love the man page as it is… for unix newbies though, it can be quite frustrating. Personally, I am use to man pages, but I still like to print some out now and then and converting them to pdf allows me to access them without opening terminal (not that you wouldn’t probably have terminal open anyway).

So I wanted to find a way to make a man page into a pdf. Of course you can do this from the terminal, but where’s the fun in that (plus you have to remember the commands each time you want to do this). There is a free GUI utility called ManOpener that allows you to view man pages easily as well, and is much more featured than this automator tool. But if all you want (as I did) was a man page made into a pdf, then this is what you need to do;

  1. Open Automator, from the Library column select TextEdit. From the actions drag “Ask for Text” over to the workflow area.
    • In the question field type “Enter man page name?” or something to indicate what you need to enter
    • You can leave the default field empty or enter something that will serve as a reminder of what to enter
    • Check the require answer box
  2. Next, from the Library column select Automator, then from the actions drag over the “Run Shell Script” to the workflow after the previous item. Type or copy & paste the following as one line, modifying the paths so that they point to your preferred locations (include the quote marks this time);

    man -t $@ > /hardrive/Users/Shared/manpages/$@.ps | echo -n “harddrive:Users:Shared:manpages:”$@”.ps”

    Set the “Pass Input” to “as arguments”

    Note: The $@ takes the value entered in the “Ask for Text” and runs it as a shell command. The first part which calls the man page then passes it to a postscript file named with the name of the man you are looking for, then it echoes out the path to the next function. The echoed path has to be in the style of the Mac OS drive path reference which uses “:” instead of slashes “/”.

  3. Last select Finder from the Library column and drag “Open Finder Items” to the workflow in the last place. Set the “open with” field to the Preview application. The path passed from the previous action will be opened in Preview converting it into a pdf.

You are ready to test, click the run arrow and try it out. If everything works, the requested man page will be open in Preview at this point. You can either save it or discard it after use. You can get fancy and do things like check for existing ps files or remove the ps file after it is converted. But this gives you the idea of what fun you can have with automator and how it can make working with unix fun. Be sure to save your workflow and make it readily accessible on your dock or wherever you like to put things to be accessed often.

Mac OS X Automator: Combining PDF files for free

When I first heard about Automator it sounded cool, but I wasn’t sure what I could use it for personally. After I had upgraded to Tiger, I got around to looking at automator and to be honest, I didn’t see anything that would really help me. I looked at the sample workflows and there was nothing that applied to my everyday or even once in a while tasks.

However, the other day I was in need of combining a couple of pdf files. I knew there was a way to do this in Mac OS X, so I set about searching the internet. I thought I had seen a terminal command process to combine pdfs, but I found instead some instructions on how to do it with automator. So I am posting here in case the reference gets lost from somewhere else…

  1. First open Automator, select Finder in the Library and drag “Ask for Finder items”, check the multiple option.
  2. Then select PDF in the Library and drag “Combine PDF Pages” set to Appending pages
  3. Then go back to the Finder listing in the Library and drag the “Rename Finder Items” set things the way you would like here
  4. Then drag a “Move Finder Items” and set it to where you would like the new file to end up

Save your workflow and then run it. Pretty cool. Other variations could substitute Get Folder Contents for step 1. Then you can just drop files you want to combine into that folder and run the command. You can include the Sort Finder Items to change the order the pdf files are combined (or you could just rename them in the finder). Now that I have a taste and feel for what Automator can really do, I have something else to play with/do in my non-existant free time. Here is the forum where I found this http://www.macosx.com/forums/showthread.php?t=239682.

Podcasting

My current workplace wants to get started doing podcasting. So I am setting up a podcast rss file. The unique thing here is that it will be dynamically updated. The audio will be saved to the server automatically. Then a script I am writing will check the directory for the 30 most recent files and then pull from a database a title and a description/summary that is entered by the production staff. All of this will be formatted into a rss feed that is usable by iTunes or other podcast aggregating software.

Continue reading

In Search of a Better Editor

I have used Windows for my work system (it is required) for over 8 years now. I have migrated through a number of code editors as my abilities and needs have changed over time. I have used WebEdit, HomeSite/ColdFusion, and now UltraEdit. On the Mac it has been BBEdit all the way. Yet, especially in the last year or so, I have been looking for something on the Mac that would work more like UltraEdit on windows. Specifically, something that would allow opening more than 1 file via FTP at a time. And didn’t require pallettes to access common code snippets (I like keyboard shortcuts). Simply, the macro features of BBEdit just don’t cut it for me. I should mention the version of BBEdit I have is v6.0… and it is a great editor. So perhaps if I weren’t too cheap to upgrade, I may find some of these features added in the most current version.

Continue reading