I tried to compile the source files, but there are dependencies on skins and
other components. Maybe start a new project and copy the code and reduce it
down even more. If you still have a problem, post that reduced test case.
On 8/14/10 12:22 PM, "Wally Kolcz" wrote:
[Attachment(s)
Wally, the report.xml is from the AdminPortal module. Like I said before, if
you are using FlashBuilder module projects and use the link-report option, the
module’s link-report overwrites the main app’s link-report.
On 8/14/10 12:22 PM, "Wally Kolcz" wrote:
[Attachment(s) <#TopText> fr
Attached is a link report based on my application which is the main mxml
(index.mxml) which just controls a loader if the loading is successful
and a module (AdminPortal.mxml). The application does not call any
functions on the module and shares no common elements (except a skin,
events, and a
Right now the project is basically 2 mxml pages. I can send the project
to you if you want, and have time, to take a look at it. Just let me
know where to send it.Thanks!
On 8/11/2010 1:24 PM, Alex Harui wrote:
In Flex 4, styles became per-module. That has the greatest chance of
causing pro
In Flex 4, styles became per-module. That has the greatest chance of causing
problems. To figure out exactly how to solve your problem would require
debugging into it.
If you are using a module project in FB, you may not be able to capture the
link-report from the main app. You will have to
I just added the link-report to the compiler and it generated a large
xml document. I only copied the parts that mentioned the module. As far
as I know, they share no common elements at all. I can include the full
report if it means I can finally get an answer to this problem.
If it is a case
Is it possibly some of your components are still using references to
StyleManager (mx) and have not been updated to "styleManager" (spark).
http://www.jonathanrowny.com/journal/migrating-flex-4-stylemanager
2010/8/5 Alex Harui
>
>
> Because I see _AdminPortal_FlexInit and
> _AdminPortal_mx_core_
Because I see _AdminPortal_FlexInit and
_AdminPortal_mx_core_FlexModuleFactory, I'm guessing this is the link-report
for the _AdminPortal module, not the main app.
If you just add -link-report to the compiler options, both the main app and
module will output the link-report to the same file, and s
After looking at the report I see things like (which makes no sense to me):
Re: [flexcoders] Why does Flex 4 hate modules?
Thanks for your help Alex, so while parsing though the link report xml I
SHOULD NOT see any references to the modules? That will help. Also, as
far as the size issue which was suggest to me before, I started to add
minHeight and minWidth to all the pieces and it didnt seem to help at all.
On 8
Well, you don’t have any references in the code you posted, but it could be
somewhere else. Open the link-report, make sure it contains a script for the
main app’s .mxml file and then see if the string name of a module is in the
file. If it is, that’s trouble. The reason for the .mxml file ch
Thank you for your advice. I did that, but I have no idea what i am
looking at. As you can see, I have no references to the modules from the
main application so I still have no idea why its throwing that error.
Where can I find more information on how to read it?
On 8/4/2010 5:16 PM, Alex Haru
Use a link-report to make sure none of the classes in the module are being
liked into the main app. Lots of folks have been doing things like:
Var myModule:MyModule = MyModule(moduleInfo.factory.create()
Instead of using an interface. This actually links MyModule into the main app,
defeating
Just kidding..kinda.. After googling a lot of combination of terms, I
was able to finally get some answers regarding problems that seem to
come up while trying to develop a modular application, but, sadly, I am
not 100% sure what the Adobe person was talking about. The error always
centers aro
14 matches
Mail list logo
