Zemfrog Quasar
Quasar Framework Integration
Features
- Support vue v2
- Added Vuex & Vue-Router
- Integrated with Quasar
Usage
Install this
pip install zemfrog-quasar
Add this to the ZEMFROG_THEMES configuration
ZEMFROG_THEMES = ["zemfrog_quasar"]
Quick Tutorial
In this theme, several jinja blocks are available, such as:
meta- List of meta tags to includelinks- This is to be included in the head tag as (link,title, etc)content- This is to be included in the main tag (div#q-app)js- The js script that will be included, after vue, vuex, vue-router & quasarvuex- Configuration passed to vuexvue_router- Configuration passed to vue-routervue- Configuration passed to vue
Layouts
Examples of using layouts:
{% extends 'quasar/layout.html' %}
Links
An example of using block links, below we add material icons. By default it doesn't come with an icon, so you have to add it yourself.
{% block links %}
<link href="https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700,900|Material+Icons" rel="stylesheet" type="text/css">
{% endblock %}
Content
An example of using block content:
{% block content %}
<q-toolbar class="text-primary">
<q-btn flat round dense icon="menu" ></q-btn>
<q-toolbar-title>
Toolbar
</q-toolbar-title>
<q-btn flat round dense icon="more_vert" ></q-btn>
</q-toolbar>
{% endblock %}
Vue
Examples of using vue:
{% block content %}
<q-toolbar class="text-primary">
<q-btn flat round dense icon="menu" @click="active = !active"></q-btn>
<q-toolbar-title>
Is this active? <{ active }>
</q-toolbar-title>
<q-btn flat round dense icon="more_vert" ></q-btn>
</q-toolbar>
{% endblock %}
{% block vue %}
data() {
return {
active: false
}
},
{% endblock %}
In the example above, there are several explanations. See below:
- We add
datato vue via thevue block - We also change the vue delimiter to
<{,}>
Quasar
If you use this, you can't use the self-closing tag. See here https://quasar.dev/start/umd#usage
Metadata
Release files for zemfrog-quasar 1.0.2
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 |
|---|---|---|---|---|
| zemfrog-quasar-1.0.2.tar.gz | 3.2 kB | Without provenance | Details for zemfrog-quasar-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zemfrog_quasar-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for zemfrog_quasar-1.0.2-py3-none-any.whl |
Total release size: 6.3 kB
Release files / zemfrog-quasar-1.0.2.tar.gz
| Download URL | zemfrog-quasar-1.0.2.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
def5c306e74ef4b951a96fcd9048a252bc2e85847223f11d4b3857c83c6f349d
|
|
BLAKE2b-256 checksum How to use checksums |
4ae6d853fd035f554a700c39e58a08f412f4636c8302d1e1100ca7234fbf0097
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.5 CPython/3.6.9 Linux/5.4.0-70-generic
|
Release files / zemfrog_quasar-1.0.2-py3-none-any.whl
| Download URL | zemfrog_quasar-1.0.2-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2adf3b17057ed26af0f1082c96b44c686deeca2c8e8ef747072472b0853d4c8f
|
|
BLAKE2b-256 checksum How to use checksums |
cb8dec876d7d4f560c9b3a1cdc08f5fa2334efa43c2da8a59029a6c02836baeb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.5 CPython/3.6.9 Linux/5.4.0-70-generic
|
Security for zemfrog-quasar 1.0.2
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.