Today I wanted to give ColdFusion 8 debugging a try.

So, I started followed the instructions on how to setup the enviornment for debugging. After installing ColdFusion 8 extensions for Eclipse, I went to enable debugger in ColdFusion Administrator. The CF administrator instructs that:

You must specify this debugger port in the JVM settings of your application server, for example: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005, and restart the server.

If I was using JRun, I know that these options can be added in the jvm.config file.

But as I use JBoss, it took me little bit to figure out where I need to make these changes.

Read more...

Just saw an interesting article on Engadget that compared iPhone SDK to Windows Mobile, Android, S60 and Toolchain.

What is really interesting is that Windows Mobile along with Nokia S60 supports Flash.

iPhone, as you know, does not support Flash (and won't support it any time soon, given Apple's comments yesterday about Flash being too slow to run on iPhone).

And what is even more interesting is that Microsoft and Nokia have signed a deal to make Silverlight available on Nokia S60 and S40.

So two things really:

1. Adobe needs to do something to get on to the iPhone platform. AIR runtime perhaps?
2. Adobe needs to look at engaging Nokia for AIR runtime.

Here is the article at Engadget: iPhone SDK Comparison Chart.

A note to myself: The only constant in life, Indy, is change!

I've been using Subversion for version control for a couple of years now. It was quite a change moving from Microsoft Visual Source to Subversion. A different mind set. A different way of doing things.

And then I read about Mercurial today.

Mercurial is one of the new breed of version control systems.

Its major goals include high performance and scalability; serverless, fully distributed collaborative development; robust handling of both plain text and binary files; and advanced branching and merging capabilities, while remaining conceptually simple. It includes an integrated web interface. (Wikipedia)

Basically Mercurial moves away from the paradigm of working with centralized repositories (like CVS and SVN) to support distributed, collaborative development. And at the same time trying to be a simple-to-use system (a big challenge!).

ﾠ

Read more...