Get It Now

We have reached a milestone where K2F can be seen out there and working.
Although there is a lot more to work on, at this point, it defines exactly what K2F is about.

K2F is being rewritten from scratch (version 2.4). This will have a widespread impact:

• It will make use of namespaces (you will have to add K2F\ before K2F functions/classes)
• It will target PHP 5.3+
• Development on the 2.3 branch will continue, but in smaller quantities
• Thanks to namespacing, K2F is less likely to screw or conflict with the host
• Also, namespacing is a better alternative to registries, since it won’t break PHPDoc support

Finally, we’d also like to announce the development (and near completion) of a Drupal Adapter for K2F. This means in the near future, you’ll be able to deploy your applications on Drupal!

There are many concepts behind K2F, each of which started at different points in time.

The main concept started some time in 2009. I was working on a rather big project when I figured I should be reusing my custom code.

When you look at it, it’s not much of a big concept, developers have been doing this since day 1. The thing is, it didn’t all stop there, it grew up.

The core code had changed many times to work for different scenarios that eventually, a pattern started to show up.

At first, it was all about having a thin layer between application logic and the host platform (eg; a CMS).

After a while, it came to me, why not completely eliminate the need for an application to depend on its host?

That’s when K2F was born.