<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Rockstar on Launchpad Blog</title>
    <link>https://blog.launchpad.net/authors/rockstar/</link>
    <description>News and updates from the Launchpad team</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Nov 2009 18:44:17 +0000</lastBuildDate>
    <atom:link href="https://blog.launchpad.net/feed/authors/rockstar/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>November Lazr-js Sprint Report</title>
      <link>https://blog.launchpad.net/general/november-lazr-js-sprint-report/</link>
      <pubDate>Tue, 17 Nov 2009 18:44:17 +0000</pubDate>
      <dc:creator>Paul Hummer</dc:creator>
      <guid isPermaLink="false">https://blog.launchpad.net/?p=1161</guid>
      <description>&lt;p&gt;Last week, members of the Launchpad team got together with members of other teams across Canonical to sprint on &lt;a href=&#34;http://launchpad.net/lazr-js&#34; title=&#34;Lazr-js in Launchpad&#34;&gt;lazr-js&lt;/a&gt;.  lazr-js is the library the Launchpad team created on top of the Yahoo User Interface 3.0 javascript library to provide a richer user experience.  For instance, the &amp;ldquo;widgets&amp;rdquo; in lazr-js are used in bug pages to help users change bug status and importance without leaving the bug page, and allowing users to subscribe to a branch without leaving the branch page.&lt;/p&gt;
&lt;p&gt;One of the big things we focused on with lazr-js last week was integration into apps other than Launchpad.  We worked with members of the internal Canonical webapp teams, the Ubuntu One team, and the Landscape team to get lazr-js integrated into those apps, and find the issues that anyone would have while trying to integrate lazr-js into their own app.&lt;/p&gt;
&lt;p&gt;As we focused on integration, we were able to see where we could make lazr-js more generic and easier to use.  We were able to find ways to automate the tests we have written for the code in lazr-js.  We also focused on fixing the bugs in lazr-js that would prevent Internet Explorer users from benefiting from lazr-js enhancements to an application, but we still have much to do in the way of cross-browser compatibility.  We&amp;rsquo;ll be working towards browser compatibility in the next few months, and welcome any contributions from the community.&lt;/p&gt;
&lt;p&gt;The sprint was a huge success.  At the beginning of the week, lazr-js was a Launchpad library, and at the end, it became a library that can be used by anyone that wants to have a rich browser experience for their webapp.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
