Anatomy of a Flexbuilder Project

[arkum]

Hi,

Started playing with Flexbuilder 3 recently and having looked at the project stucture I am a little confused.

I have 4 folders - bin-debug, html-template, libs and src.

It would seem logical to me that any classes I import or create from within the project would be placed in src and wouldn't need to be copied over to bin-debug when I publish, but it seems that classes I import are placed in bin-debug, while classes I create are placed in src.

Why does flexbuilder place class files in bin-debug (and also bin-release) when they have already been compiled and serve no further purpose. Surely bin-debug / bin-release are intended as ready to deploy?

thanks.

[dr_zeus]

There's a project setting called "Copy non-embedded files to folder". Uncheck that option and your classes won't be copied.

[CyanBlue]

What's the purpose of that setting, just out of curiosity???

[Ping]

You can found detailed explaination in Adobe's Online Help. Check the link below, I've marked the topic for you.
Flex Project Setting

[dr_zeus]

Basically, it's for copying images and other assets that are loaded at runtime to the output folder.

I dig the feature, but not the way it's been implemented in Flex Builder. It's very rare that I want every file copied. In Visual Studio, you actually have the ability to configure the copy settings for each individual file. While it might be a pain if you have many files to copy, I think it's better than also getting a bunch of files you don't want.

[CyanBlue]

That sure sounds like a good feature, but why would that copy the class files??? (I know I should have asked this in the first place... )

[dr_zeus]

Because it is poorly implemented. I almost always turn this feature off because it's not very useful when it copies files I don't need.

[CyanBlue]

Makes much sense...