Permalink
Browse files

Changing Django Uni-Form to django-uni-form

  • Loading branch information...
1 parent 491ba21 commit 1a91a89045700d9a284a2c16f8f41399b7debc81 @pydanny pydanny committed Apr 17, 2010
View
@@ -12,7 +12,7 @@ For 0.8.0
* Incorporated uni-form 1.4 by Dragan Babic
* Provide better adherence to uni-form specification of error messages
* mirumee provided some great work for making FormHelper more subclassable.
- * Django Uni-Form 0.8 and higher lays out the HTML for the uni_form tag differently. The errorMsg div is now outside the fieldset as it should be.
+ * django-uni-form 0.8 and higher lays out the HTML for the uni_form tag differently. The errorMsg div is now outside the fieldset as it should be.
* Thanks to Casper S. Jensen django-uni-form now supports 1.2 style csrf_token.
* csrf_token does not break earlier versions of Django. This will change when no version of django does not support csrf_token.
View
@@ -1,4 +1,4 @@
-Django Uni-Form Project Lead
+django-uni-form Project Lead
============================
Daniel Greenfeld <pydanny@gmail.com>
View
@@ -1,5 +1,5 @@
=====================================
-django-uni-form (Django Uni-Form)
+django-uni-form (django-uni-form)
=====================================
Django_ forms are easily rendered as tables,
@@ -10,9 +10,9 @@ format.
`Uni-form`_ has been selected as the base model for the design of the forms.
-**Note:** Django Uni-Form 0.8 and higher lays out the HTML for the uni_form tag differently. The errorMsg div is now outside the fieldset as it should be.
+**Note:** django-uni-form 0.8 and higher lays out the HTML for the uni_form tag differently. The errorMsg div is now outside the fieldset as it should be.
-**Note:** Django Uni-Form 0.7 and higher breaks backwards compatibility with previous versions of Django Uni-Form. All you have to do is update templates that call on the Django Uni-Form template tag from::
+**Note:** django-uni-form 0.7 and higher breaks backwards compatibility with previous versions of django-uni-form. All you have to do is update templates that call on the django-uni-form template tag from::
{% load uni_form %}
@@ -53,7 +53,7 @@ media folder::
Displaying the media files
~~~~~~~~~~~~~~~~~~~~~~~~~~
-Django Uni-Form requires three media files. You can see how we call them by looking in the templates/includes.html file. You can call those files in several ways:
+django-uni-form requires three media files. You can see how we call them by looking in the templates/includes.html file. You can call those files in several ways:
1. Manually by copying the HTML into your own templates::
@@ -69,7 +69,7 @@ Django Uni-Form requires three media files. You can see how we call them by loo
{% include "uni_form/includes.html" %}
-4. With some additional setup described below, via use of the Django Uni-Form **uni_form_setup** template tag.
+4. With some additional setup described below, via use of the django-uni-form **uni_form_setup** template tag.
{% uni_form_setup %}
@@ -83,7 +83,7 @@ If you want to take advantage of the uni_form_setup tag, then you'll need to mak
Customizations on '*' required fields (optional)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-If you don't like the use of '*' (asterisk) to denote required fields you can simply overrride the Django Uni-Form field.html. In your Django project's templates directory create a new directory called `uni_form`. Copy the Django Uni-Form field.html file to that directory and make the desired changes. For example::
+If you don't like the use of '*' (asterisk) to denote required fields you can simply overrride the django-uni-form field.html. In your Django project's templates directory create a new directory called `uni_form`. Copy the django-uni-form field.html file to that directory and make the desired changes. For example::
cd ~/<my-projects>/<my-awesome-django-project>/templates/
mkdir uni_form
@@ -95,7 +95,7 @@ Now you could change the asterisk to any other character, an image icon, or what
Using Uni-Form strict fields
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Django Uni-Form implements form fields in html differently than the standard Uni-Form. If you want to adhere to the strict definition of Django Uni-Form relplace the field.html file with field.strict.html. You can just follow these instructions::
+django-uni-form implements form fields in html differently than the standard Uni-Form. If you want to adhere to the strict definition of django-uni-form relplace the field.html file with field.strict.html. You can just follow these instructions::
cd ~/<my-projects>/<my-awesome-django-project>/templates/
mkdir uni_form
@@ -3,7 +3,7 @@
You can adapt this file completely to your liking, but it should at least
contain the root `toctree` directive.
-django-uni-form (Django Uni-Form)
+django-uni-form (django-uni-form)
=======================================
Django_ forms are easily rendered as tables,
@@ -14,7 +14,7 @@ format.
`Uni-form`_ has been selected as the base model for the design of the forms.
-Django Uni-Form lets you easily display Django forms as divs.
+django-uni-form lets you easily display Django forms as divs.
.. _Django: http://djangoproject.com
View
@@ -3,7 +3,7 @@
You can adapt this file completely to your liking, but it should at least
contain the root `toctree` directive.
-django-uni-form (Django Uni-Form)
+django-uni-form (django-uni-form)
=======================================
Django_ forms are easily rendered as tables,
@@ -14,7 +14,7 @@ format.
`Uni-form`_ has been selected as the base model for the design of the forms.
-Django Uni-Form lets you easily display Django forms as divs.
+django-uni-form lets you easily display Django forms as divs.
.. _Django: http://djangoproject.com
View
@@ -13,18 +13,8 @@
provide a simple tag and/or filter that lets you quickly render forms in a div
format.
-Uni-form (http://sprawsm.com/uni-form) has been selected as the base model for
+Uni-form (http://sprawsm.com/uni-form) has been selected as css/js library for
the design of the forms.
-
-This release includes:
-
- * Removed a <hr /> from the layout module.
- * Changed templatetags/uni_form.py to templatetags/uni_form_tags.py. Yes, this breaks backwards compatibility but fixes a namespace problems in Django with naming a templatetag library after the parent application.
- * Changed form_action attribute to accept not just named URLs but also any old URL.
- * Added in uni_form_setup tag.
- * Added tests
- * Added several new contributors including Dragan Babic
- * Added Danish language translation
"""
setup(
@@ -3,7 +3,7 @@
{% block body%}
<h1>
- Django Uni-Form form helper test
+ form helper test
</h1>
{% with form.helper as helper %}
@@ -3,7 +3,7 @@
{% block body%}
<h1>
- Django Uni-Form view layout test
+ view layout test
</h1>
{% with form.helper as helper %}
@@ -3,7 +3,7 @@
{% block body%}
<h1>
- Django Uni-Form basic tests
+ basic tests
</h1>
<form method="POST" action="" class="uniForm">
@@ -3,7 +3,7 @@
{% block body%}
<h1>
- Django Uni-Form view helper test
+ view helper test
</h1>
{% uni_form form helper %}

0 comments on commit 1a91a89

Please sign in to comment.