I know the order of traits for a piece matters, that a prototype has to come before functions that use that prototype, for example. But does the order of prototypes in the Module Editor matter? If Prototype B uses Prototype A as one of its traits, does Prototype A have to be listed in the Editor before Prototype B? Or will it work just as well regardless of the order the prototypes are listed in the editor?
I’ve got a lot of prototypes in a module, and I’m thinking about putting them in alphabetical order just so I can find them easier as I need to work on them in the future. But I don’t want to mess up any dependencies by doing so.
No, Prototype order makes no difference at all. Feel free to re-arrange them as required. Some designers create dummy protoypes with names to make Dividers and Headers to break them up and make them easier to find. Prototypes that are never used have no affect at all on a module.
Correct me if I’m wrong, Brent, but wouldn’t prototype order matter if, for example, a Restrict Commands trait in Prototype A needs to affect a trait in Prototype B? Not that that sounds like a good design…
The order that you include prototypes in a trait matters, based on the standard rules of ordering of the traits generated by those prototypes.
The order which you have the prototypes recorded in the module (which I understood the original question to be) does not matter.
Oh right, I completely misread the original question. Oops! Nothing to see here, move along, move along…