Hello, the standard way of doing this in PureMVC is using PureMVC multicore and create one module with one Facade for each of your modules (core).

Have a look at  Demo - Flex / Modularity http://trac.puremvc.org/Demo_AS3_MultiCore_Flex_Modularity it implements this. This seems to exactly be what you need, even if you use PureMVC in a different langage.

Porting Objs jQuery Employee Admin Demo to Native is a good idea. I'm not working on that for the moment. Please just be sure to use sources from my Github, it has slightly changed when I worked on the jQuery Mobile demo.

For StateMachine, for what I see in what David made seems, it looks like finished. He even has added unit tests. I do not have time to test it for real but it looks like finished. Note that I never wanted to use E4X in my project  you just had a look at sources when they were first converted from AS3 to JavaScript. This was just the original E4X AS3 code not JavaScript.

If you have not yet chosen which skeleton app to use you can have a look at the infamous Todo App example : https://github.com/addyosmani/todomvc this guy use this app to compare most used JavaScript MVC frameworks (look at the number of people following this github project).

Here is also a page presenting top 10 JavaScript MVC frameworks :
http://codebrief.com/2012/01/the-top-10-javascript-mvc-frameworks-reviewed/

They do not list Dojo, Zepto but there's also those ones.

For my part I use a SchedulerProxy. It has a method which receives a notification name and a number of milliseconds as parameters. It dispatches the named notification every N milliseconds and so can be used by both Command or a Mediator. The proxy also have some methods to manage the scheduled notifications map. I think I use the notification name as an ID. It could be better built and use a unique interval ID. I even thought to publish this as a PureMVC Extension for JavaScript.

I don't think project planning related questions must be get out the forums. Let's open a thread for this specific utility or kind of subjects if you want, but we can't e-mail the whole PureMVC community every time we want to talk about a project. Forums are specifically made for this in my opinion.

This said, I don't understand exactly what you mean, you already have finished to port the FSM? I just started with Unit Tests on my project. My plan was also to make a StopWatch demo when publishing the JavaScript utility. There also the multicore port of the utility to do.

What I don't understand is that I started 4 projects on my Github that are planned for long :

• JQuery and Employee Admin (done)
• JQuery Mobile and Employee Admin (done)
• State Machine (current work)
• Pipes (even not started)

I told about it to Cliff and LinkedIN group last month, Cliff just told me yesterday that you are exactly planning State Machine and Pipes. I'm working with and for PureMVC community for five years now and we never had this problem before. I'm kind of sceptic on what happens there.

I told Cliff that I even not have started with Pipes utility so anybody willing to work on it is welcome. But I really don't want to work for nothing on the StateMachine. I participate for my own fun and the community benefit I don't want to have problems because of this.

I'm currently (I mean now) working on it. I need to know if I'm losing my time.

David, can you confirm that I can continue my job on the PureMVC StateMachine?

From what I know and have tested across browsers: typeof this.onComplete == "function" is safe. This said, with JavaScript who knows, there could be a better solution for this or someone to tell that something else is best to do.

Excellent! Thank you Tony.

Just a remark, I saw that you are you using "Object.prototype.toString.call(this.onComplete)" instead of typeof this.onComplete == "function" ? Is this something related to ExtJS?

Hi Cliff, no problem. I always try to let my ego beside my workspace. But it will not benefits the PureMVC project if developers submit same things at the same time.

My thoughts were also to work with JSON instead of XML on the State Machine utility. I explained it by mail, forum or LinkedIN group recently I don't remember exactly. I wanted to make that and create the StopWatch demo before the end of the month.

To be honest I sincerely think there's plenty of things to do first before State Machine or Pipes in JavaScript. This is not so needed in JavaScript. I won't say we don't need it because I personally need them at work. This is why I started both jobs on my Github space. But I think it would be better to first have an human readable documentation for the Native port explaining "willing", "how to" and at least an "Hello World example".

Probably next what is the most requested is an AsyncCommand utility, it is so needed in JavaScript. Quite logical next the AsyncStub utility.

A lot of utility used to manage flash loading witll not be necessary with JavaScript (Loadup, Loadup as ordered) because CSS/HTML already have their loading paradigm and that we now have Require.js in JavaScript which seems to become near a standard for that.

If David want to do the PureMVC Pipes utility why not, just let me know I do not have started it officially. I just have explained why I need them and how I will conceived them. The only real need of this in JavaScript (as we don't have real modules support we have in Flash) would be to let communicate to different window context one to the other. This is a real pain to script (one could be loaded/unloaded before the other,etc) and here using Pipes would help a lot. Why not also studying a way to reuse BackBone modules. Those were my thoughts and my need at work.

David did a first pass at the StateMachine utility tonight

Important for me to know, I also started a project on the State Machine : https://github.com/tekool/puremvc-javascript-objs-statemachine and recently have announced to make it my next work for PureMVC JS. Can David let us know which status his project has in the next weeks? My project would have been convertible in less than an hour from Objs to Native

Don't we preferrably need some human readable documentation for the PureMVC JS Native port?

Now that jQuery Mobile reached its final stage and even 1.0.1 last week, I took time to finish an Employee Admin demo for jQuery mobile I started last year and that some here were aware of.

Read the blog post explaining how it works.

Launch the demo on your mobile

How would that work?

I'm sorry to talk about it again, but I'm using this syntax in Objs. In this case puremvc would not be a constructor but only a simple method.

In our case the syntax would simply be :

:

puremvc(

        // class info- defined separately to avoid collision with property
        // names defined on the prototype. None of these properties are added
        // to the classes produced.
        {
            /**
             * The classlets qualified name. The framework will automatically
             * create this object hierarchy for you, and your classes
             * constructor will be its referent
             *
             * @type {String}
             */

            classname: 'example.UserMediator'

            /**
             * The classlets superclass. The helper method will take care
             * of subclassing your class. Optional.
             *
             * @type {Function}
             */
        ,   parent: puremvc.Mediator

            /**
             * Your classes constructor. If not provided, one will be created
             * automatically for you. The automatically created constructor will
             * take care of invoking super constructors if the class is
             * extended from another
             *
             * @constructor
             */
        ,   constructor: function (viewComponent)
            {
                puremvc.Mediator.call(this.constructor.NAME, viewComponent);
            }
        }

        // prototypal traits- all instances will have these properties and
        // you can override superclass methods
    ,   {
            /** @override */
            listNotificationInterests: function ()
            {
                return [   ];
            }
        }

    ,   // static traits, i.e. properties which will be defined on constructors
        {
            /**
             * @static
             * @const
             * @type {String}
             */
            NAME: 'UserMediator'
        }
    );


If David finally chose that we need to use the method to reach classes identified by their namespace, we just need to identify the type of the parameter passed to the function to know if it's a class that is declared or a namespace that we want to reach. We can think of it as an overload like Java does. It would so be with :

:

var MyClassObject = puremvc("example.UserMediator");
This is simple and lightweight.

Why not using no name at all for the creational method?

Does David work on a way to remove code from constructors? I do not know that the Native JS repository was made public.

Cliff, the initialize (call it init or constructs or whatever we want) code convention I talk you about by e-mail and I used in my own Native framework I made last year and that I explained on my blog http://www.tekool.net/blog/2011/01/30/puremvc-native-javascript-port/ works well in conjunction with any UI/Class Framework. I used this Native PureMVC implementation successfully to build the EmployeeAdmin jQueryMobile demo I'm currently working on. It worked pretty well and could be considered as a good (not necessarily the right) solution. I can confirm that it would have also worked with any ExtJS/Prototype/Mootools frameworks. This said, I personally find any of those code convention painful to use.

Another solution I thought about to make this port a little more agnostic, would be not to use inheritance at all in the framework itself and let the developer implements its own inheritance system.