http://blog.webappkit.net/ news about webAppKit, the generic PHP kernel for web apps en Wed, 10 Sep 2008 12:39:03 +0200 http://blogs.law.harvard.edu/tech/rss Dotclear http://blog.webappkit.net/post/2006/10/27/where-is-going-webappkit urn:md5:050a5b706d09adbb82e7b30146cc2d66 Thu, 02 Nov 2006 14:23:00 +0100 J.Ducastel in-depth deprecatedroadmap <p>I realized that while i have some pretty clear idea about webappkit future, i had somewhat kept this in the secret of my head. Here are some informations about webappkit goals, intended usage/audience and roadmap.</p> <h3>A flexible architecture to build web applications on</h3> <p>WebAppKit is not another MVC framework, such as Ruby On Rails, Django and many PHP clones such as CakePHP. In fact, it's not a framework at all. It doesn't allow rapid blog/cms building by mapping an SQL database with controller classes linked to URIs. It doesn't offer (yet) cool ajax features.</p> <p>Rather, it's intended to be a lower-level structure which provides tools for the developper, with as few constraints as possible. You can use provided services as you wish, build your app on webappkit standards, or you may prefer follow your own style and rules, picking only what serves you best. You may even build your own framework on the top of webappkit, by writing your own request handler. The µkernel/service based structure of webappkit make any of its parts substitutable.</p> <p>This goal is near completion. Although there is still room for improvements, It starts to be usable for producing complete web applications, such as <a href="http://quizzgeek.net" hreflang="fr">quizzGeek</a>.</p> <h3>A platform for modular parts integration</h3> <p>As webappkit applications are highly modular, the next logical step is to allow share and reuse of modules and generic applications parts, from tiny functionnality to complete specification implementation, or even full standalone application. To achieve this, webappkit admin system will ultimately allow to import and export <q>kits</q>.</p> <p>Kits will be packages which may contain libraries, services, events, and/or triggers. They will range from basic toolkits to complete applications with their own admin, that you will be able to &quot;mount&quot; on an URI of your core application. For example, you may just install a &quot;blog&quot; kit and mount it on yourdomain.net/blog, or an &quot;accesscontrol&quot; kit mounted on yourdomain.net/private, and it will protect everything under this path.</p> <p>Webappkit web site will of course collect and distributes those kits, for the use of the community.</p>