Okay sorry about that outburst... I realised I'd added too many pipes!  I'd added the teeSplit and Merge to the module as well as the shell. I removed them and it started working.

One thing I'd like to know a bit more about is the format of a Message, namely what the header and priority properties actually do... Is there any documentation on these?

I am getting to grips, slowly but surely!

 

Hi all,

I'm trying to get something working in Flash with Pipes, but I'm really struggling here. I really want it to work but I'm probably just too dumb! 

Anyway I've tried to connect a module to a shell using acceptOutputPipe and acceptInputPipe. I am then calling sendMessage with the body of the message just being "Hello"... But then it just crashes on the Pipe.write command because output is supposedly null...

Cliff you don't fancy doing another one of your fab seminars in London any time soon do you? 

Okay, you win! 

I guess it's just a lesson learned... At least we know that from now on, using MultiCore for us is the way forward.

Thanks,

:-Joe

I'm sorry to drag this back up again but...

I've just realised that a few of my old utilities which were written in Single Core have to now be converted to Multi Core... It's taken me the last ten minutes to work out why I couldn't just copy and paste a line from another project for registering a utility mediator, and this is why.

So, as a company, we have made the decision to ensure *every* project, no matter what people are doing, is Multi Core. That way we will not have this problem in future.

But this is kinda my point... Having two versions of something that only really needs one version. And we really only need one version. If you want Single Core, how long does it take to create a key name?

I believe the principles of DRY coding skills may apply here...

   

:-Joe of the CMCOP
:-(Campaign for Multi Core ONLY PureMVC) 

Hi Cliff,

Thanks for the in-depth reply, I completely appreciate the position. I am trying to make any project, multi or single core, using MultiCore from now on just so that all the utilities created are completely portable. The only thing I'd say is that from where I'm standing I believe that MultiCore could be plugged in underneath the single core version and people using it for single core would never even know... But that's just from where I'm standing, so that's all I'll say about it.

My problem arose when I took useful reusable proxies and mediators out from a MultiCore project and tried to use them in a basic single core project. It was only the imports I needed to change, everything else was the same, so I just felt it would be nicer for there to be one version only.

Thanks for all your great work!

:-Joe

Thanks! 

Hi there,

This may have been asked before, but is it possible that Single and MultiCore versions will be merged together soon? Considering MultiCore is simply an extended version of SingleCore, it would make sense...

My main gripe with there being two separate versions is that we are starting to create a nice library of reusable proxies, mediators etc. Having two versions means that sometimes when we import a reusable proxy or mediator, it doesn't work because it is linked to multicore when the project is single core, or vice versa.

Wouldn't it be worth merging them like this:

:

var facade:IFacade = SingeCoreFacade.getInstance();

:

var facade:IFacade = MultiCoreFacade.getInstance("coreName");
So if a string isn't passed, it just uses MultiCore to generate a single facade named "single" or something, but to the programmer they are completely unaware of its MultiCore nature...

...or am I oversimplifying the problem?

thanks!

:-Joe

Hi there,

It's been a while since I've been on here, I've been busy finishing off our (Atticmedia's) first big AS3 MultiCore PureMVC project in Flash. It's a broadband rich media adventure game for kids, called The Legula Adventure.

http://www.wheredidtherivergo.co.uk/

Click "Let's Go" and then click through to "Play Our Game" and launch the game. I created an adventure game system whereby each transition/video/location you go to is its own PureMVC Core with an API. The Core can be pure code or a SWF, and each of these "scenes" may load as many dependencies (animations, objects) on top of it as it likes. The whole thing then works on a recursive loading algorithm to allow scenes visited to be removed and to cache up-coming scenes.

MultiCore was fantastic to use and I look forward to working with it again!

Thanks for your time!

:-Joe

okay sorry I've got it now 

Everything extends Notifier and Notifier has multitonKey as a protected var...

sorry - please resume normal service! 

Hello,

Am I missing something, or is there no getter for a multitonKey?

In my traces (in the Command layer) I want to add the key name, so when I trace the whole project through the shell I know which module the traces are coming from.

Any ideas?

Thanks!

:-Joe

Excellent... Sounds interesting, I look forward to it!

I was actually wondering also, is it potentially plausible in the near future for Single Core and Multicore to be merged into one single system? It would be good to know that developing a PureMVC application could then be turned into a multicore one without any messing about with the original code... Have there been any thoughts on doing so?

Interesting!

Is this something likely to be added to MultiCore at some point in the future? How would you implement such a pipe?

Luckily for me, I don't think I will need to have modules communicating with each other. It will probably be beneficial to me if all traffic goes through the main shell application anyway.

Okay, so it's

APP  ----Interface---->  MODULE
       <----Events------

That right?

Thanks!

:-Joe

Hi Cliff!

I apologise in advance for my lack of Flex knowledge... I've been poking around with the modularity demo, trying to work out what goes where.

I notice you have set up interfaces for both Widget and WidgetShell... However I am wondering if this level of complexity is more than we need for this particular project. I believe we can do all we need to do through means of dispatching events... I was wondering if you agree.

The loader engine of the shell will be responsible for loading in the "widget" SWFs and storing them in a cache for later playout. When it comes time for the SWF to be shown on-screen. Once the SWF is displayed on-screen (through the Loader Class), all I should need to do is send it a message via a function call to start playing. I guess therefore I could make use of an IWidget interface for this to be completely safe.

Unlike Modularity, the Shell should have full control over the SWF so I'd probably shy away from passing the shell instance into the widget. The widget only needs to send certain messages when things happen, such as when it has completed doing whatever it set out to do. Since there will only be one widget active at any one time, I could communicate this information to the shell via a custom event... Do you reckon that is okay?

If I ever want to add extra complexity, such as requesting the shell to do certain things (like automatically show the help screen), I could add this in as and when needed...

Can you see any problems in doing it this way?

Thanks!

:-Joe

There's no problem with a Proxy retrieving and interacting with another Proxy. The Proxies are able to encapsulate dependencies in the Domain Model this way.

That's good to know... Thanks Cliff!