Last week we had a Mono Summit in Cambridge, notes from the various discussions and developments are available here: http://www.go-mono.com/summit-notes.html
Posted on 26 Oct 2004
John Pilger documents the Story of Diego Garcia and the cleaning of the native population in the 60's.
The story has a happy ending, those expelled from Diego Garcia received 3,000 pounds (each).
There is more information on Pilger's site.
Duncan has done some work to bring the NodeStore/NodeView to life, simplifying the life of those using the TreeView, here is a screenshot from his blog entry:
Posted on 25 Oct 2004
Interesting article: 100 facts, 1 opinion.
Btw, you can not use `Fox News' as your fact check source ;-)
Thanks for all the e-mail on the Gnome Notifier. Am not interested in turning this prototype into a working product, there are better efforts underway. The point I was trying to make on my last post was that early on I realized that we needed the notification system to do more than just show a message: it is important to be able to have a list of actions associated with it that I can click on.
My toy Gnome Notifier was written a few years ago as a sample program that I wanted the Gnome people to productize. It was not meant to be a real or completed program.
Nicholas Petreley has a Security Report on Windows vs Linux.
Posted on 24 Oct 2004
Jamin, you might want to read the news articles posted from Enjoy the Draft's FAQ. I was particularly interested in question (5).
Posted on 23 Oct 2004
A good companion is: Improving .NET Application Performance and Scalability.
Calum writes his feelings about notifications: they should not have options. And here lies a problems with the view on notifications: am personally not interested in the equivalent to `tail -f some_log'. I want my notifications to be interactive, and hence those options seems awesome.
I am personally interested in a notification framework to the desktop to avoid things like GAIM popping up a dialog box in the middle of writing an email that asks me if I want to accept a buddy or not. In this particular case having a default button makes things worse, because I do not know which people I have accepted or not accidentally. I literally have this problem every day.
In fact, I want to have a log not only of notifications but of actions to follow up to. So some notifications should not go away, they should stick around, and when I have the time I can go and click the appropriate buttons `accept', `accept', `reject', `reject'.
Some other notifications can just go away: if I have not responded to the CD insertion action, it can likely go away from my screen.
Longhorn keeps track of notifications that the user has not seen.
My old gnome-notifier does exactly this, and supports a special kind of url `run:' that you could use to run programs in response to actions.
Elijah Gaim is one of the applications that have this behavior. But even if you do not steal focus, I do not want a window popping up in the middle of the screen for GAIM. I want these kind of notifications to go elsewhere (Windows uses a baloon and the proposals so far are along the same lines: notifications are out of your current work area).
An educational website: Enjoy the Draft Dot Com.
The FAQ is a must-read.
A lighter, more positive side of the draft.
Posted on 22 Oct 2004
I am the last one to notice monoForge a site that allows you to test your Web-based Mono application on Linux. During the beta period the service is free.
Another version is MonkeyPop which uses Mozilla. MonkeyPop uses a set of tools for developing desktop applications called the Chicken Framework. One nice thing about the Chicken Framework is that its distributed with documentation.
It would be nice for the authors to work together.
Posted on 21 Oct 2004
Tomorrow the 21st I will be participating on the Evolution E-Plugin hackfest. The hackfest will take place in the #evolution IRC channel on irc.gnome.org.
We will be learning the E-Plugin interface that Michael Zucchi designed for Evolution. Now Evolution 2.x can be extended with user code to implement your favorite missing feature or your favorite aberration.
Plugins are typically built with C but there is a Mono interface so any Mono supported language can be used to extend evolution.
This blog entry has some demos of the E-Plugin from August, it will give you a few ideas of what can be done.
Mark has Gecko-sharp running on Windows (this is the Gecko binding for Gtk# running on Windows).
Gecko# on Windows.
Posted on 20 Oct 2004
Echoing Nat's post on the fifth anniversary of the incorporation of Helix Code.
A lot of cool innovation on top of Mono/Gtk#.
Posted on 19 Oct 2004
An interesting article studying Microsoft as a citizen, based on the ideas from the movie "The Corporation".
The author wrote a very interesting follow-up to it.
Update: Nat has posted his thought on Microsoft. A must read.
Jon Stewart is my hero. His appearance on CNN this Friday was unbelievable. He showed the world the state of journalism in the country.
This week all the Novell Mono developers came to town for our semi-annual meeting.
Posted on 18 Oct 2004
If you were looking for information about the now extinct Dodo, look no further than here. The first match in Google is not about the Dodo, its about some Internet provided in Australia.
We learned from Dare that XML 2 was going to get some features cut, which is a good thing for us, as there is less to implement. Kind of a shame, since Atsushi has a good foundation for XQuery already on the Mono tree. Until XQuery is added back to the Framework, we will likely distribute a Mono.XML assembly that contains our implementation of XQuery for those interested in using it before the next major revision of the .NET Framework.
Atsushi had been working on our XQuery implementation for Mono, and has some insight on its current design and limitations.
To add humor to this, Nat found the the ChangeLog entry for it:
Modified Files: gtkprefs.c Log Message: Simplified the prefs dialog by replacing the tree with tabs. You may think this is a bad idea, but it"s not.
Posted on 14 Oct 2004