Announcement

Collapse
No announcement yet.

Company / Project Shared Parameters - where & how?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Company / Project Shared Parameters - where & how?

    I'm building up our office template at the moment and have just reached the point of referring to shared parameters.

    To date we've always started projects to look at the "company.txt" then, when new wants (&workarounds) come up that might throw the structure of that file out a bit, we duplicate it and make it a "projectXXX.txt" that sits in the local project library.

    To date, that's not been a problem - save having to redirect the models to the file - and so far we've never lost functionality and have only had the one instant of an orphaned field (thanks to a partner firm not sharing their editted version of the SP.txt file!)
    but it has always struck me how shared parameters can't be harder-fixed to respective models (or vice versa) and was wondering how you lot keep things all in check?
    Tags: None
    #2
    I do not even keep my SP .txt files anymore. I have never found an instance where I could not export and recreate a SP that I needed... or just make a new one. As long as they are in the family and project thats all that matters.
    -Alex Cunningham

    Comment

      #3
      Originally posted by Alex Cunningham View Post
      I do not even keep my SP .txt files anymore. I have never found an instance where I could not export and recreate a SP that I needed... or just make a new one. As long as they are in the family and project thats all that matters.
      Yikes. Why go through the hassle?

      We do the same thing as the OP originally stated. If i build the content, and its getting done for the office library, it goes in our Office Shared Parameters file. Other people will make one-off Project ones, that i will sometimes manually edit to pull the SP's in to the office one, if its worth it. Or, during QC of that content, ill add them in and replace them in the family.
      Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
      @Web | @Twitter | @LinkedIn | @Email

      Comment

        #4
        Originally posted by Twiceroadsfool View Post
        Yikes. Why go through the hassle?.
        Cuz I can't remember what I did 2 days ago... How could I remember what I did months or years ago. :-\ I am sure one day it will bite me in the ass. Ignorance is bliss.
        -Alex Cunningham

        Comment

          #5
          So every time you need a new piece of content to work the same as an old piece of content, you have to go in to a project or the old content, and export a temporary file, just so you can have the same GUID on the same shared parameter? That would be more work than simply saying *this is the correct SP file, forever* and using that.
          Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
          @Web | @Twitter | @LinkedIn | @Email

          Comment

            #6
            Like I said it will prob bite me in the ass someday. However, It's eaiser for me to remember the SP when I am working in the family, rather then searching through a SP master file. Dealing with 1 SP > Dealing with 390 SP.... Its just eaiser for me.
            -Alex Cunningham

            Comment

              #7
              Originally posted by Alex Cunningham View Post
              Like I said it will prob bite me in the ass someday. However, It's eaiser for me to remember the SP when I am working in the family, rather then searching through a SP master file. Dealing with 1 SP > Dealing with 390 SP.... Its just eaiser for me.
              why have 390 sp's? the fun of those is that you can reuse them (make the namings more generic... bolt_length is harder to reuse then length).
              besides that, you could always group your sp's by project or family if you wanted...
              Martijn de Riet
              Professional Revit Consultant | Revit API Developer
              MdR Advies
              Planta1 Revit Online Consulting

              Comment

              Previous template Next

              Related Topics

              Collapse
              Working...
              X