Announcement

Collapse
No announcement yet.

module:features Does the order of features matter?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    module:features Does the order of features matter?

    By convention I've always added the main feature first and the vis_feature second, but does it really matter? I don't find anything on the subject in the Module API Reference Guide.

    Example:
    Code:
    <MvASSIGN NAME = "l.module:features" VALUE = "util,vis_util,data_store,component,system">
    The only reason I ask is that I'm scrapping my old development system and building a new one.
    Ray Yates
    "If I have seen further, it is by standing on the shoulders of giants."
    --- Sir Isaac Newton

    #2
    Re: module:features Does the order of features matter?

    In playing around with this, I have noticed no effect whatsoever to feature order.

    Merchant seems to have it's own internal heirarchy for features.
    Gordon Currie
    Phosphor Media - "Your Success is our Business"

    Improve Your Customer Service | Get MORE Customers | Edit Any Document Easily | Free Modules | Follow Us on Facebook
    phosphormedia.com

    Comment


      #3
      Re: module:features Does the order of features matter?

      I checked with Dev, they said no it doesn't matter.
      Thanks,

      Rick Wilson
      CEO
      Miva, Inc.
      [email protected]
      https://www.miva.com

      Comment


        #4
        Re: module:features Does the order of features matter?

        Thanks guys
        Ray Yates
        "If I have seen further, it is by standing on the shoulders of giants."
        --- Sir Isaac Newton

        Comment

        Working...
        X