|
Cliff,
Along these lines, if I were to create a reusable component swc with multicore, where would be the appropriate place to put the public API methods?
As an example, let's say for instance that I want to create a reusable slideshow component that should expose methods like, back(), next(), load(), etc... I don't want the user to have to access these methods through the "image" view. This seems cumbersome to me to expect a user to import a view class and call a method like next() exposed in a package like com.useflexmore.view.image.
I'm probably missing something obvious and I apologize if this is a silly question, but just placing a public method on my Slideshow class (Facade) called "next" which would then in turn communicate with a command seems inappropriate to me somehow.
I'm interested in the best approach to creating reusable Flex components with PureMVC that expose a public API which still follows the design model. All the examples I've looked at so far tend to focus on implementing PureMVC in a complete application.
I'm coming from a few years of Cairngorm experience and am finally getting around to trying out PureMVC on a project.
Best regards,
Justin Winter
useflashmore.com
|
Show Posts
