"Love JavaScript? Now you can write desktop apps, widgets, and web pages all using the same platform." ..that made me giggle
On the serious side, http://ajaxian.com/archives/adobe-apollo-at-max sounds like fun, wonder if I can write nice apps with RIFE and OpenLaszlo..

I don't want to bury Geerts' facebook news (http://rifers.org/blogs/gbevin/2006/8/16/facebook_uses_rife), but I found this nice AJAX course on http://www.javapassion.com/ajaxcodecamp/. I still have to start with the first lesson, but a quick glance shows that its quite well done, and I'd take it if only for learning more about Firebug's Javascript debugging capabilities.

When a website is a big as e.g. blogspot.com, you'd expect them to at least have nailed the nitty gritty interface details. When I commented on the blog I linked to in the last post, I found these small things which made me wonder why people can't 'put the dot on the i' (pay attention to the last little details) as we say in dutch.
The small details I'm talking about are:

1. When there is 1 (one) comment, they say '1 comments'. This might be faster to execute (no code needed), but if that's really the reason I would be very much surprised :-)
2. If you comment on a story and choose 'anonymous', the submit button is still called 'Login and Publish', which was a bit confusing to me. A little Javascript is not too much to ask here is it, and otherwise a different title for the button maybe..

I told you these were little details, but thats where the devil is ;-)

Going to be following this page to see how my former collegue does. If he makes it to millionaire, at least I can say I helped him ;-)
[back to the regular transmission]

This is not a RIFE post perse, but since my dayjob is working with PHP, and since I could not easily find this information elsewhere, I figured I'd write a bit about it.

I had looked at using Eclipse as my php IDE before, but the problem seemed to be that Eclipse wanted everything to be in its workspace/project directory structure, whereas I like to have my php documents in my DocumentRoot directory.
The workaround I found before was to symlink from the Eclipse project directory to the docroot, but that seems like an ugly hack, and working on Windows one would have to work with the not so well documented 'junction' feature of window nt..

When I was browsing the EasyEclipse.org site I happened to find this post that explains how to set up the structure. Because it is a bit lacking in its explanation, I give you a more complete explanation, where I assume you have installed EasyEclipse ' LAMP distribution. Any other Eclipse + phpEclipse ought to work as well.

1. Start Eclipse, and create a new PHP project, with a name of your choosing
2. uncheck the 'project contents' box, and then fill in the path to your php files (not the docroot perse,e.g. /www/htdocs might not be it, cause you also need files from /www/settings, in this case you'd fill in /www)
3. click 'finish'
4. now rightclick on the project folder in the navigation pane on the left, and choose properties.
5. Choose PHP Project settings on the left, and click 'use project settings'. Fill in the URL to your local site and the docroot (/www/htdocs in my example) . Add the Include path(s)
6. Now click on the PHP Parser link on the left in this same window, and choose 'use project settings', so that the PHP Parser will know to use your projects' specific settings.

Now click OK and you're done with this part.

EasyEclipse also comes with CVS/SVN and DB tools, which a typical LAMP setup probably also uses, but setting those up are something I leave up to you.