Majic Projects
Django Pydenticon Timeline
December 03, 2016
enhancement_tiny.png 15:46  Enhancement DJPYD-8 - Update Pydenticon requirement to version 0.3
branko (branko):
Issue closed
Status changed: New ⇒ Closed
Percent completed: 0% ⇒ 100
Resolution changed: Not determined ⇒ RESOLVED
icon_milestone.png 15:46 0.2
A new milestone has been reached
enhancement_tiny.png 15:46  Enhancement DJPYD-8 - Update Pydenticon requirement to version 0.3
branko (branko):
Title updated
enhancement_tiny.png 15:46  Enhancement DJPYD-8 - Update Pydenticon requirement to version 0.3
branko (branko):
Status changed: Closed ⇒ New
Issue reopened
Resolution changed: RESOLVED ⇒ Not determined
Percent completed: 100% ⇒ 0
enhancement_tiny.png 15:42  Enhancement DJPYD-8 - Update Pydenticon requirement to version 0.3
branko (branko):
Issue closed
Status changed: New ⇒ Closed
Percent completed: 0% ⇒ 100
Resolution changed: Not determined ⇒ RESOLVED
feature_request_tiny.png 15:22  Feature request DJPYD-7 - Update application for use in Django 1.8, 1.9, and Django 1.10
branko (branko):
Issue closed
Status changed: New ⇒ Closed
Percent completed: 0% ⇒ 100
Resolution changed: Not determined ⇒ RESOLVED
enhancement_tiny.png 15:07  Enhancement DJPYD-8 - Update Pydenticon requirement to version 0.3
branko (branko):
Issue created
Since Pydenticon 0.3 version has been released, it would be useful to mark Django Pydenticon explicitly dependant on that version of Pydenticon library, and to update instructions on how to use the new ability to use transparency.
'Core' added
November 30, 2016
feature_request_tiny.png 22:16  Feature request DJPYD-7 - Update application for use in Django 1.8, 1.9, and Django 1.10
branko (branko):
Issue created
Starting with Django 1.9, use of `django.conf.urls.patterns()` has been deprecated, and it was finally removed in Django 1.10. This results in application being unusable under Django 1.10.

Application should be updated to use new way of specifying the URLs which is supported at least as early as Django 1.8 (which is the current LTS).

The following should be done:

- Update urls.py accordingly to pull request opened at [Github mirroir](https://github.com/azaghal/django-pydenticon/pull/2 "Github").
- Update minimum Django requirements to 1.8 in `setup.py`.
'Core' added
feature_request_tiny.png 22:08  Feature request DJPYD-3 - Initial tests
branko (branko):
Target milestone changed: 0.1.1 ⇒ 0.3
August 16, 2016
task_tiny.png 16:00  Task DJPYD-6 - Update links in configuration.rst to use correct domain for external documentation
branko (branko):
Issue created
Due to changes in readthedocs.org website, the documentation is now hosted on different domain - readthedocs.io. All links in **configuration.rst** should be updated to reflect this.
January 20, 2016
icon_milestone.png 00:45 0.1
A new milestone has been reached
January 22, 2014
feature_request_tiny.png 21:38  Feature request DJPYD-2 - Initial documentation
branko (branko):
Issue closed
Status changed: New ⇒ Closed
Percent completed: 0% ⇒ 100%
Resolution changed: Not determined ⇒ RESOLVED
feature_request_tiny.png 21:16  Feature request DJPYD-1 - Initial implementation
branko (branko):
Issue closed
Status changed: New ⇒ Closed
Percent completed: 0% ⇒ 100%
Resolution changed: Not determined ⇒ RESOLVED
January 20, 2014
icon_build.png 10:39 Django Pydenticon 0.1
New version released
November 30, 2013
feature_request_tiny.png 20:44  Feature request DJPYD-4 - Custom template tag for rendering identicon URL
branko (branko):
Target milestone changed: Not determined ⇒ 0.2
feature_request_tiny.png 20:44  Feature request DJPYD-5 - Substitute real data with randomly generated data for identicon hash generation
branko (branko):
Target milestone changed: Not determined ⇒ 0.2
feature_request_tiny.png 20:43  Feature request DJPYD-5 - Substitute real data with randomly generated data for identicon hash generation
branko (branko):
Issue created
It would be useful to implement a simple mechanism (may require a model as well) that can be easily used for using random data for identicon hash instead of the original data being passed. This would include:

* Option to turn on and off such behaviour.
* Every time an identicon URL is requested for raw data, random data will be used as a hash.
* When random data is generated, then it will be mapped to raw data via database model for future (re)use.

The tricky part will be how to store the raw data in database. It may be necessary to have something a bit more complex (foreign key to some other model, and name of that model's property that's supposed to be tied-in to random data).
'Core' added
feature_request_tiny.png 20:38  Feature request DJPYD-4 - Custom template tag for rendering identicon URL
branko (branko):
Issue created
A custom template tag should be implemented for rendering an identicon URL. The tag should probably accept the following parameters:

* Width and height of image.
* Padding.
* Output format.
* Inversion of foreground and background colours.

If no parameters are provided, defaults configured for the application should be used.
'Core' added
feature_request_tiny.png 20:33  Feature request DJPYD-3 - Initial tests
branko (branko):
Target milestone changed: Not determined ⇒ 0.1.1
feature_request_tiny.png 20:33  Feature request DJPYD-1 - Initial implementation
branko (branko):
Target milestone changed: Not determined ⇒ 0.1
feature_request_tiny.png 20:33  Feature request DJPYD-2 - Initial documentation
branko (branko):
Target milestone changed: Not determined ⇒ 0.1