2 ms·
I think we don't have a general-purpose tree editor for two reasons: 1. Nobody knows what it should look like. 2. Nobody knows how it should work. I fear thi
by throwanem 10y ago
I think we don't have a general-purpose tree editor for two reasons:
1. Nobody knows what it should look like.
2. Nobody knows how it should work.
I fear this article has left me as much in the dark on these points as I was before I read it. Perhaps someone else here will find something in it I missed.
- supergreg 10y agoFWIW the editor in Chromium's and Firefox's developer tools are pretty good. I'd really like to see something like that as a standalone tool for both trees and XML and see how far it can be taken.
- throwanem 10y agoThe inspector? I've seen and worked with similar tools for XML, too, though not recently. They're very good for small, constrained hand-editing, but I find them to scale extremely poorly.
- therealmarv 10y agoFor XML you may want to take a closer look at XML Marker 1.1 (it's old, freeware and Windows but still better than many other tools) and maybe Eclipse.
- dTal 10y agoI think that sums it up. We really can't top crufty old Windows freeware? There is a gaping hole in the market.
- therealmarv 10y agoThe last time I worked on complex XML I even used XML Marker with WINE... it works there. If you want the Mercedes of XML editors you should take a look at Oxygen XML editor (this is not free but runs on more platforms than Windows).
- xchaotic 10y ago+1 for OxygenXML - it is very actively developed and has its own CSS engine that goes above and beyond what browsers can do. So you can style your tree with CSS.
- throwanem 10y agoOr the market is smaller than it might seem.