js.bootstrap
Introduction
This library packages twitter bootstrap for fanstatic. It is aware of different modes (normal, minified).
This requires integration between your web framework and fanstatic, and making sure that the original resources (shipped in the resources directory in js.bootstrap) are published to some URL.
Contact
- Andrew Mleczko <andrew.mleczko at redturtle.net>RedTurtle Technology, http://www.redturtle.net/
How to use?
This should be setup before rendering a page. See fanstatic for more information:
>>> from fanstatic import init_needed >>> needed = init_needed(base_url='http://localhost')
You can import bootstrap from js.bootstrap and .need it where you want these resources to be included on a page:
>>> from js.bootstrap import bootstrap >>> bootstrap.need()
If you want gradients and drop-shadows on your buttons, menus and panels, you can include the bootstrap_theme css:
>>> from js.bootstrap import bootstrap_theme >>> bootstrap_theme.need()
Render the inclusion:
>>> print needed.render() <link rel="stylesheet" type="text/css" href="http://localhost/fanstatic/bootstrap/css/bootstrap.css" /> <link rel="stylesheet" type="text/css" href="http://localhost/fanstatic/bootstrap/css/bootstrap-theme.css" /> <script type="text/javascript" src="http://localhost/fanstatic/jquery/jquery.js"></script> <script type="text/javascript" src="http://localhost/fanstatic/bootstrap/js/bootstrap.js"></script>
CHANGES
3.3.4 (2015-04-21)
Update to Bootstrap 3.3.4 [amleczko]
3.3.2 (2015-04-17)
Update to Bootstrap 3.3.2 [teixas]
3.3.1 (2015-01-13)
Update to Bootstrap 3.3.1 [pabo3000]
Update bootstrap.py [pabo3000]
3.2 (2014-09-03)
Update to Bootstrap 3.2 [amleczko]
Add map files [neglectedvalue]
3.1.1 (2014-04-23)
Update to Bootstrap 3.1.1. [davidjb]
3.0.2 (2013-12-14)
update to bootstrap 3.0.2
3.0.0.2 (2013-12-14)
include missing font’s in manifest [dnozay]
3.0.0.1 (2013-10-01)
include missing theme.css [dairiki]
3.0 (2013-09-30)
update to bootstrap 3.0 [Christian Klinger]
2.3.2 (2013-08-02)
updated to bootstrap 2.3.2 [tmassman]
2.3.1 (2013-03-08)
Upgrade to bootstrap 2.3.1 [disko]
2.3.0 (2013-02-26)
Upgraded to bootstrap 2.3.0 [amleczko]
2.2.2 (2012-12-11)
Upgrade to bootstrap 2.2.2 [disko]
2.1.6 (2012-10-25)
Upgrade to bootstrap 2.1.1 [disko]
2.1.5 (2012-08-22)
pin to boostrap 2.1 [amleczko]
2.1.3.1 (2012-05-23)
fix problem with readme.rst and manifest.ini [amleczko]
2.1.3 (2012-05-19)
Update to bootstrap 2.0.3 [amleczko]
2.1.1 (2012-03-01)
Pin to bootstrap version 2.0.1 [amleczko]
2.1 (2012-02-01)
add also bootstrap images [amleczko]
2.0 (2012-02-01)
update to twitter bootstrap 2.0 [amleczko]
1.4 (09-11-2011)
update to twitter bootstrap 1.4 [amleczko]
1.3.2 (30-09-2011)
update bootstrap.css to proper 1.3.0 version [amleczko]
1.3.1 (29-09-2011)
fix javascript dependency problems [amleczko]
1.3.0 (28-09-2011)
Initial release - using bootstrap 1.3.0 [amleczko]
Release files for js.bootstrap 3.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| js.bootstrap-3.3.4.zip | 271.8 kB | Without provenance | Details |
Release files / js.bootstrap-3.3.4.zip
| Download URL | js.bootstrap-3.3.4.zip |
|---|---|
| Size | 271.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c6e56225f77063cf27d5a1094aced5cd35374dee682abaec555fcf86809a1f5
|
|
BLAKE2b-256 checksum How to use checksums |
0a279a776fc00065ef9661c98b391cedc1fe8d70745fa23cd4267cbcad1237a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for js.bootstrap 3.3.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
