Hey Alex, thanks a lot. I must have been logged off yahoo, didn't
realize you responded. I'm having a blast, this has been a great
weekend for Flex for me:) Having said that, prepare for more
really-trying-but-still-a-wannabe answers to your questions:

>>What are the issues here?  I posted a way to do popups in modules on
my blog (blogs.adobe.com/aharui).

I'll look. As with all your stuff, I'm sure it will solve the problem. 

The problem, if I have half a brain here, is this: I am using an
interface in which I want to define the function that allows me to use
the popup (either in modules for the most part, or in the main app to
show module loading progress, the latter of which actually works) to
load a TitleWindow that, in the end, will show the following: images
as they preload, httpservices as the load (I believe such must be
indeterminate?, or if I can show a visual preload for the XML file
itself, does that work? I'm noticing there's a difference between an
httpservice and the xml it loads, they are different animals...and I
don't know if I need to show a visual preload of the xml, which might
or might not include the data, i.e., in my httpservice there will be
images (thumbnails) or blog entries, or if I am better off showing a
visual clue to the httpservice download itself). But that's WAY down
the line. Do you use Eclipse? You know the screen that shows all the
building tasks? I want something similar for all my dynamically-loaded
data). 

The CURRENT problem (amongst a few, like that damn datagrid I'm trying
to sue in the Home page...grr), is simply that I can't get even simple
Module TitleWindow (progressPopup) communication to work, for example,
if I load an image into an ichild and I want a TitleWindow popup,
there's a definite disconnect. I DO have it working inline in a canvas
(ProgresssBar in the Galleries Module). The fancy stuff above can come
later. I'll be happy getting the image to open a Title Window and show
its dl progress...which happens in the Module - and again I hope your
blog will help me there).

>>>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.

I love the idea of getElementByID (I did OK with DHTML long as I
didn't have to get fancy with JS when I was helping friends), but I
didn't think that was possible in Flex??? I only see a
getElementByName...and as far as an Interface goes, at this point in
time, all I know how to do is the following, in the Interface:

function myFunction(thing:Type):type-of-object-to-return;

..which is thereafter implemented in the Module.
 
>>>Note that you may be running into "shared code" issues also
discussed in my blog.

I'm not sure what you mean by this (I'll look at your blog for it!),
but I can say one thing. In my main app, for example, I have a public
var, and in my interface-driven modules, I have exactly the same var
(as private) and that makes absolutely NO sense to me...in fact, it's
the variable which is used in my currentImage coding (for a breadcrumb
trail, for one).

I've done my very best to make my code clean, if looking at the whole
project via view-source helps:
http://mygallerysite.net/interfaceexample/bin/Main.html

You guys are pushing me in the right direction. I don't want to go off
on a tangent out of ignorance...I feel finally that I am building this
in a manner (i.e., through an Interface) that I have a chance to get
it working according to at least SOME form of a best practice...again,
MVC/Cairngorm/ModelGlue aside; that will be next year, when I have a
clue what I'm doing. I'm willing to build this as Version 1 of
"QuickSilver Gallery Blog" (as a darkroom guy, I love metal, and
silver is the core of any photographic process)...Version 2 can be
more MVC-oriented.

I realize I still have a lot of dependencies/non-reusable code, but
right now, it's good enough to help me learn.

Again, here's the page, VS-Enabled. I want to emphasize this entire
project will be available to the public for free. I believe in that, I
don't want money, I want to make something beautiful for
serious/startup-professional photographers and give it away. 

http://mygallerysite.net/interfaceexample/bin/Main.html

N.B. In the Main MenuBar, only the "Temporary" root works, the rest
are for future use, in essence anyways (and probably will throw an
error right now as I've hashed out the MenuBar handling code for all
but the "Temporary" stuff).

I know this is a lot of writing, and I apologize, nor do I expect
anyone to fix my problems for me, but some guidance would definitely
be much appreciated. Anyone who contributes will have their own
thank-you page, and full credit, of course...and whatever else they
want LOL.

Shawn



Reply via email to