Nope,

But I have seen it and I think it might be useful.

Best,
Sammi

Hmmmm,

so you recommend that each Proxy is usually only managing a single VO?

I put all kinds of properties (vo's or not) in the proxy and provide getters and setters to them.

Best,
Sammi

True,

there is often very little time.  That is why we love PureMVC

But sketching flows can still help, especially if it doesn't take long.  That is why tools like http://www.websequencediagrams.com/ are great.  It takes me only a few minutes to sketch some sequence that I want a developer in the team to implement.

But this tool is web based and has limitations.  I  am looking for alternatives that provide you with the same "plan at the speed of thought" but also offers expected desktop features like save and load.

They do actually have an API that I could use to create such an application - but then again  - time is a limited resource.

Best,
Sammi

Hi,

I was hoping that some of you have tips on what methods/tools you find helpful for planing the architecture of your PureMVC applications.

Do you use Sequence Diagrams?  Simple flowcharts?  Maybe nothing like that?

How do you sketch the flow of your applications?

Best,
Sammi

You are right - two notifications are the way to go I think.  It is cleaner that way.

Tank you very much,
Sammi

Hi,

this may sound strange but I think I would like to be able to "cancel" a notification.  I have a command that is triggered on notification.  This command does stuff and one of the things it does is to evaluate if there is any need to anything at all.  If nothing needs to be done I would like to prevent any interested mediator from getting the notification.

These mediators only have to act on the notification if something changed.

Sounds silly??  Maybe I should simply not send the initial notification if the command will not have to anything.  But I want the command to decide if actions are needed.

Best,
Sammi

Ooops,

I meant to say "That is to define a constant in the facade ..."

So the view components have their own constants for their normal events and corresponding notification constants a declared in the facade.

- LoginView sends a LoginView.LOGIN event when the login button is clicked
- LoginMediator listens for the event and the sends ApplicationFacade.LOGIN notification

Best,
Sammi

Thank you for your time.

I think I will end up doing like I have been doing now that I know that it is a commonly used method.  That is to define a constant in the mediator that corresponds to the view components mediator.

I wish I could figure out how to make an FDT template for a constant.  It would be cool to be able to add a constant template and then as you write the constant's name (SOME_NOTIFICATION), FDT would write "someNotification" or event just "some_notification" for you in the value of the constant

Best,
Sammi

Hi,

I have read the threads and FAQ on where to place constants and they make sense.  I prefer to put them in the ApplicationFacade, even if they are quite many, but I can also understand why some put them in a seperate file.  If I understand the recommendations correctly constants for notifications from the commands and mediators are declared in the application facade but constants for notifications from the model are declared in the proxies. 

What I want to understand better is how you handle constants in "view components".  A view component has a constant for an event that it dispatches.  Let's call it "LOGIN". The mediator for the view listens for the event and sends a LOGIN notification.

Should I declare a LOGIN constant in the application facade for that notification or can I use the constant from the view component:

sendNotification(LoginView.LOGIN)

It doesn't seem like a good idea but still most of the views actually trigger an event that results in the mediators sending out a notification and it bothers me to be defining the same constant twice.

Hmmmm....

Sammi

That sounds good Philip and I am looking forward to learn from your experience.

I am planing to write a few words also on how I like to use BulkLoader for this.

Best,
Sammi

Sorry,

I may have implied that there is a utility for PureMVC called BulkLoader - but that is not the case.

"BulkLoader is a minimal library written in Actionscript 3 (AS3) that aims to make loading and managing complex loading requirements easier and faster."

http://code.google.com/p/bulk-loader/

Best,
Sammi

Hi,

I have an application that requires quite a bit of loading at startup.  I have already completed the task by using an InitialAssetsProxy that uses BulkLoader (google) for loading the many different assets.  When the proxy has loaded all the assets an InitialAssetsLoadedCommand is run. That command creates proxies that will manage the loaded assets, and sets their data property with values from BulkLoader.

Is this better or worse than using the StartupManager Utility?  Am I missing something that makes the StartupManager more powerful?

I have used the StartupManager for this before and it works great but I feel like it requires a lot more code.

Best,
Sammi

Got it!

This is great. Thank you.

Sammi

Hi,

I am risking being taken for a silly guy - but I don't mind bacause I am.

I have been going over quite a few examples of PureMVC implementation and I can see that the usual PrepModel/PrepView commands seem to be used in Flex apps - but not in regular AS3 apps.

Is that because of the way Flex works?  Should I just register Proxys and Mediators in the Facade for simple apps? Or just in my StartupCommand?

Sorry about this silly question.

Best,
Sammi

Hi,

I just read the documentation and best practices and I must say this looks really good.  I have made several projects using Flex/Cairngorm and although I understand Cairngorm quite well I find to be an overkill for my projects.  I had been warned that it might be difficult to "unlearn" what Cairngorm teaches and switch to PureMVC but after reading the docs I am not worried.  This is pure and simple.  I remember it took some time to get to understand Cairngorm and even more time to get used to the repetitiveness.  I will still give Cairngorm respect - it is the "King", used by many to create great project.  It is just not very good for smaller, one person projects.

Now I can happily switch to PureMVC and use it for both my Flex and Flash project. I have been using PixLib for my Flash based projects and I loved it.  I just find that it makes sense to use the same framework for both Flash and Flex.  I will be able to use PureMVC for my MVC needs and mix in PixLib's functionality for other things.

Great work Cliff!  Thank you very much for creating this and sharing.

Now I am off to my first app.

Best,
Samuel