One huge question to ask is why you need an editor specifically for a tree. Do you want a gui, or a format? If you need a gui, you are automatically in domain-specific territory. If you only need a format, maybe you don't need a tree editor at all. Excel is a great tool for making trees; just add a column that names your parent. I used Excel to create a prototype of an event driven animation sequencing engine for a D…
> If you need a gui, you are automatically in domain-specific territory. The author specifically describes a platform in which domain specific concerns are facilitated by plugins, so I don't see why we are "automatically in domain-specific territory". One could easily envision classes of plugins for drawing nodes and edges (perhaps a canvas DSL), plugins for enforcing the domain's specific rules, etc.
Re: Why Don't We Have a General-Purpose Tree Editor? (2014)
#221Yes, it seems like something like Naked Objects[0] combined with domain-specific plugins / components could do quite nicely.