<more...>

I believe that flex builder installs eclipse 3.1 hence the question.

So to use flex all you need is flex builder the full version. Eclipse is not
required, rather Adobe took eclipse 3.1 and modified it for flex
builder==one in the same.

Hope I’m making sense, it's late here :)

jason



-----Message d'origine-----
De : [email protected] [mailto:[EMAIL PROTECTED] la
part de Jason Hawryluk
Envoyé : mercredi 10 janvier 2007 21:03
À : [email protected]
Objet : RE: [flexcoders] Re: IFlexModule


There was an old version of the modules framework from the original creator
(it was just a thought) it's probably not the problem.

Ok so your pc.. On another post here i asked to take a look to make sure
that the module framework is indeed where it is supposed to be.

The fact you where able to create a new app with no module reference is a
direction. I'm not sure where apache comes into play here.

you should not have both eclipse and flex builder unless your using eclipse
for something else. Flex builder uses eclipse so there could be an
incompatibility between the version flex builder is installing and the
version 3.2.

If you wish to use flex with eclipse 3.2 you should install the plug-in not
flex builder.

Does this make sense or am i wrong in assuming this as your case. Do you
have both eclipse 3.2 and flex builder 2.01 installed?

If so; this is most likely the root of the problem. If not.. well we'll keep
witling it down.

again just thinking out loud here..

jason

-----Message d'origine-----
De : [email protected] [mailto:[EMAIL PROTECTED] la
part de Greg Morphis
Envoyé : mercredi 10 janvier 2007 20:55
À : [email protected]
Objet : Re: [flexcoders] Re: IFlexModule

Thanks Jason for the help.
I'm on a PC..
I was able to create a new project, add an HBox and Label and run it
as a Flex Application.
What do you mean by "older version"? Older version of what?
I downloaded the Flex Builder 2.0.1 install file and Eclipse 3.2 on
Apache Tomcat server.

On 1/10/07, Jason Hawryluk <[EMAIL PROTECTED]> wrote:
> Judging from the error I would think that perhaps your using an older
> version or the modules or your existing project before the update was
> referencing the older modules framework. If this is the case there may
have
> been changes between the older version and the release version that are
> causing you grief. The fact that your project is failing on IFlexModule
> leads me to this.
>
> Again excuse if off the mark.
>
> Jason
>
>
>
> -----Message d'origine-----
> De : [email protected] [mailto:[EMAIL PROTECTED] la
> part de Greg Morphis
> Envoyé : mercredi 10 janvier 2007 19:20
> À : [email protected]
> Objet : Re: [flexcoders] Re: IFlexModule
>
>
> Severity and Description Path Resource Location Creation Time Id
> 1023: Incompatible override. aopscheduler line 11 1168453153048 2221
> 1120: Access of undefined property IFlexModule. aopscheduler line
> 22 1168453153048 2222
> 1144: Interface method create in namespace mx.core:IFlexModuleFactory
> is implemented with an incompatible signature in class
> _index_mx_managers_SystemManager. aopscheduler line
> 7 1168453153063 2224
> 1172: Definition mx.binding:RepeaterComponentWatcher could not be
> found. aopscheduler line 16 1168453155423 2226
> 1172: Definition mx.core:IFlexModule could not be
> found. aopscheduler line 6 1168453153063 2225
> 1180: Call to a possibly undefined method
> IFlexModule. aopscheduler line 24 1168453153063 2223
>
> On 1/10/07, Greg Morphis <[EMAIL PROTECTED]> wrote:
> > Okay I'm fed up....
> > I removed Flex Builder 2 entirely, the newly installed 2.0.1 and the
> > older installed 2, and I removed FDS2 also... I just reinstalled
> > Eclipse (unzipped the WTP zip file to the C: drive) and just ran the
> > FB2.0.1 installer. I chose default options for both questions.
> > Before going any further I wanted to test it.. so I started Eclipse
> > and guess what? There's the error!!!!!!!!!!!!!!
> >
> > On 1/10/07, Greg Morphis <[EMAIL PROTECTED]> wrote:
> > > It screwed up my old install of FB2.0/Eclipse3.1... I decided to go
> > > back to using that temporarily, so I loaded up Eclipse3.1, the
> > > Navigator view was empty!
> > > I right clicked, chose Import and chose my workspace. My projects were
> > > present in the dialog and were all checked. I hit finish and was told
> > > the projects existed.. If they did, I couldn't see them in the
> > > Navigator view...
> > > This sucks Adobe.. sucks....
> > >
> > > On 1/10/07, Tom Sobut <[EMAIL PROTECTED]> wrote:
> > > > I'm having the same problem...
> > > >
> > > > In the 2.0.1 install instructions for the Mac, Adobe instructs that
> it's necessary to "refresh
> > > > the workspace by using the -clean option". I followed the links in
the
> instructions and did
> > > > a refresh in a terminal session by entering:
> > > >
> > > > /Applications/eclipse/eclipse -clean &
> > > >
> > > > That did seem to run. Problem still exists.
> > > >
> > > > I can compile without errors back in my 2.0 beta copy which I kept
> (just in case).
> > > >
> > > > Something's wrong inside the black box.
> > > >
> > > > Hope someone can help here.
> > > >
> > > > --- In [email protected], "Greg Morphis" <[EMAIL PROTECTED]>
> wrote:
> > > > >
> > > > > I downloaded Eclipse 3.2 (the all in one wtp package), Flex 2.0.1.
I
> > > > > did a clean install in new folders. Now when I open Eclipse and
open
> a
> > > > > project I'm getting some IFlexModule error.. I did a google search
> and
> > > > > that didnt help much. Has anyone seen this error and know how to
fix
> > > > > it? It's getting on my nerves!
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Flexcoders Mailing List
> > > > FAQ:
http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> > > > Search Archives:
> http://www.mail-archive.com/flexcoders%40yahoogroups.com
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
>
>
>
>
>
>
> --
> Flexcoders Mailing List
> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
> Yahoo! Groups Links
>
>
>
>






Reply via email to