js.ace
Introduction
This library packages Ajax.org Cloud9 Editor for fanstatic.
This requires integration between your web framework and fanstatic, and making sure that the original resources (shipped in the resources directory in js.ace) are published to some URL.
Bitbucket repository : https://bitbucket.org/fanstatic/js.ace
How to use?
You can import ace from js.ace and need it where you want these resources to be included on a page:
>>> from js.ace import ace >>> ace.need()
CHANGES
1.4.11 (2020-05-31)
Update to ace v1.4.10
All resources from ace-build subdir “src-min-noconflict” are copied into this packge, but only top-level resources are defined as Resource objects. Load the extra mode/keybindings/themes/workers in javascript using ace.require().
1.0.0 (2012-10-15)
Update to ACE v1.0.
0.1.6 (10-07-2011)
Initial release.
Metadata
Release files for js.ace 1.4.11
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.ace-1.4.11.tar.gz | 2.0 MB | Without provenance | Details |
Release files / js.ace-1.4.11.tar.gz
| Download URL | js.ace-1.4.11.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3bc0116e40a6ef3754cfca645342d2c89ab1f69e8d77cf265a11d855e0ddb86
|
|
BLAKE2b-256 checksum How to use checksums |
eb83de38816049ee2f236c30d166dd95d20120b6e9fbae15a325e04cf11ca7c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/38.4.0 requests-toolbelt/0.8.0 tqdm/4.23.3 CPython/3.6.9
|
Security for js.ace 1.4.11
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.