How to add Ember-Bootstrap to an EmberJS project created via Yeoman - ember.js

I've started working on an EmberJS application and used Yeoman to generate the skeleton structure. Now, I'd like to add Ember-Bootstrap to my project but am having trouble doing so. I downloaded the latest version from GitHub and unzipped it but I'm not sure what to include.
I see several .js files in the packages/ember-bootstrap/lib folder. Do I need to include all of these? If so, then in which order should I include them?
Someone mentioned in another answer that you needed to add it to the "assets" folder but I don't have one of these.
Does installing Ember-Bootstrap require having a Rails project? I'm not familiar with Rails so please forgive for the newbie questions.
Thanks.

I found a great project that supports Bootstrap 3.0 with many components,
you can find it here:
https://github.com/ember-addons/bootstrap-for-ember
you can see all components alive:
http://ember-addons.github.io/bootstrap-for-ember
GoodLuck.

Related

Angular2 basic seed in WebStorm

I am new to Angular2 and WebStorm. I am looking for a basic project seed for WebStorm that I can start play around with Angular2.
There are lots of them online, but I can't find a single one that walks me through what are the basic packages that I need and why I need them.
Is any of you aware of a tutorial that can help me accomplish this?
As you are new to Angular2, just start with Angular2 Quickstart. You can create a new empty project in WebStorm and start populating it with your stuff following the steps in tutorial, or download the project stub from https://github.com/angular/quickstart and open project folder in WebStorm using File | Open.
Note that WebStorm itself doesn't force you to use this or that project skeleton, generator, bundler, etc. - just use whatever you want... see also https://blog.jetbrains.com/webstorm/2016/04/angular-2-workflow-in-webstorm - you may find this blog post helpful

Writing an ember-cli addon in Coffeescript

I'm trying to author an ember-cli addon, and I prefer to develop in Coffeescript. But it seems like the CLI build is hardcoded to look for just .js files. Is there any way to author an addon in Coffeescript and have the build take place with the consuming application's build (i.e. without me having to build the addon each time using a custom build process).
Yes, you can author in Coffeescript, but there was a bug in 0.0.46 where we would only preprocess *.js files in the addon tree. This is fixed on master, and should be included in 0.0.47 soonish...
So turns out this is a bug in the CLI, but it wasn't fixed in 0.0.47. See https://github.com/stefanpenner/ember-cli/issues/2354 for more context, it's currently an open issue & PR.

How to integrate Foundation 5 in django

I'd like to starting use Foundation 5 in a django project.
My doubts are about how to setup folders of Foundation project.
Foundation now uses bower for js dipendencies.
I think it's not correct make a foundation 5 set up into the static folder of django.
Has anyone done a setup of foundation in a django project?
To compile scss files I'll use django-compressor.
My solution is use django-bower... that's all!
Check here. It should have all the instructions.
https://pypi.python.org/pypi/django-zurb-foundation
I've been playing with foundation on my django project using the django development server. All I did was download the Foundation 5 static files (JS,CSS) and add them to my django static files. Then I added in the necessary scripts to my base template as shown here: http://foundation.zurb.com/docs/css.html. I haven't put it into production yet but I don't see any reason why that wouldn't work or why using static files isn't correct (as you thought in your question).
There are benefits to compiling the CSS yourself with SASS if you're really hardcore and I imagine that using template tags with django-zurb-foundation is a little cleaner or maybe easier to implement if you have tons of templates that you would need to modify but if you're like me and you just want to try Foundation out on a small project then downloading the extra applications (django-bower, django-zurb-foundation) isn't necessary.

Changing where Sitecore module is installed

I have a package I want to install. I would like the files to end up in a different directory than the installation wizard choses for them.
For example, my Sitecore copy is running at C:\SiteCore\website
The module added files to C:\SiteCore\website\Console
I would like the files to ultimately live at C:\SiteCore\website\sitecore_modules\Console
I am using Sitecore 6.5 rev 111230, but we are planning to upgrade very soon. I would like for my installed packages to migrate seamlessly once we have upgraded. For reference, the package I want to install at the moment is the Sitecore Powershell Extensions. Although, I would prefer to apply a similar method to any future packages that I install.
Is there a secret switch in the package installation process to allow me to do this? Can I do it from the package installation wizard? Is there another way to install packages?
I'm assuming I can't just change the package path and expect everything to keep working. Do I have to update a configuration somewhere (a file or inside the Sitecore CMS GUI) to make the package recognize the new file locations?
The module creator defines where files exist. If you move them you run the risk of something not working. The best idea is to ask the creator on the Marketplace page of the module.
There is no turn-key way to change this.
I guess you cand take the code from MarketPlace and you can modify it.
I don't know how exactly is the licenses with MarketPlace modules, but I think people can modify others code.
Please check on code and also on items, maybe on some fields are values for folder path.
I discovered a way to accomplish this, but it can be quite involved or even impossible, depending on the complexity and size of the package.
First of all, I did take the question to the module creator and had a very helpful and informative conversation with the creator. So thanks for that suggestion - they may even move the install location in a future release, based on my request.
The workaround is to first install the package on a system as normal. Then you figure out everything that comes with the package. For files, this is easy if your Sitecore root is under source control. For items, this is really complicated. You can search for the installed items by owner, if you had the foresight to create & use a unique user for the package installation. Or you can check the untyped files in the package that are essentially xml based item manifests.
Once you have a detailed list, you make the desired modifications to the locations. Then you recreate the package yourself using the Sitecore package designer.
This works for simple packages - I did it to one small package that I hope to get up on the Sitecore marketplace as shared source soon. And by small, I mean it was 2 files and 3 items. The package that prompted me to ask this question would not cooperate with this workaround. The included .dll had some assumptions about the file structure hard-coded into it.
The workaround I took for the more complex package was really quite basic: I just created a new source-code external to the required path. That let me wrap everything up neatly without getting medieval on the package files.
Thanks for both your answers, a very fine +1 to you.

Using latest Ember.js (1.0.0-PRE.3) with yeoman

The ember.js team just released the new version of the ember framework version 1.0.0-pre.3 this version includes the new "router" API that I'm very eager to use.
I'm about to start a new app and yeoman is in my workflow to help, but the yeoman ember-generator uses the 1.0.0-pre.2 version (wich has the deprecated router API implementation) for the generation of the projects boilerplates, but I would like to use the new version 1.0.0-pre.3 in my new project, and the easy way to do it is very hacky, it would be to change the ember.js lib directly in the yeoman templates directories and update the version number in the corresponding generator script that uses it, I've already made a test changing it this way and it would work, but this way I would "break" my yeoman installation, this is not a good option I think.
So my final master question is, how would I go about to update yeoman to use the new ember lib without hacking? Or should I maybe make a fork of the project https://github.com/yeoman/yeoman create a new branch for a new ember-generator (using the latest ember lib obviously) and make a pull request hoping to get accepted? Can someone "yeoman savvy" point me in the right direction here? I just want to make it the right way... if there is one :)
Thanks in advance!
Just manually update the ember lib in your project.
Yeoman 1.0 will have support for updating libs transparently.