Enterprise 2.0 suite
I have been working internally on a project for my company to promote the application of Web 2.0 behind the corporate firewall, and I must say this has been the greatest time of my life in the IT industry for having the opportunity to directly be engaged in the innovation and creation process of the software lifecycle…and hence, all my Ruby posts below.
With my new found faith in Rails, I have to say I have never find web development so engaging and interesting. The days I used to spend configuring struts and tiles (Java MVC framework) has literally been used to producing something nice and functional on the screen. Speaking of which, AJAX has never been easier on Rails with the introduction of link_to_remote and form_remote_tag functions, where you can map the action to a method in a controller directly, and hear this : MULTIPLE UPDATES OF DIVS with AN RJS TEMPLATE!!!!!!
RJS (Rails JavaScript???) template is a template where you can throw javascripts back to the views by specifying the div tags you want the content changed. How easy can this be ? The learning curve is also really low as you can practically find tons and tons of tutorials on the magic of it on the internet.
I better stop bragging about Rails before all of you run away. 
I have been seen as a fanatical fan of Rails.
I have also managed to throw my new found love of AJAX into the blog engine I wrote as part of the Enterprise 2.0 suite and the effects do throw me back. Some of the effects are a bit exaggerative and does not necessary translate to good usability, but the majority of it are really good. The blog engine is fully functional, with minor UI tweaks awaiting. Of course, unit-testing hasn’t been performed but continuous integration test has been performed on it from time to time (excluding unit-test 
).
The project has since been made open-source at http://enterprise20.rubyforge.org and I encourage any participation on it. I will continue development on it whenever I have the time (just been reassigned to a different client within the company) and should anyone be interested in contributing to the project, do let me know. The page looks pathetic now, but I will be throwing in some new content in it very soon.
Would be nice if RubyForge allows me to throw my blog engine onto it, wouldn’t it?
You wrote: “Of course, unit-testing hasn’t been performed but continuous integration test has been performed on it from time to time (excluding unit-test
).”
Umm, if it’s from time to time - does that still make it continuous?
/me runs away and hides
Sorry, I just have nothing better to do right now.
I suppose it would if time-to-time means “Twice built daily” with the help of say continuum.
I wrote a small script to do it at home, so didn’t have to install some heavyweights to run the continuous integration part of it.
Fair enough :).