Problems
=======
* Trouble with my SVN Mono runtime segfaulting everywhere at seemingly
random times, making me think that it might be a threading issue.
Several things hand changed -- upgrade to dual-core processor,
switched to using CFQ elevator, a load of OS updates, Mono SVN updates
-- and I wasn't able to determine which was resopsible for this issue.
I stopped installing Mono SVN over the OS-supplied one, and set up a
proper parallel-installed Mono environment. When I went back to the
OS-supplied 1.1.13, it doesn't seem to have this problem. It may be a
runtime regression, but I have not yet conclusively tracked it down.
* Still not looked at framework issues preventing document saving on 2.0.
* Not looked at GnomeVFS project deployment.
Plans for next week
==============
* Project deployment
* Fix as many as possible of the other minor items on my to-do list.
--
Michael Hutchinson
http://mjhutchinson.com
> * Not looked at GnomeVFS project deployment.
I suggest that you do not waste time with GnomeVFS, as this is one
area that everyone hopes will go away with something like FUSE.
Also, the VFS abstraction in general tries to expose things that are
not a file system as a file system, with all the shortcomings and hacks
that this involves.
A better approach would be to custom-build each deployment
mechanism as it would give us control over the actual deployment
and the user experience.
Please do not use the Gnome vfs
Oops, too late, I got it working last night. In my defence, it *was*
in my proposal...
On the plus side
1) People have GnomeVFS
2) I don't have to write lots of different providers, with different
authentication mechanisms etc; it can already deploy to any Gnome VFS
mounted volume.
TBH, I'm not sure right now that we actually need any more control
than GnomeVFS gives.