backend, frontends: message refactoring (huge commit): /!\ several features are temporarily disabled, like notifications in frontends next step in refactoring, with the following changes: - jp: updated jp message to follow changes in backend/bridge - jp: added --lang, --subject, --subject_lang, and --type options to jp message + fixed unicode handling for jid - quick_frontend (QuickApp, QuickChat): - follow backend changes - refactored chat, message are now handled in OrderedDict and uid are kept so they can be updated - Message and Occupant classes handle metadata, so frontend just have to display them - Primitivus (Chat): - follow backend/QuickFrontend changes - info & standard messages are handled in the same MessageWidget class - improved/simplified handling of messages, removed update() method - user joined/left messages are merged when next to each other - a separator is shown when message is received while widget is out of focus, so user can quickly see the new messages - affiliation/role are shown (in a basic way for now) in occupants panel - removed "/me" messages handling, as it will be done by a backend plugin - message language is displayed when available (only one language per message for now) - fixed :history and :search commands - core (constants): new constants for messages type, XML namespace, entity type - core: *Message methods renamed to follow new code sytle (e.g. sendMessageToBridge => messageSendToBridge) - core (messages handling): fixed handling of language - core (messages handling): mes_data['from'] and ['to'] are now jid.JID - core (core.xmpp): reorganised message methods, added getNick() method to client.roster - plugin text commands: fixed plugin and adapted to new messages behaviour. client is now used in arguments instead of profile - plugins: added information for cancellation reason in CancelError calls - plugin XEP-0045: various improvments, but this plugin still need work: - trigger is used to avoid message already handled by the plugin to be handled a second time - changed the way to handle history, the last message from DB is checked and we request only messages since this one, in seconds (thanks Poezio folks :)) - subject reception is waited before sending the roomJoined signal, this way we are sure that everything including history is ready - cmd_* method now follow the new convention with client instead of profile - roomUserJoined and roomUserLeft messages are removed, the events are now handled with info message with a "ROOM_USER_JOINED" info subtype - probably other forgotten stuffs :p

--- a/src/core/constants.py	Sun Jun 19 22:22:13 2016 +0200
+++ b/src/core/constants.py	Mon Jun 20 18:41:53 2016 +0200
@@ -82,6 +82,7 @@
     ENTITY_ALL_RESOURCES = '@ALL_RESOURCES@'
     ENTITY_MAIN_RESOURCE = '@MAIN_RESOURCE@'
     ENTITY_CAP_HASH = 'CAP_HASH'
+    ENTITY_TYPE = 'TYPE'
 
 
     ## Roster jids selection ##
@@ -98,6 +99,11 @@
     MESS_TYPE_GROUPCHAT = 'groupchat'
     MESS_TYPE_HEADLINE = 'headline'
     MESS_TYPE_NORMAL = 'normal'
+    MESS_TYPE_AUTO = 'auto'  # magic value to let the backend guess the type
+    MESS_TYPE_STANDARD = (MESS_TYPE_CHAT, MESS_TYPE_ERROR, MESS_TYPE_GROUPCHAT, MESS_TYPE_HEADLINE, MESS_TYPE_NORMAL)
+    MESS_TYPE_ALL = MESS_TYPE_STANDARD + (MESS_TYPE_INFO, MESS_TYPE_AUTO)
+
+    MESS_EXTRA_INFO = "info_type"
 
 
     ## Presence ##
@@ -113,6 +119,7 @@
 
 
     ## Common namespaces ##
+    NS_XML = 'http://www.w3.org/XML/1998/namespace'
     NS_CLIENT = 'jabber:client'
     NS_FORWARD = 'urn:xmpp:forward:0'
     NS_DELAY = 'urn:xmpp:delay'