Difference between revisions of "Bower"

From OpenEMR Project Wiki
Line 5: Line 5:
::*(also see above commit for a example on using the global/path)
::*(also see above commit for a example on using the global/path)
:Current assets are:
:Current assets are:
:*font-awesome-4-6-3 (commit is pending to change from font-awesome to font-awesome-4-6-3)
:*font-awesome-4-6-3 (commit is pending)
:*literallycanvas-0-4-13 (commit is pending)
::*Placed "react" as "ignoredDependencies" in .bowerrc file.
:*react-15-1-0 (commit is pending)
:'''<span style="color:red;">Development is ongoing for this project</span>''':
:'''<span style="color:red;">Development is ongoing for this project</span>''':
:*Ideal directory for this stuff
:*Ideal directory for this stuff

Revision as of 08:17, 5 July 2016

Bower

Added this to attempt to standardize the assets that are used by openemr. Assets that are collected via bower are stored at interface/static; note this location is flexible since we are not sure where we will be storing these in the future as migrate to MVC architecture.
  • The path is set to a global here in the codebase(so the path will be easy to change in the future, if needed, along with changing it in the .bowerrc file):
Current assets are:
  • font-awesome-4-6-3 (commit is pending)
  • literallycanvas-0-4-13 (commit is pending)
  • Placed "react" as "ignoredDependencies" in .bowerrc file.
  • react-15-1-0 (commit is pending)
Development is ongoing for this project:
  • Ideal directory for this stuff
  • Ideal syntax of the bower openemr package
  • Incorporating versioning of the assets to allow multiple versions of 1 library (ie. such as jquery)
  • Several questions to answer:
  • Use this only for front-end libraries (css/js)?
  • Use composer for back-end libraries? If so, use separate directory?
  • Should we be using bower for this or is it better to manually bring in packages in a standard fashion?

Forum