<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.8.4" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>http://blog.sLajax.com</title>
	<link>http://blog.slajax.com</link>
	<description>secure lightweight ajax solutions</description>
	<pubDate>Wed, 16 Dec 2009 07:39:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
			<item>
		<title>Blast Mojo is Live ! Now with scaffolding!</title>
		<link>http://blog.slajax.com/2009/12/16/blast-radius-mojo-now-open-source-with-mojo-tasks-scaffolding/</link>
        <customfield>../uploads/2009/12/mojo.jpg</customfield>
		<comments>http://blog.slajax.com/2009/12/16/blast-radius-mojo-now-open-source-with-mojo-tasks-scaffolding/#comments</comments>
		<pubDate>Wed, 16 Dec 2009 07:32:44 +0000</pubDate>
		<dc:creator>Kyle</dc:creator>
				<category><![CDATA[applications]]></category>
		<category><![CDATA[blast radius]]></category>
		<category><![CDATA[mojo]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[github]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[sLajax applications]]></category>
		<category><![CDATA[source code]]></category>

		<guid isPermaLink="false">http://blog.slajax.com/?p=127</guid>
		<description><![CDATA[ It seems I gained a lot of traffic a little while ago from a little post [1] I made about Mojo. At that time, it seems the internets got confused [2] and somehow a waterfall [3] effect [4] of misunderstandings [5] revolving around the palm pre operating system arose. Gladly those were all cleared up [6]. 

Since then there has been a lot of work going on behind the scenes by the core team trying to get Mojo open source. They came through a couple weeks ago and now Mojo is official out in the wild [7].

Being an advocate of open source, I used the opportunity to quickly build a scaffolding framework for Mojo called Mojo Tasks [8]. I had talked about doing it for a while, and tested a few difference implementations before I finally settled on the current implementation which you can find on my Git Hub account [9].

All that said, I would like to welcome Mojo  [10]into the open source world and I am very excited to make more contributions to this amazing UI framework.


[1] http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/
[2] http://discussion.treocentral.com/web-os-development/176298-mojo-javascript-palm.html
[3] http://prepoint.wordpress.com/2009/02/01/two-palm-pre-partners-revealed/
[4] http://palmwebosblog.com/palm-pre/start-developing-for-palm-pre-mojo-sdk-based-on-dojo-toolkit/
[5] http://ajaxian.com/archives/palm-mojo-uses-dojo-view-the-source
[6] http://www.precentral.net/truth-about-mojojs-and-blast-radius
[7] http://blastmojo.com
[8] http://github.com/slajax/Mojo-Tasks
[9] http://github.com/slajax/Mojo-Tasks
[10] http://blastmojo.com]]></description>
			<content:encoded><![CDATA[<img src="http://blog.slajax.com/wp-content/uploads/2009/12/mojo.jpg" alt="mojo" title="mojo" width="169" height="81" class="size-full wp-image-124" /> <p style='float:left'>It seems I gained a lot of traffic a little while ago from a little <a href="http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/">post</a> I made about Mojo. At that time, it seems the <a href="http://discussion.treocentral.com/web-os-development/176298-mojo-javascript-palm.html">internets got confused</a> and somehow a <a href="http://prepoint.wordpress.com/2009/02/01/two-palm-pre-partners-revealed/">waterfall</a> <a href="http://palmwebosblog.com/palm-pre/start-developing-for-palm-pre-mojo-sdk-based-on-dojo-toolkit/">effect</a> of <a href="http://ajaxian.com/archives/palm-mojo-uses-dojo-view-the-source">misunderstandings</a> revolving around the palm pre operating system arose. Gladly those were all <a href="http://www.precentral.net/truth-about-mojojs-and-blast-radius">cleared up</a>. </p>

<p>Since then there has been a lot of work going on behind the scenes by the core team trying to get Mojo open source. They came through a couple weeks ago and now <a href="http://blastmojo.com">Mojo is official out in the wild</a>.</p>

<p>Being an advocate of open source, I used the opportunity to quickly <a href="http://github.com/slajax/Mojo-Tasks">build a scaffolding framework for Mojo called Mojo Tasks</a>. I had talked about doing it for a while, and tested a few difference implementations before I finally settled on the current implementation which you can find on my <a href="http://github.com/slajax/Mojo-Tasks">Git Hub account</a>.</p>

<p>All that said, I would like to welcome <a href="http://blastmojo.com">Mojo </a>into the open source world and I am very excited to make more contributions to this amazing UI framework.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.slajax.com/2009/12/16/blast-radius-mojo-now-open-source-with-mojo-tasks-scaffolding/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Javascript Cross Domain Ajax</title>
		<link>http://blog.slajax.com/2008/07/23/javascript-cross-domain-ajax/</link>
        <customfield>dojo.png</customfield>
		<comments>http://blog.slajax.com/2008/07/23/javascript-cross-domain-ajax/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 17:16:23 +0000</pubDate>
		<dc:creator>Kyle</dc:creator>
				<category><![CDATA[api]]></category>
		<category><![CDATA[blast radius]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[crossdomain]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[mashup]]></category>
		<category><![CDATA[x-domain]]></category>

		<guid isPermaLink="false">http://blog.slajax.com/?p=32</guid>
		<description><![CDATA[Since I joined Blast Radius [1] I have been introduced to a lot of new and interesting development practices, frameworks and designs that I have always read or heard about, but was never really forced or motivated to imply in my daily progression.
One such framework I wrote briefly about is Mojo [2]. Being a framework that has evolved from the Dojo Toolkit [3] my interest peaked this morning when I read a very interesting article on Ajaxian [4] about cross domain transport.


Originally as more of a low level technologist who only picked up ajax and interface development as a smooth view state for communicating with my middle tier controllers I found Javascript to be very much lacking the web services department. Very often the techniques that have been traditionally used consist of one of two strategies for x-domain communication;

1- A remote javascript include is served using:



[1] http://blog.slajax.com/2008/06/17/relocating-to-vancouver-senior-interface-developer/
[2] http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/
[3] http://dojotoolkit.com
[4] http://ajaxian.com/archives/windowname-meet-dojoxiowindowname]]></description>
			<content:encoded><![CDATA[Since I <a href="http://blog.slajax.com/2008/06/17/relocating-to-vancouver-senior-interface-developer/" target="_blank">joined Blast Radius</a> I have been introduced to a lot of new and interesting development practices, frameworks and designs that I have always read or heard about, but was never really forced or motivated to imply in my daily progression.
One such framework I wrote briefly about is <a href="http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/"  target="_blank">Mojo</a>. Being a framework that has evolved from the <a href="http://dojotoolkit.com"  target="_blank">Dojo Toolkit</a> my interest peaked this morning when I read a very interesting article on <a href="http://ajaxian.com/archives/windowname-meet-dojoxiowindowname" target="_blank">Ajaxian</a> about cross domain transport.
<br/><br/>

Originally as more of a low level technologist who only picked up ajax and interface development as a smooth view state for communicating with my middle tier controllers I found Javascript to be very much lacking the web services department. Very often the techniques that have been traditionally used consist of one of two strategies for x-domain communication;
<br/><br/>
1- <strong>A remote javascript include is served using:</strong><br/>
<div class='codeWrapper'><div class='codeTitle'>javascript<span class='codeInstruct'>hover edges to scroll</span></div><code><pre>&nbsp;
&lt;script type=<span style="color: #3366CC;">'text/javascript href='</span>http:<span style="color: #009900; font-style: italic;">//remotehost/js/api.js?param=1&amp;param2'&gt;</span></pre></code></div>
This is usually a server side script that generates the file contents based on the parameters, and then either renders content locally into your DOM, or provides you with a set of methods that will allow you to manipulate the content. This is not a very secure model and does not allow you to interact with raw xml data very robustly, but as long as you trust the source that is rending the content, it is quite efficient.
<br/><br/>
2- <strong>By matter of Proxy.</strong><br/>
This method I&#8217;ve used very often for direct communication with XML, SOAP, or REST gateways. Generally, I will develop the interface layer to communicate with a server side controller which will then use Curl to invoke the remote data, process and return as an JSON object. I find this method to be very robust, and allows you to create a very extensible gateway for your Javascript cross domain requests.
<br/><br/>

With that said, the post I read this morning is indicating that a new methodology for cross-domain scripting is emerging in the Dojo framework. By way of the property <i>window.name</i> one can make a remote request and retrieve data without exploiting the ever so wonderful cross domain security model that we are subject to in all our favorite browsers. This concept is very new but interesting. It opens up a whole new world of client side mash-up possibilities that are sure to get the creative juices flowing in the client side development space. Here is an example of it would be implemented:

<div class='codeWrapper'><div class='codeTitle'>javascript<span class='codeInstruct'>hover edges to scroll</span></div><code><pre>&nbsp;
dojox.<span style="color: #006600;">io</span>.<span style="color: #006600;">windowName</span>.<span style="color: #006600;">send</span><span style="color: #66cc66;">&#40;</span>method, args<span style="color: #66cc66;">&#41;</span>; <span style="color: #009900; font-style: italic;">// simple method</span>
<span style="color: #009900; font-style: italic;">// deferred result</span>
&nbsp;
<span style="color: #003366; font-weight: bold;">var</span> deferred = dojox.<span style="color: #006600;">io</span>.<span style="color: #006600;">windowName</span>.<span style="color: #006600;">send</span><span style="color: #66cc66;">&#40;</span><span style="color: #3366CC;">"GET"</span>, <span style="color: #66cc66;">&#123;</span>url:<span style="color: #3366CC;">"http://somesite.com/resource"</span><span style="color: #66cc66;">&#125;</span><span style="color: #66cc66;">&#41;</span>;
deferred.<span style="color: #006600;">addCallback</span><span style="color: #66cc66;">&#40;</span><span style="color: #003366; font-weight: bold;">function</span><span style="color: #66cc66;">&#40;</span>result<span style="color: #66cc66;">&#41;</span><span style="color: #66cc66;">&#123;</span>
  <span style="color: #000066;">alert</span><span style="color: #66cc66;">&#40;</span><span style="color: #3366CC;">"The request returned "</span> + result<span style="color: #66cc66;">&#41;</span>;
<span style="color: #66cc66;">&#125;</span><span style="color: #66cc66;">&#41;</span>;</pre></code></div>


]]></content:encoded>
			<wfw:commentRss>http://blog.slajax.com/2008/07/23/javascript-cross-domain-ajax/feed/</wfw:commentRss>
		</item>
		<item>
		<title>First week at Blast Radius over</title>
		<link>http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/</link>
        <customfield>../uploads/2008/07/blast_front_door.jpg</customfield>
		<comments>http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/#comments</comments>
		<pubDate>Fri, 18 Jul 2008 00:52:49 +0000</pubDate>
		<dc:creator>Kyle</dc:creator>
				<category><![CDATA[blast radius]]></category>
		<category><![CDATA[blast]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[job]]></category>
		<category><![CDATA[radius]]></category>

		<guid isPermaLink="false">http://blog.slajax.com/?p=31</guid>
		<description><![CDATA[

So as of monday my first full week at Blast Radius [1] is completed. As you can see from the terribly pixelated photo above, I found it with no issues. It just so happens that my apartment is much closer then I originally thought. I literally have been leaving for work 2 minutes before I start, which still leaves enough time for an ever so terrible tasting 7/11 coffee.

Last week was full of a lot of orientation, but I did my best to take it in stride and quickly dive into learning the way things work here. I've started learning Mojo, which is an amazing interface development framework that uses the power of Dojo [2] to create a very robust and abstract environment for developers. The code is structured very strongly in a Java style pattern and I'm finding that I'm adapting to it very well. I'll have a post or two more very shortly about my experience learning it and it's details which might provide someone coming after me a starting place.

That all said, I'm happy to be settled and in my new work environment with some amazingly talented developers. It's been so long since I've worked with people who were as keen on interface development as I am. It was a long drive and a big decision to move out here, but I'm very glad I did it and cannot wait to continue to learn everything there is to learn about the experienced beast that is Blast. Tomorrow I'll start "OpX" training which will help me understand and adapt to the very agile and fast past development cycles that have made this company so successful.

[1] http://blastradius.com
[2] http://dojotoolkit.com]]></description>
			<content:encoded><![CDATA[<img class="aligncenter size-full wp-image-26" title="blast_front_door" src="http://blog.slajax.com/wp-content/uploads/2008/07/blast_front_door.jpg" alt="Blast Radius Sign" width="500" height="100" />
<br/><br/>
So as of monday my first full week at <a title="Blast Radius Website" href="http://blastradius.com" target="_blank">Blast Radius</a> is completed. As you can see from the terribly pixelated photo above, I found it with no issues. It just so happens that my apartment is much closer then I originally thought. I literally have been leaving for work 2 minutes before I start, which still leaves enough time for an ever so terrible tasting 7/11 coffee.
<br/><br/>
Last week was full of a lot of orientation, but I did my best to take it in stride and quickly dive into learning the way things work here. I&#8217;ve started learning Mojo, which is an amazing interface development framework that uses the power of <a title="Dojo Toolkit" href="http://dojotoolkit.com" target="_blank">Dojo</a> to create a very robust and abstract environment for developers. The code is structured very strongly in a Java style pattern and I&#8217;m finding that I&#8217;m adapting to it very well. I&#8217;ll have a post or two more very shortly about my experience learning it and it&#8217;s details which might provide someone coming after me a starting place.
<br/><br/>
That all said, I&#8217;m happy to be settled and in my new work environment with some amazingly talented developers. It&#8217;s been so long since I&#8217;ve worked with people who were as keen on interface development as I am. It was a long drive and a big decision to move out here, but I&#8217;m very glad I did it and cannot wait to continue to learn everything there is to learn about the experienced beast that is Blast. Tomorrow I&#8217;ll start &#8220;OpX&#8221; training which will help me understand and adapt to the very agile and fast past development cycles that have made this company so successful.]]></content:encoded>
			<wfw:commentRss>http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
