Ed,
Thanks for your post! The short answer to your question is, yes -- all three feature line-items that you've listed is on the list of things that we want to add into the Framework.
More specifically, logging will probably be integrated soon.
The hooks for session storage are already in place (e.g. there's a UseSession constant preference in the QForm class), and internally, we already built one prototype which works decently, but we're trying to clean it up a bit before putting it into the core.
For the textbox, i think you're talking about an autocomplete textbox, similar to google suggest (http://www.google.com/webhp?complete=1&hl=en) ? Actually, everything is already in place for you to be able to create your own QControl (which would likely extend from QTextBox) to do something like that. We were hoping to have a QAutoCompleteTextBox control as an official part of the core... but no one has been able to work on it yet. (e.g. the example at http://examples.qcodo.com/examples/events_actions/delayed.php at least shows the beginning of having PHP methods called via AJAX whenever stuff is typed into a textbox -- this new control would basically just expand on that php method)
In terms of the larger question of which direction to go... I think you can't really go wrong with any of the great frameworks out there, whether it'd be Rails, or any of the other PHP frameworks like Cake, Symfony or PRADO. I personally feel there are some advantages to a PHP-based framework over a Java/.NET/Ruby one (in terms of the language construct, itself, as well as the massive library of open source components you can download), but to each his/her own.
Specifically for Qcodo, I feel that the Qform library is a compelling architecture for the view/control layer of your application, and i think the concept of stateful, event-driven web forms (also seen in ASP.NET, JavaServer Faces, PRADO and XForms) is going to continue to grow as frameworks begin to incorporate the architecutre more and more.
Also, the one very different aspect of Qcodo vs. the other ORM-based frameworks is its use of Code Generation vs. runtime reflection to create your object relational model. You can see http://www.qcodo.com/documentation/article.php/6 for more about this.
Obviously, we'd like it if you went with Qcodo =), but to be honest, despite these architectural differences I listed, most of them offer (in terms of functionality) more or less the thing, and I really don't think there's a “wrong” choice.
Because you're investing the time to ramp up in and architect your system on a solid framework of any kind, I think you've already made the “right” choice. =)
Good luck w/ your decision.
--Mike