Lately I’ve made heavy use of the HIVE framework (open source), that employs State pattern throughout, and have realized that UIComponents for PureMVC could be made to be state-based fairly easily with the addition of a StateManager. That would be an awesome experiment.
Ayo - did not mention what the misgivings with PureMVC are. Is it with PureMVC, or MVC in general? This methodology has been around a long long time. I hardly do a project without it in one form or another. Three things are inescapable: all applications must have data, all lapplication must be able to manipulate the data, and they must all have a way to present the data to a person. MVC just seeks to create a clear distinction between these responsibilities.

Every spare minute I’m spending with the Memento. In some respects it’s very simple, but in others I found some subtle complexities. It’s one of the few DPs where you don’t find some kind of interface–either an interface or abstract class. Lots of time can be spent on it. For what I want to do with it, an e-learning application with video and Power-Point like graphics/text, may take some time. However, if I get a decent abstract minimalist example together, I may put it up separately.

As for chatting about PureMVC–Chandima is definitely the go-to guy on it. I’d be a third wheel and either myForum2 or Quad (http://www.sandlight.com/quad) are good places for 4-way AV Chat. Let’s set it up with a time we can all be there. You and Chandima can chat and I’ll listen! With an extra seat, we could invite someone else who’s interested.

Bill

Next up will be the Memento, which is a very interesting DP for preserving state. Following that will be the Mediator, which, I agree is a very nice way to handle a lot of different algorithms while decoupling them from their objects.

I’m going to use the Memento with an online course system I had to put together when I broke my leg in October and couldn’t go to the bricks and mortar. The Memento will allow me to preserve a “place” in the video and slide show so that the user can stop where he wants and then go back without losing his place.

I think after reading Chandima’s piece on PureMVC, you’ll have fewer misgivings.

Bill

*By the by I do have my misgivings about PureMVC but I am reading Chandima’s note on the subject before I make up my mind

You know, that’s a good question. How do you know that the choice you’ve made as far as a DP is concerned is the right one. I liked the State DP when I did a video player because the video is so clearly state driven. However, I’ve seen good video players using MVC; so that’s a great issue to broach. That might be a good topic to kick around.–How to determine whether the DP you’re using is the best choice.

Thanks,
Bill

Your analyse + real life example == good job
Thxs (very good book)

I was going through the DPs like a man possessed wondering what I missed. Now I can sleep tonight.

One of the little things I was going to write was to be called “No New is Good New”–avoiding the use of new and using alternatives approaches. It may be related to IoC from what you say, and it sounds very exciting. I got the idea from the Freemans’ book and was going to follow up from there, but now I know I’ll go searching for more on IoC

Thanks again,
Bill

IoC = Inversion of Control, a.k.a. Dependency Injection. It’s the core of frameworks like Spring and Guice.

It’s less of a design pattern, more of a school of thought: instead of having a class use a concrete implementation of another class, have it rely on an interface implemented by that concrete class. Then, use a container (such as Spring) to “wire” in the concrete implementation to use at runtime.

I do this with delegates in my Flex apps: if I have to read Contact instances from a service, I rely on IContactDelegate. Based on runtime configuration settings, I have a factory that provides a specific implementation: RemoteObjectContactDelegate may be an implementation using ColdFusion or BlazeDS, while MockContactDelegate may just “fake” having a server there so that I can develop independently of the back end.

-Joe

I’m guessing most of the people following this blogg or reading the book are actually going to implement this stuff within the Flex Framework, creating components from scratch by extending UIComponent or extending other Flex components.