Pilot the AR.Drone 2.0 directly from your browser. Extend the application with plugins to add features such as video recording, autonomous flight, face recognition, and more.
Cause bower already upgrades to 0.10 and made some change, so the components will be installed to bower_components under root path, so jquery path would be wrong.
Maybe a add a .bowerrc like this:
{
"directory": "public/components"
}
to make sure install path is what you want.
PS: Actually it's make such a big deal out of it if only use jquery, unless you might add more assets and want to manage them using bower. ;p
The reason I introduced bower in there is to have a centralized way to manage front-end dependencies for the plugins, with something similar to 'peer dependencies' in npm. But I haven't explored this yet.
Cause bower already upgrades to 0.10 and made some change, so the components will be installed to
bower_components
under root path, so jquery path would be wrong.Maybe a add a .bowerrc like this:
to make sure install path is what you want.
PS: Actually it's make such a big deal out of it if only use jquery, unless you might add more assets and want to manage them using bower. ;p