Skip to content

280: Rename Exportable Collections/Exportable Objects/Exportable Roots to use Root #544

@tngreene

Description

@tngreene

Here is a tongue twister I had with someone:

When using the exporter to try and export an OBJ from an Exportable Object I found that a mesh object got an error and it and it's materials wouldn't be exported. I made sure that my Collection wasn't an Exportable Collection containing an Exportable Object, but that wasn't the case. That mesh object is buggy. The OBJ is supposed to be exported to objects/windows.obj

Too many uses of the word exportable!!!

I propose, and I don't see why I didn't think of this, to rename the UI and concepts as such

Current Name New Name ?
Exportable Roots Roots Everything else is a "Non-Root"
Exportable Collection Root Collection Implies this collection is the start of something
Non-Exportable Collection Organizing Collection "Folder Collection" doesn't explicitly say the mental model for it's use
Exportable Object Root Object Anyone who used 2.79 will get it, deals with Objects being exported or not based on validness, errors, or visibility

A non-root object is simply an object, or at worst a "Regular" object

To redo the example from above

When using the exporter to try and export an OBJ from a Root Object I found that a mesh object got an error and it and it's materials wouldn't be exported. I made that my Collection was only an Organizing Collection containing the Root Object, but that wasn't the case. That mesh object is buggy. The OBJ is supposed to be exported to objects/windows.obj.

Now the issues related to where the exporter starts, issues with nesting, and where to change OBJ settings are clearly highlighted - anywhere the word Root is used.

Related to #420

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions