<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Moves On Rails: Tag Naviagtion</title>
    <link>http://www.movesonrails.com/articles/tag/naviagtion?tag=naviagtion</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>New ways to look at software</description>
    <item>
      <title>Multipage Navigation (or what to do with 24&amp;quot;)</title>
      <description>&lt;p&gt;The third movie of our presentation deserves a seperate blog entry: Multipage navigation.&lt;/p&gt;

&lt;p&gt;Because we sell our webapplication on a 24" Mac, we have a problem. As you all know a webpage designed for 1024 x 768 does not look nice on 1920 x 1280. There is just too much whitespace on the left and right.&lt;/p&gt;

&lt;p&gt;To solve this in Moves, we wrote a javascript library that makes our application function like a book. If you click employees , you'll get a list of employees. Clicking on a single employee will result in that employee being displayed on the right. Just watch the movie and you'll understand it right away:&lt;/p&gt;

&lt;p&gt;&lt;a href="http://www.movesonrails.com/files/MultipageNavigation%20-%20MovesOnRails.com.mov"&gt;3. Multi-page Navigation&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There are still some major issues with this library. Because all the links on the application are parsed on the fly and rewritten to Ajax links, they break our nice URLs and the back button (NOOOO! WHAT DID I TELL YOU ABOUT USING AJAX FOR NAVIGATION!!!). This is something we have accepted for the time being (as it is a closed web application), but it is something we want to fix desperately. We can get away with this for the time being because you usually only want to go back one page, and with our multi-page navigation, this page is already visible. Also, users find the breadcrumb navigation very intiuative. The upside is that our library degrades gracefully: If you don't own a big screen, the application will fall back to the standard behavior. Isn't that cool?&lt;/p&gt;

&lt;p&gt;We will be releasing this javascript library soon on Ruby Forge. Why? Because then the javascript will work out of the box (no Ruby code needs to be changed). You'll be able to get it to work in PHP or Java, but it you'll need to implement some restfullness in your application.&lt;/p&gt;

&lt;p&gt;If you have any remarks or questions, please feel free to email &lt;a href="mailto:andre.foeken@movesonrails.com"&gt;Andre&lt;/a&gt; or me (&lt;a href="bart.tenbrinke@movesonrails.com"&gt;Bart&lt;/a&gt;).&lt;/p&gt;</description>
      <pubDate>Fri, 08 Jun 2007 13:20:00 +0200</pubDate>
      <guid isPermaLink="false">urn:uuid:b00f4e7a-f0a0-45aa-a276-9cc356884df0</guid>
      <author>bart.tenbrinke@movesonrails.com (Bart ten Brinke)</author>
      <link>http://www.movesonrails.com/articles/2007/06/08/multipage-navigation</link>
      <category>Project update</category>
      <category>Multipage Navigation</category>
      <category>RubyEnRails</category>
      <category>Conference</category>
      <category>Multipage</category>
      <category>Naviagtion</category>
    </item>
  </channel>
</rss>
