Code

Changes between Version 27 and Version 28 of SessionMessages


Ignore:
Timestamp:
10/13/09 16:29:09 (5 years ago)
Author:
tobias
Comment:

add descriptions of message classes

Legend:

Unmodified
Added
Removed
Modified
  • SessionMessages

    v27 v28  
    8888}}} 
    8989 
     90=== Pre-configured Message Classes/Levels === 
     91 
     92Custom message classes may be easily configured for any type of message that does not fit into the pre-set classes, or where more granularity is needed.  Consistency is needed regarding what a given class of message means, because multiple, independent Django apps may be combined to form a single project, and consistency is desired in the display of user feedback.  It is recommended that reusable apps do not use custom message classes. 
     93 
     94 * DEBUG: Development-related messages that will be removed before a production deployment 
     95 * INFO: Informational messages for the user 
     96 * SUCCESS: An action was successful, e.g. "Your profile was updated successfully" 
     97 * WARNING: A failure did not occur but may be imminent 
     98 * ERROR: An action was '''not''' successful or some other failure occurred 
     99 
    90100=== django-notify === 
    91101django-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.