# Potential language extension for graph object classes - motivation, design

**URL:** <https://forum.graphviz.org/t/potential-language-extension-for-graph-object-classes-motivation-design/968>\
**Category:** Dev\
**Created:** [January 6, 2021, 3:10am UTC](https://forum.graphviz.org/t/potential-language-extension-for-graph-object-classes-motivation-design/968 "2021-01-06T03:10:31Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![scnorth](https://sea2.discourse-cdn.com/graphviz/user_avatar/forum.graphviz.org/scnorth/32/89_2.png) [@scnorth](https://forum.graphviz.org/u/scnorth)\
**Post date:** [January 6, 2021, 3:10am UTC](https://forum.graphviz.org/t/potential-language-extension-for-graph-object-classes-motivation-design/968/1 "2021-01-06T03:10:31Z")

</div>

It’s not so important. The meaningful problems are bugs in spline routing, orthogonal edge routing, the “trouble in init\_rank” that would not die, lack of object classes in the graph language, and one or two outstanding CERT advisories. That weird bug with ports on record nodes being flipped in certain left-to-right layouts Incrementally stable layout in dotgen, Can gvedit make the jump to QT6. New algorithms that could help with untangling hairballs. These are interesting topics.

---

_[View the full topic](https://forum.graphviz.org/t/potential-language-extension-for-graph-object-classes-motivation-design/968)._