Shawn,
I was away for a while and am trying to catch up. What are the issues here? I posted a way to do popups in modules on my blog (blogs.adobe.com/aharui). Are you trying to access internal components in a module from outside the module? This is possible, but you might want to consider a better design where you abstract the internals in some way, either by events or if you really need to, some sort of getElementByID interface. Note that you may be running into "shared code" issues also discussed in my blog. -Alex ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of shawn.gibson Sent: Sunday, August 05, 2007 6:22 PM To: [email protected] Subject: [flexcomponents] Re: how to access IDs in Module with ModuleLoader? Well, I've come a long way on this after some document research. This should actually load, if slowly, since I removed a faulty router: http://mygallerysite.net/interfaceexample/bin/Main.html <http://mygallerysite.net/interfaceexample/bin/Main.html> The "temporary" xml in the MenuBar loads a HOME and a GALLERY module. Basically, I'm beginning to get the gist of using an Interface, based on the docs, as you will probably notice from the "Adjuster ID" and the "Background Color" code:) However, I'm running into a few really nasty issues: 1) Loading the HOME module first run through (from the MenuBar), it's fine; however, after loading in the Galleries Module (people will often want to go back home, right?) I get some strange instantiation error. I am trying to move the Styles DataGrid thing in the Accordion over to e4x/HTTPService, so I'm hoping it will go away, but asking if it indeed will, might save me some grief. 2) I still can't for the life of me get any components into my project and reference anything that is outside the component. I can go App to Module, and from Module to Module, but I can't use any kind of component (i.e., an ApplicationControlBar component as opposed to inline code within the app/Module). It leads to some very ugly code, and a lot of stuff I'm sure that will cause my project to bulk out fast. 3) I can't for the life of me figure out how to set up the TitleWindow/progressWindow within the Modules. I can get it working in the main app, loading modules, but as soon as I try to put in in the interface and use it as a way of showing the progress of 'myimage' in the M_home module (or any kind of communication, in fact itwon't even compile) it blows up. This is critical to me because I'm building this from the core level-up: UI feedback is critical for showing users what's going on, since there's so much on-the-fly data loading. I want them to know everything about all loading, i.e., images, services, modules, etc. However, all that said, I'm miles ahead of where I was last week, so I'm very happy. I keep thinking I need to learn MVC/Cairngorm etc. but right now, it's much more important that I figure out the basics. Even the important stuff in the app (the real mechanism for thumbnails, a blog, the tree for loading galleries, etc., much of which I do have worked out elsewhere with Tracy Spratt's help) has taken a back seat right now so that I can ensure I'm building my project properly (if without any design patterns or other such advanced ideas as MVC/Cairngorm). I suspect it will be at least a year before I go there... Any suggestions on the above problems would be much appreciated - VS is Enabled, if indeed you can get into my app with the above link. Otherwise this post is pretty much useless and I apologize for wasting your time...my real server/dev machine setup should be out of the shop/paid for in the next couple of weeks. I can email it if any of you is truly interested and can't grab the code. Just let me know: [EMAIL PROTECTED] <mailto:shawn.gibson%40yahoo.com> or [EMAIL PROTECTED] <mailto:sgibson%40ida.ca> I'd really appreciate a bit of guidance here; I have come far (with a lot of help); but I am, as often happens, now at a standstill. Shawn
