This is mostly a question, but perhaps it could also be made more clear on the homepage.
Let me explain the background first.
I started in ~2005 or so with ruby, sort of; and my old .php code became mostly .cgi.
I wrote a custom "web-framework" which I still use, but I also use sinatra. So I already
use both .cgi and sinatra just fine. But sinatra is a bit lacking in several areas, so I am
wondering if I could move onto padrino.
But! I do not use MVC and I do not want to. The stuff I use is so super-simple that
I don't want or need the complexity of MVC. About 98% of this all is just static files,
so most of the time I only use the REST-apis to either select "sub-parts", or sometimes
to pass arguments as-is to a ruby class that handles these things.
So my question is: can padrino be used as an "extension" of sinatra but without any
MVC? Sort of where I can just continue to use "sinatra", sort of, but to add more
niceties - only cherry-picking them though. I loved that part that sinatra was modular.
It's why I don't use rails - I just can not stand the assumptions or directory layout
they want to push down. I already have the directory layout figure out so I only need
something that helps me in the existing structure as-is, rather than a change.
I think the last time I used padrino it was catering mostly to rails-users, so the first
tutorial I did was a MVC one if I recall correctly. Hence my question sort of - hopefully
that is somewhat understandable what I wrote; english isn't my strongest point really. :)
Hey there,
This is mostly a question, but perhaps it could also be made more clear on the homepage.
Let me explain the background first.
I started in ~2005 or so with ruby, sort of; and my old .php code became mostly .cgi.
I wrote a custom "web-framework" which I still use, but I also use sinatra. So I already use both .cgi and sinatra just fine. But sinatra is a bit lacking in several areas, so I am wondering if I could move onto padrino.
But! I do not use MVC and I do not want to. The stuff I use is so super-simple that I don't want or need the complexity of MVC. About 98% of this all is just static files, so most of the time I only use the REST-apis to either select "sub-parts", or sometimes to pass arguments as-is to a ruby class that handles these things.
So my question is: can padrino be used as an "extension" of sinatra but without any MVC? Sort of where I can just continue to use "sinatra", sort of, but to add more niceties - only cherry-picking them though. I loved that part that sinatra was modular. It's why I don't use rails - I just can not stand the assumptions or directory layout they want to push down. I already have the directory layout figure out so I only need something that helps me in the existing structure as-is, rather than a change.
I think the last time I used padrino it was catering mostly to rails-users, so the first tutorial I did was a MVC one if I recall correctly. Hence my question sort of - hopefully that is somewhat understandable what I wrote; english isn't my strongest point really. :)