StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I would check out these pages in the official documentation:</p> <p><a href="http://livedocs.adobe.com/flex/3/html/apparch_01.html" rel="nofollow noreferrer">Flex Application Structure</a>, <a href="http://livedocs.adobe.com/flex/3/html/building_overview_1.html" rel="nofollow noreferrer">Building Overview</a>, and <a href="http://livedocs.adobe.com/flex/3/html/help.html?content=modular_5.html" rel="nofollow noreferrer">Application Deployment</a></p> <p>The short, off-the-top-of-my-head answer would be: </p> <ul> <li><em>html-template</em> is aptly named, and stores the HTML "wrapper" or "container" for the actual Flash object. If you need to do "standard" HTML/Javascript design/interactions around your Flash/Flex application, you modify <em>index.template.html</em> inside <em>html-template</em> and add external CSS, JS, etc, to that folder. </li> <li><em>bin-debug</em> is the version of your app compiled for debugging purposes. So it takes everything in <em>html-template</em> and copies it to <em>bin-debug</em> while compiling all the SWFs that comprise your application.</li> <li><em>bin-release</em> is very similar to <em>bin-debug</em> but is populated through the Flex Builder release process and provides additional options like "view source". I have actually just copied straight from <em>bin-debug</em> to a demo server without trouble before, but I'm sure that's a bad idea for actual deployments.</li> </ul> <p>The only other thing I would add is that Flex Builder tries to create the debug builds as quickly as possible, and so it only copies or compiles the files it thinks have changed...and sometimes it misses some. A Project->Clean... will force all the files to be re-copied/compiled into <em>bin-debug</em>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload