<?xml version="1.0"?>
<rss version="2.0">
	<channel>
		<title>thoughts from the Axiom Team</title>
		<link>http://www.axiomblog.com/</link>
		<description>What do we have to say?</description>
	<item>
		<title>New Axiom Stack site launched!</title>
		<link>http://www.axiomblog.com/11-10-2008/new-axiom-stack-site-launched</link>
		<description><p>We've been working hard on the new <a href="http://www.axiomstack.com" target="_blank">Axiom Stack website</a> (well ok, Nick has been working the hardest) and boy are we excited about it.</p>
<p>We changed the look, made it a bit more functional that design oriented. We added search and now the full <a href="http://www.axiomstack.com/learn" target="_blank">Axiom Stack documentation</a> is searchable and downloadable! Woo hoo.</p>
<p>We've added a <a href="http://www.axiomstack.com/community/" target="_blank">community section</a> with all the areas where you can find Axiom Stack including this blog, <a href="http://www.twitter.com/axiomsoftware" target="_blank">twitter</a>, google groups for <a href="http://groups.google.com/group/axiom-stack-announce" target="_blank">announcements</a> and <a href="http://groups.google.com/group/axiom-stack" target="_blank">forums</a> and our <a href="http://axiomstack.com/community/issue-tracking" target="_blank">Issue Tracking site</a>.</p>
<p>The most important area we've added is <a href="http://axiomstack.com/about/support" target="_blank">support</a>. Now you can sign up and get support for your Axiom Stack build. We have email and phone support available depending on the plan you take. This will make it much easier for you to get you questions answered by us and keep moving along with your project.</p>
<p>Our <a href="http://axiomstack.com/learn/" target="_blank">documentation</a> is constantly being updated. We added in more tutorials and how to's. We've opened a <a href="http://axiomstack.com/company/partners" target="_blank">Partner's area</a> (ask us how to become one) and we introduce you to the <a href="http://axiomstack.com/company/the-team" target="_blank">Axiom Team</a>.</p>
<p>Go and take a look. Let us know what you're working on, get involved in the community and ask us how you can get support.</p>
<p>Give Axiom Stack a try, you won't be disappointed.</p></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>Axiom Software and Joyent - The Stack Is-a-Rollin'.</title>
		<link>http://www.axiomblog.com/10-09-2008/axiom-software-and-joyent---the-stack-is-a-rollin</link>
		<description><p>We like choices. We assume you do too. In helping you see the advantages of the Axiom Stack, we've teamed up with <a href="http://wiki.joyent.com/all-accelerators:kb:axiom">Joyent</a> to give you the tools to power your applications with our framework and their state-of-the-art servers.</p>
<p>Having used the services at Joyent, we can say that we were both pleased and impressed. Their Accelerators are simple to setup, easy to use and cost effective. This means you can now go to Joyent, and <a href="http://wiki.joyent.com/all-accelerators:kb:axiom">in a few steps, have a server configured and ready to go with Axiom Stack</a>.</p>
<p>We are pleased to be teaming up with Joyent. <a href="http://www.joyeur.com/2008/10/10/joyent-labs-axiom-stack-on-joyent-accelerators">Kent Langley wrote about Axiom Stack deployment on Joyent Accelerators</a> on the Joyent Blog.</p>
<blockquote>"I think of Axiom Stack as a Javascript Platform as a Service (PaaS) on top of Joyent’s Infrastructure as a Service (IaaS). As such, I think it could be of interest to a number of people."<br/>
</blockquote>
<p>Joyent's Accelerator gives you the ease and flexibility of cloud computing. Dynamically expand your instance in minutes. The power and scalability of the Joyent Accelerator combined with the ease of the Axiom Stack make a lineup that can help build and host dynamic applications better and faster.</p>
<p>Go to <a href="http://wiki.joyent.com/all-accelerators:kb:axiom">Joyent</a> and check it out today.</p></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>Documentin' Ain't Easy</title>
		<link>http://www.axiomblog.com/09-11-2008/documentin-aint-easy</link>
		<description><p>Creating a documentation system for Axiom Stack has been a unique challenge and I wanted to elaborate a bit on what we've come up with to do the job. <br/><br/>Most widely used languages have good code-level documentation tools already: RDoc for Ruby, Javadoc for Java, etc.  You comment your code according to the coventions of the tool and the tool in turn takes them and spits out some nicely formatted, human-readable documentation. <br/><br/>Our challenge: not everything in the Axiom Javascript environment is implemented in Javascript!  Axiom Stack itself is written in Java, while applications are written in Javascript.  The JS API available to your application code comes from two sources:</p><p>- Pure Java objects, wrapped up and exposed to the scripting layer via Rhino.  This is stuff like the<a href="http://www.axiomstack.com/static/docs/AxiomObject.html">AxiomObject</a>prototype and the<a href="http://www.axiomstack.com/static/docs/app.html">app</a>object.</p><p>- Modules and libraries written in Javascript.  We include a number of utility libraries (like the<a href="http://www.axiomstack.com/static/docs/FtpObject.html">ftp</a>library) and enhancements to existing JS prototypes like Array and String in this fashion.</p><p>So, we couldn't simply run the language-appropriate tool over all our code and be done with it.  Here's how we did it:<br/><br/>First, we created a class that used Sun's<a href="http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/doclet/spec/index.html">Doclet API</a>to run over all our Java classes.  Any classes marked as exposed to the scripting layer are transformed into stub Javascript. This code doesn't do anything, but serves as an empty frame for<a href="http://jsdoc.sourceforge.net/">jsdoc</a>to parse, and is thrown away after the build has completed. Quick example:</p><pre class="java:nogutter:nocontrols" name="code">/** 
 * Grates cheese of your choice.
 * @jsconstructor
 */
public class CheeseGrater(){
 	/**
	 * @param {String} cheeseType Type of cheese.
	 */
   	public CheeseGrater(String cheeseType){
		    // ...
	}

	/**
	 * Grate up some cheese!
	 */
	public GratedCheese grate(){
		// ...
  	}			
}</pre><p>Becomes:</p><pre class="jscript:nogutter:nocontrols" name="code">/**
  * Grates cheese of your choice
  * @param {String} cheeseType Type of cheese.
  * @constructor
  */
function CheeseGrater(/**String*/ cheeseType){}

/**
  * Grate up some cheese!
  * @returns {GratedCheese}
  */	  
CheeseGrater.prototype.grate = function(){}</pre><p><br/>Then, we run jsdoc over both the Java-generated stub code and the real Javascript in our libraries and presto! Usable documentation.</p></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>Consider It Open</title>
		<link>http://www.axiomblog.com/09-04-2008/consider-it-open</link>
		<description><p>The<a href="http://www.axiomstack.com">Axiom Stack</a>source code has been opened. It was a fairly large undertaking to get the source out to all of you in a way that made sense and made it easy. Also, we didn't want to release the source without<a href="http://www.axiomstack.com/learn">documentation</a>.</p><p>So, we cobbled together a documentation tool based on<a href="http://www.jsdoctoolkit.org/">JSDoc</a>. This grabs methods within the Javascript context including the Java specific methods. This is extremely handy as we no longer have to use two tools for documentation. This means that you'll get more and better documentation as the projects progress.</p><p>Also, we had to get some licensing in place. This is important because we want you to be able to view and modify the source. Ultimately we'd like to include what you're working on in our codebase too. More heads are better than one.</p><p>In the same spirit that we provided the source to you, we'd like you to do for others. This is the reason we put the stack under the<a href="http://axiomstack.com/license-agreement">AGPL license</a>. If you'd prefer to not reveal your<i>secret sauce</i>, we understand. Feel free to<a href="mailto:info@axiomsoftwareinc.com">contact us</a>to discuss other arrangements.</p><p>One other thing we did was to create a<a href="http://www.axiomstack.com/forums">forum system</a>on top of the stack. We like the phrase "eat your own dogfood". We're in the process of revamping parts of it as I type this, but it is available for use right now. Feel free to take it for a test drive, we're watching them so you can ask all the questions you'd like...unless you're a bot...then stay out.</p><p>Overall, this was a big deal for us. We wanted to give back to the community that gave and continues to give to us. Thanks, enjoy, and let us know what you think. We'd love to hear from you.</p></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>Axiom Searchable Radio and NPR</title>
		<link>http://www.axiomblog.com/07-16-2008/axiom-searchable-radio-and-npr</link>
		<description><p><a href="http://www.npr.org">National Public Radio</a>(NPR) has released their API and has included Axiom Software's Searchable Radio widget on their<a href="http://www.npr.org/api/widgets.php">API widget page</a>. NPR has been working on their much anticipated API release for some time. The API gives developers access to all of NPR radio's news, features and music.</p><p>Axiom Searchable Radio gives the user the ability to search, browse and listen to those stories through their iPhone®. Access<a href="http://www.searchableradio.com">searchableradio.com</a>from your iPhone browser and dig in to thousands of pieces of content.</p><p>Axiom Searchable Radio was developed with and runs on the Axiom Stack (soon to be) open source web application server. Check the<a href="http://www.axiomstack.com">Axiom Stack</a>for the upcoming open source release, tutorials and documentation.</p></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>Almost Ready ..</title>
		<link>http://www.axiomblog.com/07-14-2008/almost-ready-</link>
		<description><p>We are very close to having the Axiom Stack source code ready for the public.  The primary task left is code commenting.  Its that thing that most developers like to avoid unless they have a gun pointed at their head (and even then, they might reflect for a few minutes before deciding on bullet vs code commenting).  In addition to making the code base easier to follow for people who want to jump in and start hacking, a primary goal for us is to use JSDoc to take the Java code comments and create Javascript level API docs out of them.  There are a lot of classes to comment in order to get the Axiom JavaScript APIs fully documented.  This should all be finished pretty soon, and hopefully the source code and documentation will make it easy for developers interested in the stack to jump right in.</p><br/></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>One Stack to Rule Them All</title>
		<link>http://www.axiomblog.com/06-30-2008/one-stack-to-rule-them-all</link>
		<description><p>Are we offensively biased? Sure we are. Do we think our products are the best? Of course we do. Are we prepared to listen to the community? Can we take criticism? Will this help us? Yes, yes and you bet.</p><p>We know our product is mature; we are also mature enough to know it can be improved. That’s where you come in. Opening the source of the<a href="http://www.axiomstack.com">Axiom Stack</a>is a big deal. We are opening our hard work, our development expertise and our lives to you. We have been living this Stack and living the process for some time. We are confident of not falling flat due to quality challenges; we know we made something good. The Axiom Stack been implemented and running on some large, high traffic<a href="http://axiomsoftwareinc.com/success_stories">websites</a>. We’ve had some great feedback from the release of the free-for-personal-use version, which launched in March at<a href="http://2008.sxsw.com/interactive/">SWSX</a>. But, having others look into the full source is something that hasn’t been done. What’s needed is the differing points of view and having others look at it through eyes with experiences that can take it in an uphill climb to where? Well, who knows? All we do know is that we have a plan to keep it moving the right direction and with your help, it’ll go further faster and eventually rule them all.</p></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>Open it up</title>
		<link>http://www.axiomblog.com/06-28-2008/open-it-up</link>
		<description><p>Well, the decision has been made and we’re excited, the work has begun and it’s only a matter of time. Axiom Stack has decided to open up its source to the outside. We are re-licensing the software under GPL. This will help us confirm what we already know, Axiom Stack is a smart choice for developers who want to build applications and deploy websites quickly and easily.</p><p>We’ve been using it and it’s deployed commercially, that’s good. This step is bound to be filled with excitement, and worry. It’ll open us up as a company so others can view the inner workings. I’m sure they’ll be disagreements amongst the newly building community…but that’s good. How else to improve what we know is already good.</p><br/><p>It’s a big step and a good one. So go take a look. Dig around. Let us know what you think. We need a few weeks to tie up the loose licensing ends, but it’s only a matter of time before we open it up.</p></description>
		<pubDate>undefined</pubDate>
	</item><item>
		<title>Networking: go on, try it you’ll like it</title>
		<link>http://www.axiomblog.com/05-29-2008/networking-go-on-try-it-youll-like-it</link>
		<description><p>The term Networking has a tendency to make most developers cringe and walk the other way. I say most, there must be some that don’t mind speaking to strangers about what they do, what they’re working on, what they’re interested in doing, where they see their industry going and developing relationships with others with or without similar interests. It doesn’t sound that hard.</p><p>The scary part is that networking is actually marketing…”ah, what, marketing, not me, no no no! I develop applications, I write the best code, I use great scripting languages and I read and comment on technical Web sites”. See any similarities here?</p><p>Just getting out and talking passionately about what you do is the best marketing there is. People are interested if you are excited about your subject. People want to know what’s new about it, why it’s special and why it’ll succeed. You might also learn a thing or two.</p><p>Learn from others by listening. Now, I know what you’re thinking. You know what you’re doing better than anyone else and there isn’t anything you could possibly learn from them. But, listening to what others say about their past experiences with any software is one of the best ways to gauge your own work or product.</p><p>Networking is easier than you think and very productive for your company and brand. Seeing smart people talk passionately about their work will excite others about your work, which will turn into leads, which could possibly turn into sales. If you are passionate about your work and can talk about it, you can successfully network.</p><p>Try it, you might like it.</p></description>
		<pubDate>undefined</pubDate>
	</item></channel>
</rss>