|
Title: Status of Multi vs Single core demos and utils Post by: justSteve on March 17, 2008, 07:49:46 Looking for a quick overview of where things stand with the multi-core version.
How do we go about using the startupmanager utility. Is a port to the multi-core package required / already underway? The version of the Best Practices & overview docs aren't yet referencing the Multiton...will these documents update or will an independent paper be published? And a quick question about appropriate usage of Multiton verion... Effectively all the development I'm involved with will make use of nested and or sibling-level PureMVC objects - e.g. a top-level menu (based on PureMVC) can cause change of view stack to bring up a slideshow also based on PureMVC. My life is easier by just focusing on the Multi-Core version, right? Or are there other considerations to take into account? From the client-side point of view, what's the functional difference? thx --steve... Title: Re: Status of Multi vs Single core demos and utils Post by: puremvc on March 18, 2008, 11:35:22 Sorry I didn't get back to you on this one yet, Steve.
Yes, it sounds like you need to focus on MultiCore for your app. Although people have been able to make Modules and loaded SWFs work with the Standard Version, this is the Meaning of Life for MultiCore; its raison d'etre. In the Standard Version the predominant approach has been to do a lot of registration/removal of actors when a Module/SWF is loaded. The problem with this is since all the actors are swimming in the same pool, so to speak, you have namespace issues. For instance if one widget registers a Notification to a constant evaluating to 'ButtonClicked', then no other loaded apps can use that string as a Notification constant. Playing with ApplicationDomain can help this, but as you can see, you're jumping through hoops. Trying to fit a square peg in a round hole. So MultiCore just has a map of instances for each singleton rather than one. The instances are retrieved by key, exactly like you retrieve Mediators or Proxies, so it is a familiar idiom. Read here: http://forums.puremvc.org/index.php?topic=313.0 about the access of the facade in the constructor which is the primary difference in practice between the two versions of the framework for AS3. -=Cliff> Title: Re: Status of Multi vs Single core demos and utils Post by: StephenDurr on April 10, 2008, 06:51:36 The version of the Best Practices & overview docs aren't yet referencing the Multiton...will these documents update or will an independent paper be published?Any update on this? The Modularity demo app is nice but it would also be very helpful to have a Multicore section in the Best Practices doc. Thx! Title: Re: Status of Multi vs Single core demos and utils Post by: puremvc on April 11, 2008, 04:16:10 More than likely it will be added as an extra chapter at the end, but I haven't ruled out having a second document. The to-do list is becoming quite long, but getting MultiCore fully supported is quite high on the list.
-=Cliff> |