Overextended modules about aura HOT 1 CLOSED

Hey Dustin,

I completely agree that a Todo application on its own is insufficient to correctly illustrate how this architecture can be more efficient than others. Zakas used it the most on the Yahoo homepage and so I would argue that perhaps demonstrating it on a significantly scaled down 'homepage' with a few sample widgets (e.g weather) would be better.

In the past I have found myself going entirely too granular with Todo apps trying to make them fit into the architecture (I.e a Todo counter was a widget, the list was a widget etc). This is fine for a very basic way of showing the thing working, but anyone reviewing the architecture will be very likely to be building something non-trivial, where Todo app just doesn't cut it.

With that in mind perhaps we could do three widgets (weather, stock checker, something else). I'm using the word widget rather than module here as I think that's what each of these wrapped 'blocks' of functionality really are.I also am in agreement about AMD modules being the 'modules' in this architecture. Maybe we should have a wiki page in pace with a glossary of terms so others aren't confused too.

So then each AMD module within the Aura module includes the sandbox to get the functionality it needs like DOM manipulation, event handling, and AJAX. There is most likely a single entry point into that Aura module which, I think, would also be the one responsible for registering the Aura module with the core (mediator).

I agree with all of the above too.

I think we have a good opportunity with this project to define not just an example of how to implement this architecture but an entire layer that developers could drop into an a new project and use. Aura-core would probably evolve into this. One thing I'll probably be pushing for later is adding unit tests (which I'm more than happy to write up), but I'm excited to see what demo apps we can put together once everything is stable.

Please feel free to reach out at any time.
Addy

from aura.