integrate component-graph ?

[yields]

what do you guys think ?
component-graph

it's kinda annoying to have to download it in order to run it, and i think even if it had it's own domain it will be annoying too.

[ianstormtaylor]

i think it looks sexy as hell ;)

[yields]

thanks!

[ghost]

@yields is the indicated size inclusive of the dependencies? Seems very helpful!

[yields]

nope, just the lib itself.

i think dependencies are "free" if you are using component, though i'm open to suggestions!

[tj]

+500

[yields]

sweet!

@visionmedia, @ianstormtaylor

how / where do you think it's best to integrate it,

• in a component page, as a view, maybe add a link to the nav ?
• mount it e.g component.io/graph/user/project

[ianstormtaylor]

it would be cool inline i think. or else i probably wouldnt click it very often if i had to navigate away from the component page i'm looking to see it, which would be unfortunate because part of me thinks it is interesting for everyone to see the component graph of the component they are searching for. it's kind of like visualizing the component.json which is rarely "checked" to see if everything is okay.

the trick is that its big, dunno how small we could make it and still have it be useful.

tangent: it would be sweet to have a mode where the circles aren't colored, but actually the github avatar of the user who owns the dependency. you could see who each component is depending on. and then would really be sweet to find ones that have like 5+ different people's components used

[ianstormtaylor]

if its not visible by default because its too distracting, it would be nice to have a small icon that brings it inline (fade in) instead of navigating away still

[tj]

on the page would be cool, I wouldn't mind dumbing down the github readme stuff a bit, it's styled really bad right now and I'm not a huge fan of mirroring github like npmjs.org does

[ianstormtaylor]

yeah i generally just immediately click the github link in npm instead of reading the readme on npm

[timoxley]

@ianstormtaylor yeah the npmjs.org pages are really annoying. I have a chrome extension that automatically forwards you to the repo, but this is less useful recently as there's now npm repo modulename to go straight to the repo from the commandline.

Would be good to have the dependency graph displayed upfront (less clicking = better) but only if there's a way to make the graph non-moving/dynamic.

[ianstormtaylor]

@timoxley as in get rid of the initial bounce-around animation, yeah? i could see that. i could also see (if we move to sheets) it might feel badassly like the sheets sliding out caused the animation though :)

[juliangruber]

@timoxley for that I created ghub.io

[timoxley]

@ianstormtaylor yep, I'm not sure if it's possible though, every time I see one of those d3 force directed graphs it's unnecessarily animated and interactive. hopefully the net will soon collectively cotton on that most d3 effects are superfluous, tacky distraction, like dramatic transition effects in slideshows, overt photoshop filters or miley cyrus.

[timoxley]

not criticizing your tool @yields, the graph is pretty and useful!

[ianstormtaylor]

"miley cyrus" XD

[timoxley]

@juliangruber nice, how do you get there from the commandline though?

[yields]

@timoxley

yeah this was the first time i used d3 and i didn't enjoy this at all hehe (felt like jquery all over again), i'm actually working on removing this huge dep.

[ianstormtaylor]

is it okay to hack on a diff branch under the component org? bored and wanna try some stuff out but figure i shouldnt do it on my own fork for people to help

[juliangruber]

@timoxley you could do $ open http://ghub.io/component

[tj]

@ianstormtaylor yeah go nuts man!

@yields haha yeah, I like the idea of d3 but it's a behemoth for sure, I can't help but think how many useful components/npm modules it would be comprised of :(