Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using component.js #40

Open
jasonkuhrt opened this issue Mar 28, 2014 · 6 comments
Open

Using component.js #40

jasonkuhrt opened this issue Mar 28, 2014 · 6 comments

Comments

@jasonkuhrt
Copy link

I am a little confused about component support. Happily for me you have chosen to use it but I didn't see simple component integration for worker.js. I am currently manually storing the worker file under /dist/, however, if I am installing from component this should be taken care of automatically?

You are also missing component install instructions at http://gridstylesheets.org/usage/

@jasonkuhrt
Copy link
Author

I will happily send a PR to update the docs at https://github.com/the-gss/the-gss.github.io once I understand correct component integration.

@d4tocchini
Copy link
Member

I've been a little befuddled with Component.io lately. @bergie set the component things up, and I find myself bugging him about it more than I would like to. Component is being used for GSS's internal depedencies, but when I include GSS in another project I fall back to bower. PR's are more than welcome if you can help make this better!

@jasonkuhrt
Copy link
Author

@d4tocchini @bergie componentjs is a solid idea initially pushed greatly by @visionmedia, and now @jonathanong. Things have been bit bumpy (reasonably so) on the road to 1.0.0, but I would wager there is a lot of benefit to staying the coarse here. bower to my knowledge does not solve as many problems as componentjs such as a module and build solution. As far as I can tell componentjs supports the unix-y/npm-y modularize-everything philosophy quite well. Wrinkles remain, I'm curious what yours are.

@jasonkuhrt
Copy link
Author

Moreover bower is just version resolution and a fat git pull (no?) whereas componentjs has a far more nuanced solution on hand.

@bergie
Copy link
Contributor

bergie commented May 5, 2014

@jasonkuhrt yeah, Component.io has its good and bad sides. Especially plugin support is problematic (see for example the still-unsolved componentjs/builder.js#125 which breaks all plugins). They have a rewrite of the installation and building process, but that is still not quite production-ready, and includes severe usability setbacks, like requiring GitHub authentication credentials to install anything.

Despite these, I agree that we should ensure GSS is installable via Component. Is anything else missing than some files declarations?

@tj
Copy link

tj commented May 5, 2014

yea sorry guys :( it has been in flux lately since I haven't really been working on it (I'm not doing any front-end work lately) so things are getting a little crazy. The end-game is just to be better at supporting future web components etc, since that's where the future is going, component and browserify will disappear as they are today

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants