Concord, our GPL outliner

Re:Concord, our GPL outliner by jerf on Monday September 16, 2013 @02:06PM (#6394722)

I've fiddled with this extensively. The problem isn't data representation; sure, "outlines" are "just" graphs. The question is, what on Earth does your UI look like? Editing "graphs" is hardly more structured than creating a "data editor"... ok, those are some nice English words you've got there, but how does it actually work?

At least by limiting it to text and stuff that looks a lot like text, you can produce a real application that does real things of real value. It may not be suitable for everything, but your thing that is suitable for "everything" is likely come out being suitable for nothing in practice.

[ Parent | on HN ]

Re:Concord, our GPL outliner by smoyer on Monday September 16, 2013 @03:17PM (#6395205)

That's a hard problem - I haven't done any "fiddle" but I've spent a lot of time doing Gedankenexperiment and haven't come up with anything I believe is remotely applicable. The genealogy example I gave is simpler but I'm not sure I've seen an editor for that use-case that's optimal either.

Maybe the problem just can't be simplified further? And as an aside, I wasn't trying to disparage Dave Winer's implementation of tree editing at all.

[ Parent | on HN ]

Re:Concord, our GPL outliner by andrewflnr on Monday September 16, 2013 @03:47PM (#6395451)

I wrote one. It might not be exactly what you had in mind. It works okay for me for brainstorming: github.com/andrewf/graphpaper

[ Parent | on HN ]