While discussing allowing the variant names be manually overridden, it was suggested to use UUIDs as the default variant name.
While discussing allowing the variant names be manually overridden, it was suggested to use UUIDs as the default variant name.
Comments
Comment #1
damienmckennaRather than relying on another module, if UUIDs are to be used by CTools it have a UUID generator built in?
Comment #2
merlinofchaos commentedUUID generators are relatively easy, and the UUID module does a lot more than just provide a generator and some of that may not be desired so I can see putting a generic uuid generator in CTools for this purpose.
Comment #3
merlinofchaos commentedTo refer to the original conversation, note that using a name based upon the manually entered name will not solve the problem of name collisions during export. The only two things that will solve that would be:
1) Uniquely naming handlers in the UI. I think this would ultimately be bad UX because there's very little real basis to name these things on and it will confuse and annoy people.
2) Any derived name is ultimately going to end up with a counter, and a counter will foil exports which end up deriving the same way that the one in the database derived.