Comments for darcusblog http://community.muohio.edu/blogs/darcusb geek tools and the scholar Sat, 07 Nov 2009 16:23:08 +0000 http://wordpress.org/?v=2.7 hourly 1 Comment on Public Work From the Start by darcusb http://community.muohio.edu/blogs/darcusb/archives/2009/08/07/public-work-from-the-start/comment-page-1#comment-1804 darcusb Fri, 14 Aug 2009 12:55:30 +0000 http://community.muohio.edu/blogs/darcusb/?p=667#comment-1804 <p>Thanks Chris. Good to see you trying to push repositories forward, as I really haven't found that model very compelling. </p> <p>When I get around to it, for example, my publications will be hosted on <a href="http://bruce.darcus.name" rel="nofollow">my own site</a>, as easily accessible XHTML (I did have code that integrated commenting on the articles via disqus, but had to pull it because of bugs in their software w/XHTML).</p> <p>On the SCM, I'm just using darcs, where I keep a sort of master repository on my main site, and then keep local copies wherever I work. The distributed nature of darcs means I have effectively full backups on every machine I am working on.</p> <p>I may open this up to web viewing later, but am not going to worry about it ATM.</p> <p>As you may guess from the above, I think SF is a horrible model for this. But then I don't much like the idea of centralization to begin with. It seems preferable to be able to simply copy/fork a distributed repository to a central local if/when the need arises. Of course, for this to be valuable to people other than technically-savvy geeks, you'd have to put some work into a nice UI; maybe something along the lines of <a href="http://github.com/commandline/flashbake/tree/master" rel="nofollow">this</a>.</p> Thanks Chris. Good to see you trying to push repositories forward, as I really haven’t found that model very compelling.

When I get around to it, for example, my publications will be hosted on my own site, as easily accessible XHTML (I did have code that integrated commenting on the articles via disqus, but had to pull it because of bugs in their software w/XHTML).

On the SCM, I’m just using darcs, where I keep a sort of master repository on my main site, and then keep local copies wherever I work. The distributed nature of darcs means I have effectively full backups on every machine I am working on.

I may open this up to web viewing later, but am not going to worry about it ATM.

As you may guess from the above, I think SF is a horrible model for this. But then I don’t much like the idea of centralization to begin with. It seems preferable to be able to simply copy/fork a distributed repository to a central local if/when the need arises. Of course, for this to be valuable to people other than technically-savvy geeks, you’d have to put some work into a nice UI; maybe something along the lines of this.

]]> Comment on Public Work From the Start by Chris Rusbridge http://community.muohio.edu/blogs/darcusb/archives/2009/08/07/public-work-from-the-start/comment-page-1#comment-1803 Chris Rusbridge Fri, 14 Aug 2009 09:39:23 +0000 http://community.muohio.edu/blogs/darcusb/?p=667#comment-1803 <p>I've been worrying a bit about aspects of this also. The first thing to remember is that there is a well developed repository movement; if you are careful about the rights you grant to publishers, and read the small print, you can deposit a version of your paper in your local repository for free access (sometimes after an embargo period). Then, on making the repository more useful, see the series of posts starting at http://digitalcuration.blogspot.com/2008/07/negative-click-positive-value-research.html, and ending with http://digitalcuration.blogspot.com/2008/08/comments-on-negative-click-research.html. On whether source code repositories could be useful for these purposes, http://digitalcuration.blogspot.com/2009/04/libraries-of-future-sourceforge-as.html reports some interesting discussions. But if you make progress on your "source control and backup system for manuscripts", I'd love to hear...</p> I’ve been worrying a bit about aspects of this also. The first thing to remember is that there is a well developed repository movement; if you are careful about the rights you grant to publishers, and read the small print, you can deposit a version of your paper in your local repository for free access (sometimes after an embargo period). Then, on making the repository more useful, see the series of posts starting at http://digitalcuration.blogspot.com/2008/07/negative-click-positive-value-research.html, and ending with http://digitalcuration.blogspot.com/2008/08/comments-on-negative-click-research.html. On whether source code repositories could be useful for these purposes, http://digitalcuration.blogspot.com/2009/04/libraries-of-future-sourceforge-as.html reports some interesting discussions. But if you make progress on your “source control and backup system for manuscripts”, I’d love to hear…

]]> Comment on Google Wave and Rich Text by darcusb http://community.muohio.edu/blogs/darcusb/archives/2009/07/30/google-wave-and-rich-text/comment-page-1#comment-1793 darcusb Thu, 30 Jul 2009 21:49:05 +0000 http://community.muohio.edu/blogs/darcusb/?p=659#comment-1793 <p>Oh, that IS a good start; wouldn't have bothered with the post if I'd seen that. But I didn't see it, b/c it's behind the exceedingly misleadingly named "paragraph size" icon. </p> <p>Odd too that the automatic title style is rendered much smaller than h1.</p> Oh, that IS a good start; wouldn’t have bothered with the post if I’d seen that. But I didn’t see it, b/c it’s behind the exceedingly misleadingly named “paragraph size” icon.

Odd too that the automatic title style is rendered much smaller than h1.

]]> Comment on Google Wave and Rich Text by Martin Fenner http://community.muohio.edu/blogs/darcusb/archives/2009/07/30/google-wave-and-rich-text/comment-page-1#comment-1792 Martin Fenner Thu, 30 Jul 2009 21:39:37 +0000 http://community.muohio.edu/blogs/darcusb/?p=659#comment-1792 <p>It's not much, but Google Wave has support for headings (H1-H4).</p> It’s not much, but Google Wave has support for headings (H1-H4).

]]>