Download Surge
Isaac Dealey
100 downloads in the last 24 hours.
--
[ ike ] founder - onTap framework
phone: 781.769.0723
Gerald Guido
Very cool.
I think the one thing on the article that really grabbed my attention was the emphasis on ontap being simple. Many ppl getting into frameworks for the first time tend to be overwhelmed with the sheer volume of new concepts. That and having to undertake a whole new approach of coding/thinking at the same time (i.e. going from procedural to OO).
~G~
"If everything seems under control, you're not going fast enough"
-- Mario Andretti
Isaac Dealey
> was the emphasis on ontap being simple. Many ppl getting into
> frameworks for the first time tend to be overwhelmed with the sheer
> volume of new concepts. That and having to undertake a whole new
> approach of coding/thinking at the same time (i.e. going from
> procedural to OO).
Ahh cool... Well... what do you think so far? Is it easy to learn? :)
One of the things I wanted to do with this framework early on was to
design it in such a way that existing sites could be ported into it
gradually. I think that was the original intent behind the rear
controller, the notion that you could build your site "flat" or you
could build it in the framework, and the URLs would be the same either
way. And since the URLs wouldn't change, any given page could be in or
out of the framework, so you could move them into the framework a few
pages per day without having to do any of the usual sort of code
freezing or branching that's involved with those kinds of ports (which
are often not undertaken due to the effort involved in things like
site-wide URL changes).
Front-controller sites can be ported into the framework without changing
URLs either, although it would be a little more work to do that
gradually.
I put up an article the other day titled "the rear controller and you"
on the wiki that talks about the differences between the front
controller design pattern and the rear controller design pattern.