Open addyosmani opened 12 years ago
Ah, you are correct. I hadn't noticed that. Lets go with your suggestion :)
@unity
You are excellence.
Regarding the image / aura draft:
To all, what I'm meditating over (tldr):
I think we should create 2 diagrams:
Widgets are made to be reusable / modular. By themselves they are not active.
An application, like apps/demo/js/app.js
will use Aura's core, which requires the vendor libs and backboneSandbox
, which starts instances of widgets for an application.
Some bikeshedding, which may give people a better idea of how core.js really behaves: To be closer to what flask/slim does, we could make core
into Aura
/App
the class, and var app = new Aura()
or new App()
, where app
is now the a central sandbox for the app? This helps differentiate aura at framework level from the application instance.
IMO there should be 2 drafts: 1.) representation of Aura's factories, core has the vendor libs, there are widgets available to use. 2.) representation of an application instance using core
, loading vendor libs, abstracting them and instantiating widgets to the DOM, the widgets subscribing to pubsub.
On the Home page there should be only one diagram, not thriving for completeness but for clarity. It should be showing how Aura is architectured.
How it works exactly can be shown in the docs, in a tutorial and other places IMHO
Keeping that in mind, do you see anything else that should go in the homepage's diagram ?
Here's a live preview, with a nice eyecandy.
https://github.com/hull/aura/tree/website
We use Middleman + middleman-gh-pages to automate deployment to gh-pages.
Just to be clear : We're NOT finished, still working on it…
Absolutely love the eyecandy/animations and live preview. Thanks @unity :) I'll be reviewing the architecture we currently have in master to ensure the diagram captures everything we've recently added.
All: should we consider adding a feature table describing what we do or this information vs. other frameworks similar to us, or do we feel the three columned paragraph covers this sufficiently?
Looks great!!! Kudos to @unity & his team.
@addyosmani: I think table in adaption to all mentioned above wouldn't hurt.
On Wed, Nov 28, 2012 at 10:15 AM, Addy Osmani notifications@github.comwrote:
Absolutely love the eyecandy/animations and live preview. Thanks @unityhttps://github.com/unity:) I'll be reviewing the architecture we currently have in master to ensure the diagram captures everything we've recently added.
All: should we consider adding a feature table describing what we do or this information vs. other frameworks similar to us, or do we feel the three columned paragraph covers this sufficiently?
— Reply to this email directly or view it on GitHubhttps://github.com/addyosmani/aura/issues/132#issuecomment-10811329.
OK, wow. That looks great.
Optimization for the EyeCandy
Noticed some performance issues on my older Mac (canvas).
Your Feedback (did I say that already ? :) )
What more can I say than wow! So minimalistic and clean. And the header, bravo.
The only nitpick I can think of is that it would be more natural if the stars faded in and out. They currently suddenly appear and disappear.
Oh, and the site is currently unusable on iPhone. Looks like you're stealing touchmove or something.
Anyone up for writing it ? :)
@sindresorhus Thanks for the comments.
@sindresorhus @addyosmani @Francisc @robertd New version available here : http://hull.github.com/aura/
For now the text is taken from Aura's current description of the modules. If you want it updated, please tell us so !
Also, Vendors & Base have empty popovers. If someone wants to write a few paragraphs to cover what Base & Vendors do, that would be great !
The stars should appear and fade out reeeeally slowly. pop-in and outs are bugs, I'll look into that.
Seems like this happens when i switch back to the Aura site after a couple of minutes.
Particle field performance has been improved. Is it sufficient ?
Yup, much better
The schema entirely html, css & svg based, and animated.
So simple and elegant. I really like it! Combined with the pretty popovers it really makes Aura architecture approachable.
One thing I'm missing is a link to the demo.
I can add a link to a demo page. Is it out there already or do we need to build one ?
I'll look closely into the particles flicker, I have an idea where that could come from.
I was thinking about this https://github.com/addyosmani/aura/blob/master/src/index.html
It was a pleasure meeting you both in person @unity :)
Some further feedback on the site: I noticed that on mobile the section right after the header appears to fold prematurely so that the headline isn't visible (tested on Chrome/Android 4.2). On desktop it looks great though!
Same here !
Thanks for the feedback, I'll look into it and try to reproduce. Don't own an android though :)
Glad you like it, it's a fun project :)
On Tuesday, December 4, 2012, Addy Osmani wrote:
It was a pleasure meeting you both in person @unityhttps://github.com/unity:)
Some further feedback on the site: I noticed that on mobile the section right after the header appears to fold prematurely so that the headline isn't visible (tested on Chrome/Android 4.2). On desktop it looks great though!
— Reply to this email directly or view it on GitHubhttps://github.com/addyosmani/aura/issues/132#issuecomment-11017157.
Just pushed an updated version with the following changes :
All that would be missing would be a bit of text for the Base & Vendors, and the site could be pushed IMHO.
Woorks good on iPhone 4S. Particle effect flickers when scrolling but nothing serious. Great job !!!
Sent from my iPhone
On Dec 5, 2012, at 11:26 AM, Romain Dardour notifications@github.com wrote:
Just pushed an updated version with the following changes :
All that would be missing would be a bit of text for the Base & Vendors, and the site could be pushed IMHO.
— Reply to this email directly or view it on GitHubhttps://github.com/addyosmani/aura/issues/132#issuecomment-11053780.
Looks great on Chrome for Android here too. Fantastic job guys :)
A pleasure. Incidentally, we launched our own site today : http://hull.io
If you check it out, you'll see that our product might be a cool demo of a large scale aura app :)
Regards.
R.
On Wednesday, December 5, 2012, Addy Osmani wrote:
Looks great on Chrome for Android here too. Fantastic job guys :)
— Reply to this email directly or view it on GitHubhttps://github.com/addyosmani/aura/issues/132#issuecomment-11055328.
Only good things :)
If you want a "using aura" section tell me I'll add one with great pride and pleasure.
Still missing a bit of copy btw but I'm holding back writing it until the naming changes discussions have been sorted out
Romain Dardour, hull romain@hull.io
On Dec 15, 2012, at 4:43 PM, Addy Osmani notifications@github.com wrote:
What do we think about including apps/sites using Aura on the homepage? The two most recent I'm aware of are:
But I know there are more. I can tweet out to ask about others using it if we think its a solid idea.
— Reply to this email directly or view it on GitHubhttps://github.com/addyosmani/aura/issues/132#issuecomment-11405799.
I would love a "Using Aura" section :) We'll try to wrap up the naming changes as soon as we can!
As part of the conversation around the site, we should think about how we're also going to update the language in the README.
At present, we call Aura a "decoupled, event-driven architecture for widget based applications". I've been talking to Aura users recently and a few feel that we're limiting ourselves by saying we're specifically for widgets.
I was wondering if anyone else felt the same way. I also wonder if we should be making more of a deal that we offer a "scalable" architecture (ala Zakas) or whether we think developers get this without it needing to be said more clearly. I've noticed that some of the Aura alternatives do this.
Btw, in case anyone is interested the alternatives to Aura that are out there at the moment include:
Kernel.js, ScaleApp, Teriffically and Hydra.js.
Useful to look at what they're doing for their sites/language.
I think that most of these sites (including aura's which I'm working on) focus on explaining how it works whereas the most important thing is how it helps.
The benefits should be understandable by developers of much less expertise than the ones developing aura or even using it. The average jquery developer should be able to understand the problem and how aura provides a solution.
That does not mean it should be usable by them, but explaining the problem and solution should make them want to use it and improve.
I'll have a more detailed look at all those sites, try to extract the good and post it here. Explaining the problem and solution should be the matter of 2 small paragraphs, no more. All those sites say a bit much IMHO.
On 16 déc. 2012, at 19:36, Addy Osmani notifications@github.com wrote:
As part of the conversation around the site, we should think about how we're also going to update the language in the README.
At present, we call Aura a "decoupled, event-driven architecture for widget based applications". I've been talking to Aura users recently and a few feel that we're limiting ourselves by saying we're specifically for widgets.
I was wondering if anyone else felt the same way. I also wonder if we should be making more of a deal that we offer a "scalable" architecture (ala Zakas) or whether we think developers get this without it needing to be said more clearly. I've noticed that some of the Aura alternatives do this.
Btw, in case anyone is interested the alternatives to Aura that are out there at the moment include:
Kernel.js http://alanlindsay.me/kerneljs/, ScaleApp http://scaleapp.org/, Teriffically http://terrifically.org/ and Hydra.jshttps://github.com/tcorral/Hydra.js .
Useful to look at what they're doing for their sites/language.
— Reply to this email directly or view it on GitHubhttps://github.com/addyosmani/aura/issues/132#issuecomment-11420989.
"Aura helps you write cleaner, more scalable apps."
Wdyt ? Does it encompass what aura does ?
How about "Aura helps you write clean, scalable apps"? :)
Looks good to me :)
Is that the new tagline then ?
Romain Dardour, hull romain@hull.io +33 6 20 555 666
On Tuesday, December 18, 2012 at 12:17 AM, Addy Osmani wrote:
How about "Aura helps you write clean, scalable apps"? :)
— Reply to this email directly or view it on GitHub (https://github.com/addyosmani/aura/issues/132#issuecomment-11466738).
If no one disagrees I guess so :) //cc @tony
I like it, succinct.
"Aura helps you write clean, scalable apps"
Fine w/ me. :)
@sbellity @tony @atesgoral do we feel comfortable enough that the architecture concepts going into Aura 1.0, based on aura-express are stable/finalized at this point? If so, @unity might be able to update the mocks so that we can get a little further on the site :)
I'd be glad to do that : I'll check up with @sbellity how the architecture changed and how to explain it
If I need anything written or explained from you guys, I'll post here !
On Saturday, January 12, 2013 at 12:25 PM, Addy Osmani wrote:
@sbellity (https://github.com/sbellity) @tony (https://github.com/tony) @atesgoral (https://github.com/atesgoral) do we feel comfortable enough that the architecture concepts going into Aura 1.0, based on aura-express are stable/finalized at this point? If so, @unity (https://github.com/unity) might be able to update the mocks so that we can get a little further on the site :)
— Reply to this email directly or view it on GitHub (https://github.com/aurajs/aura/issues/132#issuecomment-12176799).
That would be awesome!
aura-express introduces important concepts :
I have previously posted about this is this thread : https://github.com/aurajs/aura/issues/168#issuecomment-11695071
I'am currently working on a blog post that explains all those concepts and why they were implemented in aura-express.
That sounds great, @sbellity :) I look forward to reading what you write up. Very excited for us to be getting aura-express off the ground and into master.
If anyone is interested in taking this on, we need to design/create a new site for Aura's 1.0 release. Feel free to let us know if you'd be up for helping with this :)