padrino
We really like Sinatra and use it for all our new projects.
However, we’ve decided that Padrino doesn’t have enough support from the core Sinatra team.
We do hope to create more screencasts about how we use Sinatra, but we don’t have plans to cover Padrino.
56 comments
-
CJ Lazell
commented
Very sad to see something with the most votes declined! I would have loved this screencast!
-
Chris E
commented
Really? 548 votes doesn't mean anything...
-
bashcoder commented
Interesting - I would not consider Sinatra's level of support for Padrino as any sort of factor, as Sinatra is not based on Padrino. Not sure why that would even be an issue. The reverse consideration would be quite valid, however.
-
Marius
commented
+1
-
Mick Pollard
commented
this would be pretty useful. +1
-
Rixius
commented
Yes more Padrino display is a good thing.
-
Abhas Abhinav
commented
Yes - An advanced Padrino screencast would be wonderful!
-
Humberto Morales
commented
This would be the bee's knees!
-
Masterof0
commented
A comprehensive webcast on Padrino is desperately needed.
-
Dominic Son
commented
Jeff, Rails has always needed a real admin system. It'd be nice to show Padrino with Sinatra, and using it into a Rails App with Rack.
'I'd buy THAT for a dolllar!' - Robocop Commercial.
-
Efrén Fuentes
commented
Cool! Please hurry up!
-
TheSent
commented
Padrino. PRETTY PLEASE!
-
Pan Inkognito commented
Any progress?
-
moosc
commented
Any news?
If it's planned i have some suggestions:
- May be 2 screencasts (beginner and advanced)
- Registration: twitter, facebook, and normal registration
- Roles
- Upload multiple files (with uploadify or swfupload or ...)
- Nested forms (planned for 1.0)
- Sending mails
.... -
activestylus
commented
I already use and love Padrino. All that's missing is bigger community - a screencast would have a huge positive impact there
-
Altareq
commented
Padrino is great. once you try it, you would prefer it over many other ruby web frameworks.
Yes, for a Screencast! -
Raymond
commented
Cool! Just in time for Padrino version 1.0. ;D
-
Brian
commented
My Ruby journey is somewhat atypical in that I started out with Sinatra, and then progressed to Padrino. I still haven't used Rails on any real projects.
By the time I had weaned myself off PHP and was ready to start real Ruby development (having been watching the community for several years with a keen interest), I already knew about things like DataMapper, Haml, Sass, Compass, Cucumber, Rack and Bundler, and I had a few relatively small projects I wanted to get my teeth into quickly.
Rails didn't really seem like the right fit (the less opinionated version 3 was still in beta), so I when I came across Sinatra, I decided to use it for my first production Ruby project.
Being a big PeepCode fan, I bought the Sinatra and jQTouch screencasts to help me get to grips with two new technologies. For me they were the best resource available bar none to explain in detail and clarity the fundamentals of the two frameworks. I was also pleasantly surprised when I realised how well these two technologies worked together upon noticing how the jQT screencast used Sinatra behind the scenes.
After a few months I discovered Padrino and I've already built two production sites with it. It really hits the sweet spot between convention and flexibility, and is based on a very strong underlying architecture.
For inspiration I often refer to the blog example on the website, and the source code of the Padrino website on GitHub, to see how things are done.
An example project with the PeepCode treatment would be awesome. And a great way to coax other developers into the 'family'. ;-)
-
Elmer Rivera
commented
We are waiting for the screencast!
-
Temba Mazingi
commented
Just one more place before we get to #1