# Uliweb UI
## What’s it
uliweb-ui is used to collection ui components, such as css and js.
## Compile utils and tags
First install node.js, npm,then install gulp and dependencies:
` npm install gulp npm install gulp gulp-riot gulp-clean-css gulp-jshint gulp-uglify gulp-concat gulp-rename gulp-notify del riot uglify-js error jshint `
Run:
` gulp default `
to compile uliweb-ui.css and uliweb-ui.js to uliweb_ui/static/modules, also compile tags to uliweb_ui/static/modules/tags
## make jsmodules.js
jsmodules.js is used to combine js modules defined in settings.ini into a javascript file, so that head.load can load them via load([“module1”, “module2”], function(){}). You can get it through command line uliweb jsmodule -a uliweb_ui to recreate it and save it to uliweb_ui/static/jsmodules.js. Because uliweb_ui is just an app, but not an application, so you should run jsmodule command in a project directory, so you can make a simple project, and just add uliweb_ui to INSTALLED_APPS, and run the command.
Uliweb_ui is already create jsmodule.js for you. But if you want to add more ui components to settings.ini, and also want to use load to process them, you should recreate jsmodules.js yourself.
## Concat plugins Step.1 Write some configuration in ‘settings.ini’ of your uliweb project. like that:
` [TEMPLATE_GULP] you_want_name = [ "plugin name", ... ] `
Step.2 Enter a command in CLI of your uliweb project
` uliweb gulpplugins -d app_name `
Then you will find some files in the folder(you_want_name.js && you_want_name.css)
` .../your_project/apps/app_name/static/ `
Step.3 In the template file, use plugin with command “{{use ‘plugin name’}}” , you_want_name.js and you_want_name.css will loaded
Metadata
Release files for uliweb-ui 0.1.0
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 | Actions |
|---|---|---|---|---|
| uliweb-ui-0.1.0.tar.gz | 12.6 MB | Without provenance | Details for uliweb-ui-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| uliweb_ui-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for uliweb_ui-0.1.0-py3-none-any.whl |
Total release size: 26.1 MB
Release files / uliweb-ui-0.1.0.tar.gz
| Download URL | uliweb-ui-0.1.0.tar.gz |
|---|---|
| Size | 12.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6c5dc57da48fbd37bf0069e8a492a81fba63a24fa3acdbaa87fe917782742171
|
|
BLAKE2b-256 checksum How to use checksums |
27957b5f8b9ca543b8c0344b0e69209fc58213d4ea69e1e3b7c7208b78f08212
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Release files / uliweb_ui-0.1.0-py3-none-any.whl
| Download URL | uliweb_ui-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc20130bba3cc1c4746a5e370cbe7ac7718bb2a0251f8bf5e9a5c88c48411c36
|
|
BLAKE2b-256 checksum How to use checksums |
2ec18d6571640f2057da3928a420261f5aa407edf78baaa6cb95669216095f6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Security for uliweb-ui 0.1.0
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.