search

realityendshere / emberella

A collection of Ember mixins, helpers, views, and controllers developed for my own projects that might offer use or inspiration to other budding Ember developers.
MIT License
250 stars 25 forks source link

Any plans on adding bower support? #8

Open seifsallam opened 11 years ago

realityendshere commented 11 years ago

At this time, my projects only require support for Safari. Thus, I only verify usability in the one browser.

That said, many of the mixins, helpers, and controllers do not rely on anything browser specific. And the list view is used by at least one other developer as part of a publicly-facing web app with support for multiple browsers. I will also consider any pull request that adds browser support.

The whole project still has no tests, is in flux as Ember itself evolves, and should be considered experimental. As stated, it is offered for inspiration and exploration purposes at this time --- not recommended for production use, yet.

realityendshere commented 11 years ago

Sorry about my brain fart. I see now you were, in fact, talking about Bower (https://github.com/bower/bower).

The short answer is: maybe. My apps currently run on Rails with our client code packaged up by Rails Asset Pipeline / Sprockets. As you can see, my knowledge of package management options is otherwise somewhat limited --- so I am open to thoughts and suggestions.

Thanks for suggesting Bower. I will keep it in mind.

seifsallam commented 11 years ago

I'm new to the whole thing too. Anyway thanks for considering it, and keep it with emberella :+1:

gentlefox commented 10 years ago

You can simply add this repo to bower.json. ie: { "name": "myApp", "dependencies":{ "handlebars": "~1.3.0", "jquery": "^1.11.1", "qunit": "~1.12.0", "ember-qunit": "~0.1.5", "ember": "1.5.1", "ember-data": "1.0.0-beta.8", "emberella": "https://github.com/realityendshere/emberella.git", "ember-resolver": "~0.1.1", "ic-ajax": "~1.x", "loader": "stefanpenner/loader.js#1.0.0", "ember-cli-shims": "stefanpenner/ember-cli-shims#0.0.2", "ember-load-initializers": "stefanpenner/ember-load-initializers#0.0.2", "ember-qunit-notifications": "^0.0.1", "ember-cli-test-loader": "rjackson/ember-cli-test-loader#0.0.2", "pipwerks_scorm_wrapper": "git://github.com/pipwerks/scorm-api-wrapper", "sly": "", "bourbon": "3.2.x", "neat": "~1.6.0", "bitters": "~0.10.0", "ember-data.model-fragments": "~0.2.0", "projekktor": "", "respond": "~1.4.2" } }

When a repo hasn't been configured for Bower, you just need to be aware of compatibility requirements and resolve them yourself, taking care to maintain a personal fork of a repo if a particular version is required. If you're using ember-cli, such as I am, then you can still control where and how one uses any code brought in via bower all within your Brocfile.js.

seifsallam commented 10 years ago

@gentlefox Thanks for the tip :+1: