Hi Doug, This approach is pretty cool, really thank you so much Doug. :)
--- In [email protected], "dougmccune" <[EMAIL PROTECTED]> wrote: > > I do this all the time, it's actually how I prefer to code most of my > stuff. Once you set up your project it doesn't require any additional > work to test code. > > Basically I have two projects, one is a Flex Library Project that has > all my AS-only classes. This gets compiled into a SWC when the project > gets built. Second, I have a Flex Project that I use to house my MXML > testing files. The Flex Project references the Library Project, so it > has access to all the classes in the Library Project. I have my > Library Project set up to automatically build the SWC when I save any > of the files, so I know the SWC file is always current. > > So if I make a change in my Library Project to the AS classes, the SWC > gets rebuilt. Then I just have to rebuild the MXML testing file and > run it to see the changes. The process ends up being: 1. make changes > to AS class, 2. rebuild MXML project, 3. run or debug MXML app. > > Step 2 in there happens automatically if I make any changes to the > MXML files, which I usually end up doing anyway. So really I change > the AS class, save, change the MXML class, hit the "Debug" button, and > I launch the debugging version of the newest of everything. > > Does that make sense? I think the workflow works well. > > Doug > > > --- In [email protected], "Chua Chee Seng" <quai83@> > wrote: > > > > Hi Doug, > > > > This help, thanks a lot. Just that I now face the problem of having > > to go through few steps to test run code changes: to package it in > > different component project, and then reference the resulting swc in > > another project, then only I can test run it. Do you have better > > solution? > > > > Thank you very much > > > > Regards, > > Chee Seng > > > > --- In [email protected], Doug McCune <dmccune@> wrote: > > > > > > If you package it as a SWC and then add that compiled SWC to a Flex > > > project then it will show up in the Design View just like the normal > > > button. So create a new Flex Library Project, add you Button.as file, > > > specify the AS classes to include (by changing the properties of the > > > library project), and then build the project. That will make a .SWC > > file > > > in the bin directory. Now you can reference this SWC in other Flex > > Projects. > > > > > > Doug > > > > > > > > > Chua Chee Seng wrote: > > > > > > > > Hi, > > > > > > > > I am trying to go through the Button source code to examine how > it is > > > > written, I have copied the original Button.as into a new > package, and > > > > I rename the package. I copy the styles folder, Version.as and > > > > Button.png into my relative folder too. It compiles, and exist > in the > > > > Component panel of the builder. However, when I drag it into the UI > > > > area and drog, nothing is render except a small rectangle. I can > click > > > > on it and specified the width and height in the properties panel. > > > > After specifying the width and height, it is showing a empty > > > > transparent rectangle in the design view, clicking on it can see the > > > > border, but can see the button image. It works fine when I run the > > > > application. May I know how does the Flex builder render the custom > > > > component when I drag and drop from the component window? Am I > > > > missing something there? > > > > > > > > Thanks in advance for any help. > > > > > > > > Regards, > > > > Chee Seng > > > > > > > > > > > > > >
