Plugin Developer Name Spaces (2 posts)

  1. unteins
    Posted 11 years ago #

    This is for all of you plugin developers out there who might be using the Custom Meta Data option in 1.2 to store data for your plugins.
    I would like to propose that we voluntarily use prefixes on our data tags so that we can keep our plugins running in their own name spaces and not have conflicts. I plan on prefixing all of my plugin custom meta data with the unt_MetaDataKey so that there shouldn't be a big risk of anyone else having a meta key with the same name.
    I think a 3 letter combination whould be enough. Use your initials or something. I will add a wiki page suggesting the same thing as well.

  2. mortenf
    Posted 11 years ago #

    I think the principle is fine, but I'd suggest using the basename of the plugin file, e.g. "google_hilite" (note dashes turned into underscores), as prefix instead.
    Also, I suggest using this approach for function names as well.

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.