Separate projects is my preference and seems logical to me but is not
really endorsed/recommended by Adobe which is disappointing. The
compiler arguments you mentioned can be used to optimize but
FlexBuilder is flaky at best using that approach. See
https://bugs.adobe.com/jira/browse/FB-12220 for
We do exactly this. Each module is a project. This allows each
developer to create \ compile \ run a project without reference to
another dev. We load each module in the app (at runtime) on demand
using the moduleLoader. (Watch for the intermittent loader bug and
knock on popup bug !)
The down sid
I've not tried that approach yet and admittedly don't quite understand
how it supports lazy loading. Do you just specify the module lib's SWC
as the url for ModuleLoaders that live in the main app?
Regardless, I feel like separate projects for each module should
absolutely be a supported workflow.
We create all of our module projects under a modules directory, each
one having their own sub directory. Each project has its own bin-debug
directory created by FB. We then use an ant script in FB to iterate
through all of the module\**\debug-bin directories and copy the swfs
to the dev's local jbo
On Friday 11 Apr 2008, ben.clinkinbeard wrote:
> https://bugs.adobe.com/jira/browse/FB-12220 for example. That thread
> also talks a bit about their recommended approach which, again, I am
> not crazy about.
You mean "a "module project" would be largely a usability feature to make it
more obvious
Thanks Bob. In dev mode (Flexbuilder only) is there a convenient way
to reference the module SWFs by a relative URL, or does one have to
copy them into the loader app's output directory?
On Fri, Apr 11, 2008 at 7:42 AM, bobpardoe1959
<[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> We do exactly this. Eac
We used Adobe's endorsed/recommended way.
Got a lot of problems...
1- passing objects between modules.
2 - some developers bad pratices, like create a new instance of another
module instead use ModuleLoader.
3 - bad control of what code is from what module.
And others diary problems.
Now I compi
Forget to mention,
This release is done with flex-mojos http://flex-mojos.blogspot.com/
VELO
On Fri, Apr 11, 2008 at 4:47 PM, VELO <[EMAIL PROTECTED]> wrote:
> We used Adobe's endorsed/recommended way.
>
> Got a lot of problems...
> 1- passing objects between modules.
> 2 - some developers bad
Thanks, that information is helpful.
However, I'm trying to avoid running a local server, since the
back-end is .NET and I'm on a Mac.
I guess I could copy the modules to the loading app's output
directory, and maybe set up an Eclipse builder to do this
transparently.
Or perhaps I could point the
9 matches
Mail list logo
