Once again, NO explode has occurred upon opening !
The "magic" was done when the file was created via "Save As Component".
The "magic" will be undone when the file is inserted as a component.
This is not true.
The former definition's entities collection has been saved as the new component files's model entities collection. The former component's attribute dictionaries collection, has been saved as the new component file's model attribute dictionaries collection. The former definition's origin has been saved as the new component's model origin.
Nothing is gone.
To insist that exploding is occurring, just creates a mental block, that prevents you from understanding this concept. Forget the word and concept of "explode" with regard to this issue. It is bad wording that the original author of the tutorial, thought would somehow make people understand.
This is not any different than dealing with attributes in a normal model. A plugin has always been needed to allow end users to view or edit them.
Attributes and their Dictionaries (as well as collections of the latter,) were not designed as end user objects. They were always meant as programmatic data objects, hidden "behind the curtain" but enabling plugins to do nifty visible things.
So nothing more nor less has been hidden.
In fact, "Dynamic Components" is an extension, which can be switched on and off, that provides a webdialog to view only specially named attribute dictionaries, if it exist, attached to component definitions and instances.
You will be surprised at the number of other attribute dictionaries attached to the model or other subordinate model constructs "under the hood." Users are not normally supposed to know about them, because they are plugin data, and if altered, can break plugin functionality. Some of it is very fundamental, such as the GeoReference information.
Correct. This means that ANY model skp file can be inserted as a component, into another model.
This is exactly what happens when you use the Component Browser and grab someone else's building model from the 3D Warehouse, and insert it into your model. The model skp from 3DW, is made into a component definition, and an instance of it is inserted where you point to have it inserted.
Agreed. They are working on overhauling all the docs as we speak.