Re: [Orgmode] Org Radio

[David O'Toole]

Hello Bastien,

I really like the region idea. However it could be very tricky to
implement. The annotations in the radio file would be matched to
regions in the target file. So presumably we save the region's
coordinates in the radio file along with its annotation. We can use
markers and overlay properties to keep these data consistent in the
face of changes that happen in an Emacs buffer, but if a file can
change outside Emacs (i.e. annotating a shared file in version
control) then we have a problem, because (in the new model you are
suggesting) there was never anything in the file itself to indicate
which regions go with which annotations. That model is interesting
because it means you can annotate files without changing them
(i.e. notes on /etc). But I don't see how to keep the radio file from
breaking.

But maybe I am missing an obvious solution---can you give more details
on the GPLv3 thing you are referring to?

--dave

From: Bastien <address@hidden>
Subject: Re: [Orgmode] Org Radio
Date: Sat, 22 Dec 2007 19:49:34 +0100

> Hi David,
> 
> "David O'Toole" <address@hidden> writes:
> 
> > I'm writing an add-on for Org (again!)
> >
> > This one is called radio.el. It lets you annotate files (or even
> > individual lines within files) with arbitrary org subtrees.
> 
> Great!  I played with it a bit, and I like the general idea.  I thought
> about doing something similar a while ago, because the one thing I lack
> in Emacs is the ability to take notes against one particular file and to
> see from within the file if there are notes attached to it...
> 
> Maybe one direction for further improvements: I don't really like the
> glyph ":>".  I would prefer that taking notes is done against a region
> and that the whole region get overlayed when you activate radio-mode (or
> whatever mode it could be.)
> 
> Remember the GPLv3 comment process and the way comments were overlined.
> Turning your mode on could overline regions that are annotated, and
> those overlined regions could link to the note in the attached Org
> file...  
> 
> Does this fit with your use of the tool ?
> 
> -- 
> Bastien