I have been working on a sort of unframework for a little while (although at first it was intended to be a complete framework with routing and similar functionality not in Flourish). Instead, I have opted to leave it more open just like Flourish does and so the classes I have made (all of which begin with 's') are designed to be used just about anywhere, be it your MVC framework, or generic procedural code, or even CLI scripts.
A short description of what each class intends to do or help with:
sArray - array utility functions
sAuthorization - has a method requireNotLoggedIn() that does the reverse of requireLoggedIn()
sCache - extension of fCache but makes each key unique so cache keys (like those of APC) do not collide
sGrammar - extension of fGrammar; has a method dashize() that does the same as underscorize() but with dashes; it uses fURL::makeFriendly() but also supports camelCase notation
sHTTPRequest - a simple object class to do HTTP requests from the server side
sImage - a questionable extension to fImage; this was mainly made because fImage::rotate() does not take into account IFD* exif data that contains the orientation information; has a flip() method for flipping pixels vertically or horizontally or both (this is required by some orientations)
sJSONP - like fJSON, but for sending JSONP responses
sProcess - An object class to run processes, including interactive processes; tested on Windows as well
sRequest - Generally, when I handle a POST request, I redirect the user after. This means that if the user hits the back button, first they are not bothered by that annoying message that is meaningless to 99% of users, but also it means that the data from the form is not put back by the browser (which means less usability). sRequest::savePostValues('some_id') can save the POST values into session for later retrieval. You can delete the values when the form is submitted successfully by calling sRequest::deletePostValues(). You can restore the POST values (calls fRequest::set()) when re-rendering the form after a validation error by calling sRequest::setPostValues(). This class also has a non-throwing method to check a CSRF token string, useful with fValidation::addCallbackRule().
sResponse - For general HTTP header responses. More to come in this class.
sTemplate - This is an alternative to fTemplating which is similar to PHPTemplate. If you have used Drupal in the past, consider sTemplate::buffer() to be equivalent to Drupal's theme() function and the .tpl.php files will not be unusual to you. Features CSS minification optionally using CssMin and CDN support. See the documentation and tutorial for more details.
sTimestamp - This is an extension fTimestamp that can receive a RFC3339 timestamp as well as whatever can be parsed by fTimestamp.
https://github.com/tatsh/sutra
Of course, this unframework is dependent on a potentially patched Flourish (see the patches directory).
There is a tutorial here on how to get started fast: https://github.com/tatsh/sutra/wiki/Tutorial
Documentation: http://tatsh.github.com/sutra/
I'm doing a final check before the final version of 1.2 is released. Will be very soon.
Ideas for version 1.3: https://github.com/tatsh/sutra/wiki/Roadmap
And of course if you would like to join, simply fork, and make a pull request with your changes. My standards are almost the same as Flourish', but just a few changes: 'public static' instead of 'static public', bracket on the same line for (public static function {), end bracket on separate line (not '} else {'), and 2-spaces instead of real tabs.