I want pizza!
(sorry for my painful english)
In the last weeks, I had trouble using SVN in my University. I talked to the network admin, he said it should be working, and now he is going to fix it. That’s good news for next week. But I couldn’t wait: I did an incredible workaround (“gambiarra” in portuguese… do you know Gambiarra? 
), so incredible that I’m ashamed of writing about it in details.
I’ve been reading several tomboy addins code, and got the idea of the implementations. I’ve already coded something I think will be the “skeleton” for my addin. C# is very easy – but I think it’s weird. Even Java is more elegant… Anyway, I prefer Python ;D.
Monodevelop is very nice. Monodoc is cool. I just didn’t get the point on not using devhelp instead. (Okay, maybe they wanted to keep .NET documentation grouped and isolated from the rest…).
Everything seems to be alright, the only problem now is: I haven’t eat pizza for two weeks. I ran out of money traveling to Porto Alegre (FISL) and now I’m desperated!
P.S.: 10% of my GSoC money is reserved to pizza. Plus other 10%, for home-delivered pizza, and 10% for that frozen pizzas we can buy in supermarkets.
Subscribe by RSS
Jonathan Pryor Said,
May 9, 2008 @ 3:01 pm
I can’t speak to why devhelp wasn’t originally used, but I can speculate.
The ECMA standard includes some class library documentation, and it was useful to reuse this documentation to bootstrap Mono’s documentation.
However, the ECMA documentation was in a custom XML dialect. This isn’t too different from how other doc systems use docbook XML.
We could have provided an XML->HTML conversion script, as docbook provides, but monodoc has one feature that devhelp doesn’t: editing support.
Had we relied only devhelp, we couldn’t have allowed any editing of the documentation, and it would have been more difficult for external contributors to help with the documentation effort.
Gabriel Marcondes Said,
May 9, 2008 @ 9:18 pm
Thanks, Jonathan!