Here is an example of what I am saying.
the group create package is the only one visible for editing and the one with the icon is the only one not visible on page load when previewing the app.
It would be help if it was like this because the element tree is still confusing.
Well let us think about it and see what users say. May go back to that after allā¦ 
Combining the element tree and the old way is what I am describing. Keeping the element tree is good, just give the eye/icon to the elements that donāt load when the app is being previewed.
My thoughts would be to just make the eye a different color if it is not visible. It is really hard to see the visible and non visible eye on my element tree. However I do love love love the new way of organizing.
We just pushed a pretty big change, where you can pick to only show hideable entries, in which case itās pretty close to what it was before.
Thanks Emmanuel. From the forum it seems that people are using the element tree is different ways depending on the way they build pages and this seems great.
I am a bit lost about the sorting in each mode though. What is the latest status ?
By position (we havenāt made change to the responsive view yet).
ok.
I would just like to voice that in the case described with screenshot above (and maybe for other single page apps) this makes it very hard to read the page structure.
When the number of elements gets significant and many of them are on the same high it would be very convenient to have control on the order on which the elements are displayed.
I have ~12 pages in a single page app using states to show/hide. If this is a bad design, please let me know how to adjust.
How is it worse than before?
It looks like this new sorting messed up my app?!
I use many different groups on a dashboard page and I have an invisible group that doesnāt show up when I send to the back but if I bring to the front then the menu isnāt clickable (even itās hidden)
It canāt change the app object. So if you see something strange, please file a bug report.
Well before the alphabetical sorting allowed to define the logical components of the page through prefix. Which was really really great.
Actually I used prefixes that would match the page states triggering the hidden/visible status. This way it was really easy to play with the navigation.
Iād be happy to show it via webex if it helps.
@emmanuel what if we could have another dropdown box below the element tree that has the old feature. If thatās not to much to ask or if itās not suggested already.
For the element tree, I get that the position on the page makes sense, but when āonly show hideableā is checked, I would prefer alphanumerical sorting.
At what point does everybodyās opinion start to detract from progress that could be made on other features?
Agree
When youāre only showing hidden elements, itās pretty much the same as before, so I donāt see a need to add something else.
Is it maybe possible to drag the element tree wider for element names thatās to long to show?
Please note that the view with hidden elements only used to be hierarchical and is now flat.
I really dislike the new element tree. Iām using a simple page as example:
Before I had this 5 āhidden elementsā on the left. Itās easy to see the text and the eye icon when its on.
I could use the top white menu āelementā to view the entire list, or search.
Thereās some nice UI to try to get inspirations (apps like Atom, Brackets, Macaw, LightTable are nice examples).
Maybe the eye icon (when off) can show just when hovering the element line (makes the list less cluttered ).
I think if thereās a search bar on it, and it will filter as we type itād help a lot, but thereās the main issue about it: I canāt understand the need to this element tree and the top āelementā white menu, they both seems to do the same thing.
