Difference between revisions of "Bower"
From OpenEMR Project Wiki
|
|
| (150 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| =Bower=
| | #REDIRECT [[Composer and NPM]] |
| :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):
| |
| ::*https://github.com/openemr/openemr/commit/b63b0da6a5eae6f8051234bff104a06cb37db167
| |
| ::*(also see above commit for a example on using the global/path)
| |
| :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)
| |
| :'''<span style="color:red;">Development is ongoing for this project</span>''':
| |
| :*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=
| |
| :*[https://sourceforge.net/p/openemr/discussion/202506/thread/d4ec2b8b/ assets directory]
| |
Latest revision as of 07:28, 1 September 2018
