# Order of Pipeline Browser Objects

**URL:** <https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685>\
**Category:** ParaView Support\
**Created:** [December 22, 2021, 10:05pm UTC](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685 "2021-12-22T22:05:50Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)\
**Post date:** [January 4, 2022, 3:25pm UTC](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685/22 "2022-01-04T15:25:46Z")

</div>

You may be interested by the node editor plugin though:

> [@Official Node Editor in ParaView ?](https://discourse.paraview.org/t/official-node-editor-in-paraview/6295/9):
>
> Since it looks like this conversation is the most up-to-date on the discourse regarding the node editor, I’ll just point some informations here : the node editor has been officially merged into ParaView, see : [https://gitlab.kitware.com/paraview/paraview/-/merge\_requests/4952](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4952) there’s issues already logged in the repo at [https://gitlab.kitware.com/paraview/paraview/-/issues/20726](https://gitlab.kitware.com/paraview/paraview/-/issues/20726) so everyone is aware of what the current limitations are. Feel free to add/resolve/comment stuff on this issue if …

---

_[View the full topic](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685)._
