I just came across it today, (google search)
looks pretty powerful
must have a look

OK, so this is an experiment that I have been pondering and working on for about six months now.
Its code named Domino, and its function is to enable non linear execution of commands from an external data source.

The main reason I started on this is that in previous complex projects I have had problems managing my command structures, especially those which involved chaining them up.  I wanted to be able to visualise them, so I started drawing diagrams of command processes.

anyhow what i had originally intended (while still maintaining the core idea) has become something else entirely, and the scope of the final project scares me a bit (i'm about 1/100 of the way through it).

I have all the core code functioning, and am busy writing a real world demo (a flick book application for my wife's art project), but I'd like to explain the concept and get your feed back, as I'm not sure if it is just quite an interesting experiment, or if it actually has any real world value.

I appreciate you taking the time to read it:
http://revisual.co.uk/?p=386

cheers

hey, NarfTurd (nice name) :~)
the confusion may also have come about through the fact that I originally called my UnifiedLoader AssetLoader, but changed the name so that people wouldn't get confused....
can't win, eh?

been thinking about this quite a bit...

and surely a Notification's name is defined as a string.  It doesn't enforce any content structure.  To do so now would only create huge backward compatibility issues. I personal think you should be able to define notification names as the first line of Shakespeare's sonnets (poetic and obviscating) if you so desire. 

darshan seems to have been one step ahead of this any way.

changing the note names on the utils is not a problem, but it should be part of a considered plan, not just a quick fix

cheers

this shouldn't be needed,

If you need more than one command to be triggered by this event, simply register a macro command (synch or asynch ) with the Notification, and add all the sub commands within the initializeMacroCommand method.

also, don't forget that mediators can also have interests in notifications.

cheers:~)

hey, thats really cool Darshan! :~)

of course it was,
I'm only saying that it is good to get some standards so that such a simple thing doesn't bring down the house.

btw, i always used to use . delimitation with my note names which, of course, would not clash with the Fabrication /
just a thought
:~)

sure, jasonmac, I bow to your knowledge of Fabrication, I haven't had a chance to look at it yet.
If it's entire notification system relies on slashes, then:

Asking a developer with a huge code base, who's project has existed much longer than this one, to change his entire logic of routing to work with a very small utility seems a poor choice of fixes to me

seems a sensible attitude :~)

The slash notifications in the State Machine were added by Cliff, so I await his judgement.

as I said previously, I think this is going to happen more and more, and not just for simple utilities like this one. 

hi GroundZero,

you have brought to a point a question that I have been asking my self.  There is a lot of really great stuff  coming out around the pureMVC frame work: fabrication, pureMVC Studio, and I'm not sure whether they will be compatible with each other. I'm working on my own little project, and don't want to create something that can't be used seemlessly alongside the like.  

In this case though, I have to agree with gjastrab, I think using package conventions on note names is a really useful way to avoid pollution, and they are simply Strings, and should be able to contain anything. I think you are right about talking to Darshan about this, as the fact that they can't work together needs to be ironed out. I'd be interested to hear Cliffs views on this.  I'm sure he has a master plan that he hasn't divulged to us yet.

well here it is:

http://revisual.co.uk/?p=409

The AsynchMacroCommand doesn't seem the keep the thread, and so the DISPLAY state is entered before the load is completed ( check out the enabling of the button states ). This is ok in the demo, as the progress window is modal, so restricts interaction. So using this method requires more care.

Have a look and see if I've done something wrong...

cheers

LOL, yes, that's next on my list.... I wanted to show two ways, encapsulating the asynchronisity in its own state, and an asynchronous state transition.

Its just that the project I ripped the demo code out of handles it the former way.

I will try to do it by the end of the week.

hey, cambiata,
have whipped up a quick demo here you go.
http://revisual.co.uk/?p=388

I presume you are talking about the Interceptor Pattern
Do you have any resources?

well, I'm working on some thing similar at the mo, and at some point I'll try and rip the guts out to make a simple demo... don't hold your breath tho...:~/