[flexcoders] Re: Interfaces not working the way I understand anyway

2009-01-16 Thread mmormando
Not necessarily, but then the app has been a bit.different from day
one. In it most of the modules are discreet bits of functionality
where the Main App simply organizes and hosts the other modules,
which may in turn host other modules that the main app knows
absolutely nothing about. Except now it seems pretty clear that if the
main module REALLY knows nothing about any discreet piece, that piece
might go walkabout at any time.
Important safety tipwe live and learn.
thx for all the help everyone!
Mike


--- In flexcoders@yahoogroups.com, Josh McDonald dzn...@... wrote:

 Just the interfaces, but your modules should be using interfaces defined
 (and used) in the main app anyway, no?
 
 -Josh
 



[flexcoders] Re: Interfaces not working the way I understand anyway

2009-01-15 Thread mmormando
--- In flexcoders@yahoogroups.com, Alex Harui aha...@... wrote:

 Sounds like an applicationDomain topology problem.  See the  modules
presentation on my blog.  Make sure the interface is linked into the
main app.


That got it!
Thanks!!
(maybe modules should be marked experimental or something)



[flexcoders] Re: Interfaces not working the way I understand anyway

2009-01-15 Thread mmormando
--- In flexcoders@yahoogroups.com, mmormando m...@... wrote:

 --- In flexcoders@yahoogroups.com, Alex Harui aharui@ wrote:
 
  Sounds like an applicationDomain topology problem.  See the  modules
 presentation on my blog.  Make sure the interface is linked into the
 main app.
 
 
 That got it!
 Thanks!!
 (maybe modules should be marked experimental or something)



After seeing this, does it more or less mean that I need to statically
link a copy of every stinking module I've got into my main module in
order to be sure I won't run afoul of this problem every time I turn
around?
Not exactly sounding like an optimal solution.



Re: [flexcoders] Re: Interfaces not working the way I understand anyway

2009-01-15 Thread Josh McDonald
Just the interfaces, but your modules should be using interfaces defined
(and used) in the main app anyway, no?

-Josh

2009/1/16 mmormando m...@mormando.com

 --- In flexcoders@yahoogroups.com, mmormando m...@... wrote:
 
  --- In flexcoders@yahoogroups.com, Alex Harui aharui@ wrote:
  
   Sounds like an applicationDomain topology problem.  See the  modules
  presentation on my blog.  Make sure the interface is linked into the
  main app.
 
 
  That got it!
  Thanks!!
  (maybe modules should be marked experimental or something)
 


 After seeing this, does it more or less mean that I need to statically
 link a copy of every stinking module I've got into my main module in
 order to be sure I won't run afoul of this problem every time I turn
 around?
 Not exactly sounding like an optimal solution.


 

 --
 Flexcoders Mailing List
 FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
 Alternative FAQ location:
 https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847
 Search Archives:
 http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups
 Links






-- 
Therefore, send not to know For whom the bell tolls. It tolls for thee.

Like the cut of my jib? Check out my Flex blog!

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: j...@gfunk007.com
:: http://flex.joshmcdonald.info/
:: http://twitter.com/sophistifunk