I've just had a quick look at the demos and they seem to be very clear and easy to follow -- great effort guys!
-Chris

Thanks to all of those involved. Really looking forward to using this in our current project 
-Chris

Thanks Cliff (and David!),

Can't wait to dig in and give it a whirl. Yes, skipping the IE bit for a super basic demo is perfect - reduces the cruft and lets one concentrate on getting just the concept working (I'm only doing dev work for Webkit, so even better in my case!).

Many thanks to all involved for the efforts. Greatly appreciated! 

-Chris

Sounds great Cliff - sorry to be such a nag 
-Chris

PS. Let me know if I can help somehow...

Hi David,

I can imagine that you're busy as hell with a myriad of projects...

...if you'd like to, you could drop me a running native js project of some sort and I'll try and distill it down to an App Skeleton. As my skills in the PureMVC dept are rather lacking at the moment, it might require a bit of polish on your end, but that might save you a bit of time and allow me to start getting involved (as opposed to just asking for things on the forums all the time!).

Cheers,
-Chris

Hi David,

Yes, I think that an absolute minimal project would be both the fastest/easiest for you guys to chuck together and also the logical starting point for people trying out the Native port. For my money it doesn't even need to have an UI or any comms, just a working error-free skeleton, using the new native define() syntax.

After this is available, maybe a couple of more ultra-simple discovery apps could be built, before a newbie gets dropped into the Box Splash & Employee Admin demos (which can be pretty intimidating when one is first confronted with PureMVC)?
Here are a couple of rough ideas from following here for a while:

   

• Hello World -- simple UI example
• Multi-core -- how it relates to building larger, organised (modular?) js apps with PureMVC
• Hello World Plus -- An extended UI example, that might use some sort of UI helper (see this done repeatedly in other ports, so guessing it's a good idea).
• (...here would come the standard Box Splash & Employee Admin demos...)
• (...more advanced utilities demos...)

This way there would be a nice progression from the most minimal, to a complete functioning PureMVC Native JS app -- and each step in the progression would be very small and (hoping!) easy to follow/understand.

As always, a nice post (blog) somewhere aimed at those of us who are still quite new to PureMVC would be great! 

Cheers,
-Chris

Hi Cliff & Co.,

Just wondering if one you of core devs might be able to quickly put together a super simple/minimal Application Skeleton using the Native JS port and define()?

Cheers,
-Chris

I think define is fine

Just to check - is someone working on a super-simple Hello World example yet? I'm not clever enough to figure it out on my own... 

-Chris

Sounds like a great plan of attack Cliff.

Would also love to get my hands on it - happy to try and help with docs, testing, etc. 
-Chris

Thanks very much for the infos Cliff. Greatly looking forward to playing with it

Would be fantastic if there were three people (to start off with) involved in the core development. I did some googling and found two implementations, so curious as to who the third might be.

Cheers,
-Chris

Hi Cliff,

You mentioned a possible Native Javascript PureMVC port on LinkedIn -- just wanted to leave a bread-crumb here too (hope I'm not spilling any beans!).

I think a non-lib (mootools, prototype, et al) bound PureMVC would be perfect for us developers looking to avoid large, all encompassing MVC frameworks (for ex: JavascriptMVC).

I'm finding Agility.js (with jQuery and Less css) to be rather a slick way to handle the View part of the equation. I'm thinking that a Native Javascript PureMVC port might be a perfect fit with Agility for medium to larger sized apps. Can't wait! 

Cheers,
-Chris

Okay - after having done some more digging, it looks like the PureMVC MooTools js port is the way to go for JS based AIR apps.

I haven't done anything with MooTools to date, but must say that it looks like the perfect match for PureMVC! Not having a good way to organise my js code properly in a larg-ish AIR app has been the one thing holding me back from giving the tech a proper try.

Sorry for the noise with the above questions! If I get it all working and manage to grok PureMVC, would be happy to share any insights I might garner... 

Cheers,
-Chris

Hi gurus,

I'm slowly coming to grips with AIR 2.0 Javascript based apps (using jQuery).

I'd *really* like to have a go at using PureMVC for this work, but am not sure if it's possible to use the PureMVC actionscript classes, defined in "PureMVC_AS3_2_0_4.swf", directly via Javascript or not.

The issue seems to be needing to sub-class the PureMVC classes to use them correctly. I don't think there's a way to do this via Javascript???

I can import the PureMVC lib into the project with:

:

<script type="application/x-shockwave-flash" src="/lib/puremvc/PureMVC_AS3_2_0_4.swf"></script>

and create an instance of Facade...

:

var puremvc;
$(document).ready(function(){
     if (!puremvc) puremvc = {};
     puremvc.facade = new window.runtime.org.puremvc.as3.patterns.facade.Facade();
});

...but haven't figured out a way to handle the required sub-classing or adding Interfaces to the js object.

Anyone ever tried this?
If this approach isn't workable (guessing it's not), does anyone have some pointers as to how an AIR js based app could make use of the PureMVC swf directly, or would I have to look at using the JS port??

Sorry if this is a lot of questions!

Cheers,
-Chris

Thanks for the pointer Cliff -- I'll def follow your suggestion 

Cheers,
-Chris