cfRhino / News: Recent posts

I have been working, recently, on adding auto-wiring to CFRhino to make the instantiation and use of components a little easier. Up to know, you would have had to create and pass in any objects that your primary object might require. This can be problematic, if you consider the following non-trivial scenario from a possible forum application:

Forum object requires the UserPreferences object
Thread object requires the UserPreferences object
Thread object requires the Forum object... read more

So I had a lot of problems, in my own mind, with the current release of CFRhino. It is not particularly Object Oriented, it makes a great deal of use of the application and request scopes and requires the developer to use them too. This is not supportive of one of the most importante tennets of OO design, namely encapsulation of data. The data is out in the shared scopes for all to see.

So I have started to redevelop it. I've chosen to start with the rhino_core packages. I've so far removed all references (I think) to application scopes inside the CFC's and have also tried to reduce the volume of data exchange, but init'ing those CFC's with references to the rhino core CFC. I'm pretty happy with how it's going. Check out the Subversion trunk if you want a better look.

I have just tagged a release version of Rhino in the SVN. Find it at;

https://cfrhino.svn.sourceforge.net/svnroot/cfrhino/tags/0.3.1

NOTE: The path to the SVN repository has changed as of the end of Nov 06 so update any links you may have. I will try and post a download when I get a chance.

Finally, after a couple of months working on the framework, I have released the (CF)Rhino into the wild. It's probably at a beta stage, but a good beta and is working nicely in all areas (I've tested). As with nearly all other Open Source devs I've encountered, the documentation is a little light on the ground, but if you want some starters before the docs are in place then feel free to email me. So download it and enjoy.