Jonathan Rowny

So this has been out there for awhile, but it just started getting some marketing attention: Brackets, an opensource IDE.

I like the idea of an opensource editor built in HTML/CSS/Javascript so I gave it a shot. Obviously, it's too new to be really replace your every day tools, but it does have some promising features. Not only that, but it's SUPER easy to work on. So here's a few extnesions I wrote.

Snippets

Type a familiar trigger, hit a keystroke, and bam, you've got a snippet. You can create new snippet templates with JSON (XML soon) and if you don't like keystrokes, you can use the tool bar by going to "View -> Snippets."


Download and place in extensions/user

GitHub

The GitHub extension aims to do integration of the GitHub api direclty into Brackets. For the time being, it mostly only does gists. You can post your current document or current selection to a gist.

Download and place in extensions/user

You can check out the session code here: on GitHub.

The presentation will be in the community area today at 11am. Come check it out! The slides are attached in case you want to follow along.

Here's a link to my presentation, http://goo.gl/WTlj9. Source code will be posted here shortly. Or you can search to see some outdated code from DrupalCon SF and DesignCamp Boston.

I'm loving the new Flash Builder and 4.5 SDK. I don't know if everyone came to the same realization that I did... but "states" are awesome now with the 4+ SDK! You can change ANY property on the fly. Take for example a two stage button:

<s:Button icon.viewing="{Icons.PENCIL}" 
	      icon.editing="{Icons.DRIVE}"
	      label.viewing="Edit"
	      label.editing="Save"
	      click.viewing="{currentState='editing'}" 
	      click.editing="{currentState='viewing'}"
	      />

One button, two actions, two states. Note: the Icons class is just a static class with some icons embedded in it. Makes for quickly iconing stuff. Now I'm not saying you CAN or SHOULD do your buttons this way... you might simply make two buttons:

<s:Button icon="{Icons.DRIVE}"
	      label="Save" 
	      click="{currentState='viewing'}"
          includeIn="editing"
	    />
<s:Button icon="{Icons.PENCIL}" 
	      label="Edit"
	      click="{currentState='editing'}" 
          includeIn="viewing"
	    />

In theory, the former should take less memory but I haven't actually gone to look at what the states management is doing behind the scenes.

Of course, all the previous code assumes you've got the states defined:

<s:states>
   <s:State name="viewing"/>
   <s:State name="editing"/>
</s:states>