Ok, maybe I'm double posting, but I thought this would definitely be the right topic to make a real announcement.
The PHP framework I started working on a couple of months ago is now available for an alpha release. It's still very raw and needs a lot of organization and additions. However, I think it has a lot of potential to become an incredibly useful tool for developers to create interactive websites that can output multiple protocols. I'm looking for some developers to help me out with coding, bugtesting, module development, etc. I've GPL'd the source, so its free for anyone to download and use.
demo
homepage
From the wiki:
How does it work?
Phritz works by parsing incoming requests to determine the format of the request. These requests are then wrapped in a simple Request object that is passed to a specified Controller which then passes that request to the requested method. Responses are returned in a simple Response object that is passed to the View object that corresponds to the type of request made (i.e. SOAPView,RPCView, HTMLView, etc). The View object formats the response variables appropriately and displays the finished result.
What display types does Phritz support?
Currently, Phritz supports output in xHTML, WML, SOAP, XML-RPC, and AJAX(XML). I am also planning on supporting JSON and RSS.
What's the point?
The trends toward non-standard access of web data (i.e. not through a browser) are undeniable. The use of Web Services is increasing, creating "mash-up" websites that people can use to access the content of any number of other sites. Desktop gui applications such as Flock, Firefox, Thunderbird, etc. are increasingly utilizing the web services of sites to allow users to obtain data without ever loading a web page. In addition, the use of mobile browsers is increasing, forcing companies to rewrite entire applications to output WAP format instead of standard HTML. The goal of Phritz is to facilitate the move toward these trends by allowing developers to create applications that offer these web services and WAP compatible content without having to go through the hassle of coding them manually.