Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/hellysmile/django-activeurl
Easy-to-use active URL highlighting for Django
https://github.com/hellysmile/django-activeurl
Last synced: 18 days ago
JSON representation
Easy-to-use active URL highlighting for Django
- Host: GitHub
- URL: https://github.com/hellysmile/django-activeurl
- Owner: hellysmile
- License: apache-2.0
- Created: 2013-02-15T23:10:05.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2022-09-26T13:07:23.000Z (about 2 years ago)
- Last Synced: 2024-10-14T17:07:02.901Z (about 1 month ago)
- Language: Python
- Homepage: http://django-activeurl.readthedocs.io/en/latest/
- Size: 328 KB
- Stars: 158
- Watchers: 8
- Forks: 29
- Open Issues: 12
-
Metadata Files:
- Readme: README.rst
- Changelog: CHANGES.rst
- License: LICENSE
Awesome Lists containing this project
README
================
django-activeurl
================
Easy-to-use active URL highlighting for Django
.. image:: https://img.shields.io/travis/hellysmile/django-activeurl.svg
:target: https://travis-ci.org/hellysmile/django-activeurl
.. image:: https://img.shields.io/codecov/c/github/hellysmile/django-activeurl.svg
:target: https://codecov.io/gh/hellysmile/django-activeurl
.. image:: https://img.shields.io/pypi/v/django_activeurl.svg
:target: https://pypi.python.org/pypi/django-activeurl
Features
========
* automatic highlighting of currently active ```` tags via CSS class
* automatic highlighting of parent ```` tags for menus
* removes boring / hardcoded stuff from your life!
* href="#" never causes highlighting for compatibility with techniques such as
bootstrap nav.
Usage
=====
After loading the template library via
.. code-block:: html+django
{% load activeurl %}
the following code snippet will be rendered like this if `request.full_path()` starts with `/some_page/`:
.. code-block:: html+django
{% activeurl %}
{% endactiveurl %}
**Note:**
The content of ``{% activeurl %}…{% endactiveurl %}`` must have valid root tag (i.e.
``
- `` or ``
Installation
============
Python 2.7+, 3.4+ are supported.
1. Install the *stable* version using ``pip``::
pip install django-activeurl
or install the *in-development* version using ``pip``::
pip install -e git+git://github.com/hellysmile/django-activeurl#egg=django_activeurl
2. In your ``settings.py`` add the following:
.. code-block:: python
INSTALLED_APPS = (
...
'django_activeurl',
...
)
TEMPLATE_CONTEXT_PROCESSORS = (
...
'django.core.context_processors.request',
...
)
3. The *lxml* library is required and thus additional libraries need to be installed to build it:
* Ubuntu::
sudo apt-get install libxml2 libxml2-dev libxslt-dev build-essential python-dev
sudo ldconfig
* Fedora::
sudo yum groupinstall 'Development Tools'
sudo yum install libxslt-devel libxml2 libxml2-devel python-devel
sudo ldconfig
* MacOS X::
brew install libxml2 libxslt
sudo update_dyld_shared_cache -force
* Windows:
A pre-built *lxml* binary can be found `here `_
* Clouds:
There's a 99.99% chance that *lxml* will build out of the box.
Options
=======
menu ="yes|no" (default: "yes")
-------------------------------
Should hierarchical menus be supported? There are two different ways to declare an *active* status:
* the *starts-with* logic toggles the active state if ``request.get_full_path()`` starts with the
contents of the ``
{% endactiveurl %}
The **equals** logic works best for non-hierarchical menus where only those items should be highlighted whose ``href``-attribute perfectly match ``request.get_full_path()``:
.. code-block:: html+django
{% activeurl menu="no" parent_tag="div" %}
{% endactiveurl %}
ignore_params ="yes|no" (default: "no")
---------------------------------------
``ignore_params`` will ignore GET parameters of URLs, e.g.
*/accounts/login/* will match */accounts/login/?next=/accounts/signup/*.
parent_tag ="div|li|self|…" (default: "li")
-------------------------------------------
``parent_tag`` defines that a parent element -- and not the ```` tag itself -- should be declared *active* when there's a match in URLs. When you need to change the CSS class of the ```` tag, just enter "self".
css_class ="" (default: "active")
-----------------------------------------
Defines what CSS class to add to an active element.
Configuration
=============
The default options can be set in ``settings.py`` as well:
.. code-block:: python
ACTIVE_URL_KWARGS = {
'css_class': 'active',
'parent_tag': 'li',
'menu': 'yes',
'ignore_params': 'no'
}
ACTIVE_URL_CACHE = True
ACTIVE_URL_CACHE_TIMEOUT = 60 * 60 * 24 # 1 day
ACTIVE_URL_CACHE_PREFIX = 'django_activeurl'
By default *django-activeurl* will try to retrieve a previously rendered HTML node from Django's caching backend before active URLs are looked for and a new HTML tree is built. You can disable the cache with ``ACTIVE_URL_CACHE = False``.
In addition, ``ACTIVE_URL_CACHE_TIMEOUT`` can be used to define a timeout for keys to expire. The default value is one day.
The last configuration option is ``ACTIVE_URL_CACHE_PREFIX`` (which is ``django_activeurl`` by default) and defines which name to use in Django's caching backend.
Tests
-----
::
pip install tox
tox
Jinja2
======
Vanilla `Jinja2 `_ configuration:
.. code-block:: python
from jinja2 import Environment
from django_activeurl.ext.django_jinja import ActiveUrl
env = Environment(
extensions=[ActiveUrl]
)
Options can be omitted:
.. code-block:: jinja
{% activeurl css_class="active", menu="yes", parent_tag="li", ignore_params="no" %}
{% endactiveurl %}
If you're using `django-jinja `_
you need to load the ``ActiveUrl`` in ``settings.py``.
Django 1.8+ Jinja2 environment loader example can be found in `tests `_.
Background
==========
For building the HTML element tree *django-activeurl* uses `lxml
`_, which is one of the best HTML parsing
tools around. More info and benchmarks can be found at `habrahabr.ru
`_ (in russian). Note that there's no
content rebuilding inside the template tag when no active URLs are found, so
there's no impact on performance.