Create web application using ruby not with frameworks

I started writing a little microframework built on top of Sinatra for
similar reasons. I got kind of fed up thinking that ruby's harder to get
__simple__ database-backed web apps up than something like PHP with
mysql.

So I basically built on top of ActiveSupport, ActiveModel, Sinatra and
DBI. So it really is close to the metal, and much harder to get caught
in the sea of abstraction that Rails sometimes presents me with.

The code's on Github, and although I haven't added docs yet I plan on
doing that this week. If you're curious, there's a simple 'ORM" called
LazyRecord that basically does things like #save, #destroy, #update,
etc...

code is here: https://github.com/luke-gru/studio54

LazyRecord: is in lib/lazy_record.rb
LazyController is in lib/lazy_controller.rb

main file is 'dance.rb', where routes are mapped, controllers are called
and responses are sent.

It's called Studio54 because it's like Sinatra meets Rails...

oh boy..

-Luke

···

--
Posted via http://www.ruby-forum.com/.

Have you ever tried Camping? I haven't had time to dig thru your code,
but I've got a feeling you're reinventing it.

-- Matma Rex

···

2012/1/4 luke gruber <luke.gru@gmail.com>:

I started writing a little microframework built on top of Sinatra for
similar reasons. I got kind of fed up thinking that ruby's harder to get
__simple__ database-backed web apps up than something like PHP with
mysql.

So I basically built on top of ActiveSupport, ActiveModel, Sinatra and
DBI. So it really is close to the metal, and much harder to get caught
in the sea of abstraction that Rails sometimes presents me with.

The code's on Github, and although I haven't added docs yet I plan on
doing that this week. If you're curious, there's a simple 'ORM" called
LazyRecord that basically does things like #save, #destroy, #update,
etc...

code is here: https://github.com/luke-gru/studio54

LazyRecord: is in lib/lazy_record.rb
LazyController is in lib/lazy_controller.rb

main file is 'dance.rb', where routes are mapped, controllers are called
and responses are sent.

Have you ever tried Camping? I haven't had time to dig thru your code,
but I've got a feeling you're reinventing it.

-- Matma Rex

Yeah, the Camping code is really fun to read. Basically, Studio54 tries
to
do even less in certain areas. So, there are no migrations. Set up the
database yourself using phpmyadmin or whatever. This is how most
newcomers coming from PHP work anyway, I find. Even so, it uses DBI to
be database agnostic for queries, so if there's a DBI driver for that
database then it should work.

Also, since all the rendering is done in a seperate file from the main
controllers, many controllers can be called from one route, which keeps
things DRY. Also, anything available in Sinatra is available in
Studio54, so all the Tilt stuff is available for views.

But yeah, it's not very ambitious or complete, just a personal project
that I made after getting frustrated with Rails having too much
abstraction.

-Luke

···

--
Posted via http://www.ruby-forum.com/.