automach

6 ms·

1.
by automach 15y ago
Using the Dock connector involved paying Apple a licensing fee. This circumvents that, and it's similar (although more involved) to how Square's card readers work. There is already an iOS serial cable though, which I would think would be a
2.
by automach 15y ago
I'm all for new ideas and tools, but you have to bring something to the table other than just being different. And just being "smaller" is not enough. This is the problem with Padrino- it isn't different enough. We don't need a smaller MVC
3.
by automach 15y ago
As someone that has been writing production Rails and Sinatra apps for years, I have to recommend against using Padrino. Rails scales up and down pretty well, and I don't really see a need for Sinatra in anything but very small or single-pu
4.
by automach 15y ago
The docs have gotten a lot better. In particular, the guides site has a lot of really useful content: http://guides.sproutcore.com You will probably still have to look at the API docs (and read some source) from time to time, but the core
5.
by automach 15y ago
We're using SproutCore 1.6 and TemplateViews for a medium size app, and in many ways, it feels like the early days of any framework- there are a lot of nice features, but you have to be willing to dig into framework code and bend it to your
6.
Using Handlebars partials in SproutCore TemplateViews(techmology.posterous.com)
4 points by automach 15y ago|0 comments
7.
by automach 15y ago
The focus of SproutCore 2.0 is building views using Handlebars and the ability to use these views and the data layer in ways that play nicely other frameworks and web technologies. The only real demo so far is the todos app: https://githu
8.
by automach 15y ago
The pie charts don't really make any sense. For example, a single project can use Cucumber, Capybara, and RSpec, or none of them, or any combination. But in the article and its graphs they are presented as mutually exclusive options. Separa