So I’d like to help design and develop (just getting aquainted to the codebase, so my design skills are a lot better than my development ones currently) this new editor.
In my mind, it could not only serve the purpose of an improved overview of the blend file, but also as a location to visually see elements of the file such as objects, materials etc. like you can in the asset browser. I asked @julianeisel in another topic regarding the asset browser, and if that editor could be used for this purpose. He didn’t get back to me, but it seemed the appropriate place for that management. Albeit in another mode. One view for assets from other files / libraries, one for assets in the current file, and one for all of the elements in the current file (what do you think this view mode should be called?).
So what features would this mode provide?
Here are some features I could see it handling (so as to help with the orphaned data build up):
- Lists / makes thumbnails (where possible) for all elements in the current file
- Allows for filtering / sorting of those assets based on type / other data
- Mark elements as assets and those then get added to the asset views for further management (such as addition of tags, categories etc.)
- Create / delete / rename elements
- See data that is orphaned that could be deleted
- See how all of the data is connected to each other, through references to other elements, or an actual node based view for better visibility on how the file is laid out
I think this viewer would solve three issues.
- It would make all elements first class citizens, and not subservient to objects. So you could create materials here and not have them have to be currently associated with an object.
- It would also make it much easier to see what’s in your current file and manage that by allowing for not only visual representations of them through thumbnails, but also by providing filters / sorting. This could be extremely useful for complex files that have complicated hierarchies and lots of elements
- It would solve the visibility of orphaned data, along with possible prompts on close about the fact that there is orphaned data. It would also need refinement for what is actually orphaned data. A material that isn’t currently assigned to an object shouldn’t be considered an orphan. It would be a departure from the object centric orientation of blender and into a more balanced and safe creation mode.
What do y’all think?