==================
Simple application to manage "what's new" welcome screen based on package version.
.. note:: Package must contains valid PEP386 entry in the __init__ of the main module.
How to use
----------
- put ``whatsnew`` in your INSTALLED_APPS::
INTALLED_APPS=(
...
'whatsnew'
)
- modify your base template as
.. code-block:: html
<link href="{% static 'whatsnew/whatsnew.min.css' %}" rel="stylesheet" media="screen">
<script language="JavaScript" src="{% static 'whatsnew/js/whatsnew.min.js' %}"></script>
{% load whatsnew %}
<body>
{% whatsnew '<your_main_package_name>' %}
- create your :file:`whatsnew/whatsnew.html` like:
.. code-block:: html
<style>
#django-whatsnew .button.b-close {
background-color: #2B91AF;
border-radius: 7px;
box-shadow: none;
font: bold 131% sans-serif;
cursor: pointer;
padding: 0 6px 2px;
position: absolute;
right: -7px;
top: -7px;
text-align: center;
text-decoration: none;
}
#django-whatsnew {
font-size: 200%;
background-color: #FFFFFF;
border-radius: 10px;
box-shadow: 0 0 25px 5px #999999;
color: #111111;
display: none;
min-width: 450px;
padding: 0px 5px 5px 15px;
}
</style>
<script>
{% if display %}
function setCookie(name, value, days) {
var expires;
if (days) {
var date = new Date();
date.setTime(date.getTime() + (days * 24 * 60 * 60 * 1000));
expires = "; expires=" + date.toGMTString();
} else {
expires = "";
}
document.cookie = name + "=" + value + expires + "; path=/";
}
setCookie('{{ name }}', '{{ news.version }}');
$(function () {
$('#django-whatsnew').bPopup({
speed: 450,
transition: 'slideDown'
});
$('#whatsnew-seen').click(function () {
setCookie('{{ name }}', '{{ news.version }}', 365);
});
});
{% endif %}
</script>
<div id="django-whatsnew" style="display: none">
<span class="button b-close"><span>X</span></span>
{{ news.content|safe }}
<span><input type="checkbox" id="whatsnew-seen">do not show again</span>
</div>
- and your :file:`whatsnew/test.html` like:
.. code-block:: html
{% extends "base.html" %}{% load whatsnew %}
{% block body %}
{% whatsnew 'whatsnew' 1 %}
<script>
$('.b-close').click(function () {
window.history.go(-1);
})
</script>
{% endblock body %}
{% block jira %}{% endblock jira %}
How version are checked
------------------------
- try to get version number using setuptools
- check the main package name for 'version', 'VERSION' or '__version__'
- try to call package.get_version()
- raise DistributionNotFound
Metadata
Release files for whatsnew 0.3
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 |
|---|---|---|---|---|
| whatsnew-0.3.tar.gz | 16.3 kB | Without provenance | Details for whatsnew-0.3.tar.gz |
Release files / whatsnew-0.3.tar.gz
| Download URL | whatsnew-0.3.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aea54f37d3235e1bf7625585f239ad7a1bd87ba4b7ee6aa830735c37a23446c6
|
|
BLAKE2b-256 checksum How to use checksums |
d06d71dda410c8553e4080ea10500c816d45fe9d7709aa8257bf7a3b91d6602c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for whatsnew 0.3
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.