Ex-Framework Apr 3 2006

As some people may or may not have noticed, I have given up on the xFramework project. The various related project url’s now point to this very blog, and I guess the reason I gave it up is because I figured it just wasn’t that useful. There were no other contributors, so there are no licensing issues - obviously any one who took a snapshot of the licensed code is free to continue to work with that code based on the terms under which it was licensed, however going forward the repository has been retired, and I will no longer work on or continue to update xFramework. Going forward, for those that are interested, I will take the most useful parts of xFramework (namely the reflection helper code, the unit-testing framework, and the web/Xml stuff) and use it to form my own “internal” framework, upon which I will base a few applications I’ve been dreaming up. I’m hoping this will be a more streamlined approach for me, and might work out with better results than if these applications were based on a separate open-source framework I had to maintain aswell.

More news to follow on the result of this change, and the applications I’m working on, shortly I hope.

And for those wondering what happened to my series of articles on Ruby on Rails, I’m working on a BIG next installment, that’ll be a complete walkthrough of my experiences creating a simple database web application, from start-to-finish. The idea is that all the basics, resulting in a fully functioning app, will be completed by the end of this next part, and the following tutorial will then fill in some fancy details, like some advanced style techniques, AJAX, alsorts of extras.


Technorati Tags: , , , , , ,

codingeleldiablomonopersonalprogrammingrubytechxframework