Paging Dr. Frankenstein…

This is an old post from my previous Joomla!-powered site; sorry for the retread.

---

The title’s pretty apt, I think–Cloverleaf is far less my code than anyone else’s at this point, made of bolting together all sorts of stuff. Open Source in action, yo.

A few quick updates regarding Cloverleaf, as some folks have expressed some interest in the project. I’d like to throw a shout-out to Franz, whose questions got me off my ass and drove me to write a little documentation for installing the pre-pre-pre-pre-alpha CloverleafET code. If anyone else is interested, you can access that documentation on the Mono GSoC 2008 Google Groups page.

Last (first) blog post, I mentioned that my next goal was going to be getting ASP.NET to work remotely. It’s done…mostly. XSP2 support works, for a moderate value of “works”–there’s a possibility of leaving zombie processes and it currently is hardcoded to port 8080–and will be touched up in the next week or so. Apache2 support might take a little longer; that’s going to be much messier than I’d hoped for. Zeroconf also works, although I haven’t written any configuration for that yet so all you’ll see in the service browser is “Cloverleaf [$machinename, Unix]“.

I haven’t tested it on Linux using Avahi yet, because Ubuntu’s habit of making eight hundred million packages for any application you want to install is making it seriously painful to get working; I’m about ready to say to hell with Ubuntu and install OpenSuSE. If they hadn’t defaulted to KDE 4 (utter, utter crap, and no I don’t care that they say it’ll “get better later,” I’ll jut stop using Linux on the desktop when they drop support for KDE 3), I’m sure I already would have. But CloverleafService should run just fine if you can puzzle out how to put together the various bits and pieces.

Making progress, though. The next week will mostly be fixing the bits and pieces mentioned above, making remote instantiations of XSP2 listen on random ports so multiple users can use it and doing a little configuration work for CloverleafService. Then, it’s off to actually writing the add-in portion of the code so it actually plugs into Visual Studio and doesn’t just lout around in External Tools.

If you’re interested in Cloverleaf or any of the Mono Project’s other GSoC projects, the development trunk can be checked out from our Mono Project GSoC 2008 page on Google Code. You can also see our development discussions and weekly reports on our Google Groups page. Eventually, Cloverleaf will probably find a place to live here on my website, but that’s a ways off at least.