Changes between Version 19 and Version 20 of SessionMessages

Timestamp:

Oct 10, 2009, 12:59:06 PM (15 years ago)

Author:

Tobias McNulty

Comment:

potential messaging API

SessionMessages

@@ -64 +64 @@
 
 == Potential API ==
-django-notify is the current front-runner in terms of technical features so a sampling of the potential API is included below.  Feel free to include the API(s) of other solutions as well for comparison.  Discussion of the API should take place on the [http://groups.google.com/group/django-developers/browse_thread/thread/eba93088c649022b django-developers list].
+
+The API is under discussion on the [http://groups.google.com/group/django-developers/browse_thread/thread/eba93088c649022b django-developers list].  Following are a few different iterations of what it might look like:
+
+{{{
+from django.contrib import messages
+
+request.messages.add('message', messages.INFO)
+# or
+request.messages.add('message', classes=(messages.WARNING,))
+# or
+request.messages.error('message')
+}}}
+
+Using messages in your template:
+
+{{{
+{% if request.messages %}
+<ul class="messages">
+        {% for message in request.messages %}
+        <li{% if message.tags %} class="{{ message.tags }}"{% endif %}>{{ message }}</li>
+        {% endfor %}
+</ul>
+{% endif %}
+}}}
 
 === django-notify ===
+django-notify is the current front-runner in terms of technical features so a sampling of the potential API is included below.  Feel free to include the API(s) of other solutions as well for comparison.  It is understood that, should django-notify be chosen, this may (and probably will) change prior to inclusion in the core.
+
 Add the middleware to your MIDDLEWARE_CLASSES setting (after !SessionMiddleware):
 {{{