hellopat

I'm working on an app which uses Ember 1.0.0pre-2. Over the past few weeks I've been lazy / busy doing other things so the project was set aside for a bit. I came back to it yesterday, opened the guide page (http://emberjs.com/guides/) and noticed it had been updated. I was excited and immediately checked the Router section. The guide reflects a brand new router API, which from what I've read makes it much easier to control the state of your application.

The problem with Ember right now is the documentation doesn't align with the most recent public version, which will confuse the heck out of newcomers and frustrate people who are still learning Ember. You can however, check out master to get the new router implementation.

I'm personally making the jump to the bleeding edge for two reasons: 1. The old router API is very hard to grasp. A lot of unknowns as far as where domain code fits when building your application using the router. 2. I don't want to be stuck struggling to find documentation for an already difficult API to work with.

With all that said, Ember is worth taking a look at as far as an 'improved' MV* experience, but you have to be careful as it is in a state of flux.

I'm working on one right now and will definitely be integrating this into it. It's a perfect fit.

This is awesome.

One suggestion based on what I saw from the demo video: give the presenter the option to use either tap or gesture based transitions. It may be easier for the presenter to use gestures since they wouldn't have to look at the device to ensure they're tapping on the correct arrow. A simple double tap anywhere on the screen could bring them back to the index.

You could use it as a tool to learn Mongo query syntax assuming you have SQL down.

Sorry, I probably should have put in some instructions. When mousetip is turned on, you can hold down a modifier key (ctrl, cmd, windows key) and tooltips will dynamically appear based on the bounded shortcuts.

Confidence being the one I've noticed throughout following his career.

Another big issue is a broken javascript profiler. I've been using this quite a bit to optimize code on a project I've been working on and noticed after I updated that you can no longer expand nodes. Pretty bummed.

I'm having this issue as well.

I haven't used coffee script myself, but I think you'd be hard pressed to find someone that wrote something in CoffeeScript and regretted it. The biggest arguments against using CoffeeScript (or any language that compiles to JavaScript) that I seem to keep hearing are:

1. JavaScript isn't a very readable language. (I think this is untrue. I've seen some incredibly well written / structured JS) 2. Not everyone knows CoffeeScript, so when you put a project up on GitHub and it's written in CoffeeScript, it's difficult for people who only know the syntax of native JS to understand what's going on. (To counter this - a lot of projects that are written in CoffeeScript are bundled with the compiled JS code as well - which also happens to be very readable IMHO).

COMPANY (Philadelphia, PA) OneTwoSee http://www.onetwosee.com pclark@onetwosee.com

A funded social television startup focusing on companion applications.

BASIC DESCRIPTION (Front End Developer) Cut up and implement layouts from our graphic designer. This isn't just building static web pages from mock-ups. Our pages display real-time data via AJAX and involve complex behaviors and animations. Many of our designs involve implementing custom meters and graph widgets based on statistical data from our application server. You must be able to implement these using HTML5, CSS, and Javascript.

NECESSARY SKILLS Expert level knowledge in HTML, CSS, and Javascript. Expert at troubleshooting and building around cross-browser/cross-platform inconsistencies. Experience with, but not total reliance on, Javascript libraries and CSS frameworks (e.g. jQuery, Twitter Bootstrap, etc). Hand code your HTML, CSS, and Javascript. Make mobile-friendly versions of pages using CSS media queries. General knowledge of Photoshop. Good design and UX sense. Experience with version control software. Preferably git. Love discovering and applying new technologies and techniques.

BONUS Experience with compiled CSS systems like Less and Sass. Experience with NodeJS and the ExpressJS framework. Experience with backbone.js. Experience building vector graphic widgets with RaphaelJS or, even better, your own library.