1 Reply Latest reply on Aug 4, 2008 3:40 PM by Jed Schneider

    I must be really stoooopid

    ProjectedSurplus Level 1
      OK, so one of the great things about flex (it seems) is the community of developers and the components they "contribute" like flexlib . What I don't understand despite overheating googles search computers is how to implement them.

      Specifically Ted Patrick's blog http://www.onflex.org/ted/2008/03/fxb3-tip-that-libs-folder.php suggests its as easy as dropping swc s into the lib folder but as I said at the outset, I must be really stupid cuz after I dropped flexlib.swc into my flex project lib then the Custom Components available for drag and drop into design view expands and I can (say) drag in an address form. However, I can't figure out what to do then!

      There don't seem to be any places I can edit/access the text inputs etc in the component nor any AS/mxml files nor . . .

      Alternatively, if I import say the Fisheye http://www.quietlyscheming.com/blog/components/fisheye-component/ via Import >>> Existing Projects into Workspace the process seems to work fine but then throws

      "unable to open 'C:\dev\qs\web\config\WEB-INF\flex\services-config.xml'

      and lastly, if I import this calculator component: http://flexglossary.net/lffs/lffs-10-calculator-continued/calculator-code-reviewed/srcview / then I don't see how to use it in another "project" (I've tried adding via the project references page but it doesn't seem to help)

      I realize this is a variety of issues but all probably relate to my gross lack of understanding of a concept or two so both answers or directions to a learning resource would be appreciated.

      Thanks in advance.
        • 1. Re: I must be really stoooopid
          Jed Schneider
          in order to use the custom components once they are available in your src directory, you must import them into your application to use the custom components. in your application tag you will see a namespace for the mx: components that references an adobe url. you can then add a new name space that identifies the new components, for example xmlns:sp = "com.superPanel"

          then once you import that name space when you type "<sp:" to add a new mxml tag, the intelli-type should pick up all the components available in that package.

          Maybe you already knew this but if not, it should get you started down the right path.