Skip navigation

Monthly Archives: March 2009

I was excited to read this article on “continuous deployment” in terms of software development.  Excited because in most respects, we’re already following some of it’s practices.  However, I think we here at Frontier could probably stand some more testing and the ability to have the server reject a change based on certain criteria. 

Along other lines, Ars technica is reporting that Google chrome should be out for OS X as early as this fall

Nettuts+ has 10 Rare HTML tags you should now about.  Most intriguing to me?  #7 fieldset and #4 Address.  I don’t use those and, where appropriate, I should. 

There’s a number of different ways to test Internet Explorer via OS X.  I think devthought has got the best one

devthought lists the 4 stages of programming competence.  I rate myself at stage 2, consciously incompetent.

Can you get better?  I thought I had you figured out.  But again today you showed me that you are more well planned and made than I originally thought. 

Coda’s sharing feature is really very nice.  You can share via Bonjour over a network, or by inviting another Coda user.  Changes are made in real time, much like Google spreadsheets.  This, along with the ability to tie into Subversion and other source control setups, Coda just earned more “Pwnage Points” as we continue to never look back from Dreamweaver

I mean, I guess DW has it’s place in things.  But in terms of simplicity, ease of use, and over-all making-my-coding-life-easier I’m finding it hard to be beat. 

I was attempting to rewrite our page lock function (designed to prohibit multiple people from submitting changes to a job at once) using jQuery and had a time trying to get an AJAX call to run with the $(window).unload function. 

After much searching and some IRC chat on the #jQuery irc channel, I finally got it. 

//bind action to page unload

$(window).bind(‘beforeunload’,function(){

   $.ajax({

   type: “GET”,
   url: “includes/PageLock.php”,
   cache: false,
   async: false,
   data: “Job=ID, Mode=’unlock'”,

   });
});

The keys here were to set the ‘cache’ to ‘false’ as well as ‘async’.  This does two things:  1) prohibits the browser from caching the page being called and 2) runs the AJAX synchronously, thus freezing the browser until the call is finished.  Now, whenever a user leaves a page, the page can be unlocked.  I also included a modal window that displays a processing dialog so that the user knows what’s going on.