Question about lazy instantiation, another about child (lazy) contexts about typhoon

[jasperblues]

Hi Bruce,

You're asking in the correct place, because I haven't set up a mailing list yet. . . (I think its about time that I did).

1. All objects in Typhoon are instantiated in a lazy fashion - the object is not built until its asked for. For an object that has a heavy instantiation there's currently no way to mark it for eager instantiation, however you could easily work around this by fetching when you set up the container.

Regarding singleton vs prototype: A prototype is a new instance of an object, while a singleton is a shared instance. You should generally use prototype (especially for mobile) because these will be cleaned up (i.e. dealloc'd) when no longer referenced. . . However, you sometimes need a true shared instance - e.g. RootViewController or something that holds shared state.

1. Its possible to group components using separate files (for XML style) or categories (for block-style) . . however its not currently possible to set up child/parent containers.

If you like I can open an issue for either of the above features - eager instantiation and/or child contexts.

Jasper Blues
Landline: +63.2.826.2489
Skype: jasperblues
LinkedIn Twitter

On Jul 5, 2013, at 11:39 PM, Bruce Flowers [email protected] wrote:

I'm just asking here since I hadn't seen another forum, but please let me know if I'm not in the right place:

Does Typhoon have a provision for lazy instantiation for objects? Is the "prototype" scope for this purpose? Could you explain a little more about this?

Is there any way to initialize "child" contexts, which would be aware of the main one? If so, is it possible to do deferred initialization of child contexts?

Thanks,
Bruce

—
Reply to this email directly or view it on GitHub.

[jasperblues]

Pull request #29 adds support for lazy vs eager init. . .