app initialization

[Tyler Wright]

Reflex is coming along and so far it's staying very small (even without many optimizations). Because of its size a lot of Reflex-based apps/games/websites probably won't want a forced loading bar, like all Flex apps have. So do we have an optional loading sequence? Has anyone thought into a system-manager initialization workflow yet?

Tyler

[Jacob Wright]

I know how to do it, but no, I haven't thought about whether we should or not. We definitely should support it, but I'm not sure the workflow to optionally have it or optionally not. Would you use a different Application class depending on if you wanted a preloader or not?

[Tyler Wright]

I know how to do it, but no, I haven't thought about whether we should or not. We definitely should support it, but I'm not sure the workflow to optionally have it or optionally not. Would you use a different Application class depending on if you wanted a preloader or not?

That's sort of what I was thinking. I still have some research to do into how the [Frame] tags work. Maybe there's a single Application class but there's a specialized Preloader class you add to it as a child that will jumpstart the system. I'll look more into it another day, I have too much to finish today, just wanted to get the thread started.

Tyler

[Ben Stucki]

Yeah, I think we should support both workflows, and also take a look at approaches for loading over several frames (load the home screen while other pieces are still streaming in). Ideally we're making a framework which can create apps small enough not to need it.

- Ben

[Tyler Wright]

Yeah, I think we should support both workflows, and also take a look at approaches for loading over several frames (load the home screen while other pieces are still streaming in). Ideally we're making a framework which can create apps small enough not to need it.

If things keep going the way they're going, we'll have applications smaller than Flex pre-loaders. :)