Merge branch 'mail-addons-9.0-res_partner_mails_count' of github.com:yelizariev/addons-dev into mail-addons-9.0-res_partner_mails_count

Conflicts:
	README.md
	res_partner_mails_count/README.rst
	res_partner_mails_count/__openerp__.py
	res_partner_mails_count/models.py
	res_partner_mails_count/static/src/js/main.js
	res_partner_mails_count/templates.xml
	res_partner_mails_count/views/res_partner_mails_count.xml

LICENSE

@@ -0,0 +1,166 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
+

README.md

@@ -1,64 +1,14 @@
-# addons-dev
-
-Addons Forge
-
-# Initialization
-
-1. Fork this repo
-2. Clone to your machine:
-
-        git clone git@github.com:USERNAME/addons-dev.git
-
-3. Add remotes
-
-        cd addons-dev
-
-        git remote add upstream          git@github.com:yelizariev/addons-dev.git
-        git remote add addons-yelizariev https://github.com/yelizariev/addons-yelizariev.git
-        git remote add pos-addons        https://github.com/yelizariev/pos-addons.git
-        git remote add mail-addons       https://github.com/yelizariev/mail-addons.git
-        git remote add access-addons     https://github.com/yelizariev/access-addons.git
-        git remote add website-addons    https://github.com/yelizariev/website-addons.git
-        git remote add l10n-addons       https://github.com/yelizariev/l10n-addons.git
-
-# Create new branch
-*(push access is needed)*
-
-    # specify target repo and branch:
-    export REPO=addons-yelizariev BRANCH=9.0 FEATURE=some-feature
-
-    # fetch remote
-    git fetch ${REPO}
-
-    # create new branch
-    git checkout -b ${REPO}-${BRANCH}-${FEATURE} ${REPO}/${BRANCH}
-
-    # push to upstream
-    git push upstream ${REPO}-${BRANCH}-${FEATURE}
-    
-    #
-
-# PR to existed branch
-
-If branch (e.g. *addons-yelizariev-9.0-some-feature*) already exists in **addons-dev**, send commits to your fork first and then create PR to **addons-dev**
-
-    git push origin addons-yelizariev-9.0-some-feature
-
-# Final PR to target repo
-
-    # example for addons-yelizariev
-    cd /path/to/addons-yelizariev
-
-    # add remote if it doesn't exist yet
-    git remote add addons-dev https://github.com/yelizariev/addons-dev.git
-
-    # fetch remote
-    git fetch addons-dev
-
-    # create branch
-    git checkout -b 9.0-some-feature addons-dev/addons-yelizariev-9.0-some-feature
-
-    # push to your fork of target repo
-    git push origin 9.0-some-feature
-
-    # create PR to target repo
+# mail-addons
+Odoo (OpenERP) mail addons
+
+List of repositories:
+---------------------
+
+* https://github.com/yelizariev/addons-yelizariev
+* https://github.com/yelizariev/pos-addons
+* https://github.com/yelizariev/mail-addons
+* https://github.com/yelizariev/rental-addons
+* https://github.com/yelizariev/access-addons
+* https://github.com/yelizariev/website-addons
+* https://github.com/yelizariev/l10n-addons
+* https://github.com/yelizariev/odoo-saas-tools

res_partner_mails_count/__openerp__.py

@@ -1,33 +1,28 @@
 # -*- coding: utf-8 -*-
 {
-    "name": "Smart buttons for mails count",
-
-    "summary": """
-        This module adds Smart buttons with "Mails from" and "Mails to" count of mails in the partner form.
-    """,
-
-    "description": """
-        You can see Smart buttons "Mails from" and "Mails to" in the contact
-        form in the Messaging/Contacts menu. If you click on these buttons,
-        you can see list of corresponded mails. Click on the "Send a message"
-        link to send mail to the partner.
-    """,
-
-    "author": "IT-Projects LLC, Pavel Romanchenko",
-    "website": "http://www.it-projects.info",
-
-    # Categories can be used to filter modules in modules listing
-    # Check https://github.com/odoo/odoo/blob/master/openerp/addons/base/module/module_data.xml
-    # for the full list
-    "category": "Uncategorized",
+    "name": """Partner mails count""",
+    "summary": """Displays amount of incoming and outgoing partner mails.""",
+    "category": "Sales Management",
+    "images": ['images/1.png'],
     "version": "1.0.0",
 
-    # any module necessary for this one to work correctly
-    "depends": ["base", "mail"],
+    "author": "IT-Projects LLC",
+    "website": "https://it-projects.info",
+    "license": "GPL-3",
+    "price": 30.00,
+    "currency": "EUR",
 
-    # always loaded
+    "depends": [
+        'base',
+        'mail' ,
+    ],
+    "external_dependencies": {"python": [], "bin": []},
     "data": [
-        "views/res_partner_mails_count.xml",
-        "templates.xml",
+        'views/res_partner_mails_count.xml',
+        'templates.xml',
+    ],
+    "demo": [
     ],
+    "installable": True,
+    "auto_install": False,
 }

res_partner_mails_count/static/description/index.html

@@ -0,0 +1,21 @@
+<section class="oe_container">
+    <div class="oe_row oe_spaced">
+        <div class="oe_span12">
+            <h2 class="oe_slogan">Smart buttons for mails count</h2>
+            <h3 class="oe_slogan">Display amount of messages from/to customer</h3>
+            <p>
+                Open partner (customer) form and look up how many messages he got and sent:
+                <img class="oe_picture oe_screenshot" src="1.png"/>
+            </p> 
+            <p>
+                If you click any of this buttons:
+                <img class="oe_picture oe_screenshot" src="2.png"/>
+            </p>
+            <p>
+                You will see those mails:
+                <img class="oe_picture oe_screenshot" src="3.png"/>
+            </p>
+        </div>
+
+    </div>
+</section>

res_partner_mails_count/static/src/js/main.js

@@ -1,16 +1,10 @@
-// openerp.res_partner_mails_count = function(instance){
-//     instance.mail.Wall.include({
-//         init: function(){
-//             this._super.apply(this, arguments);
-//             if(this.context.ignore_search_model){
-//                 delete this.defaults.model;
-//             }
-//         }
-//     });
-// };
-
-
-// odoo.define('res_partner_mails_count.main', function(require) {
-//     "use strict";
-//
-// });
+openerp.res_partner_mails_count = function(instance){
+	instance.mail.Wall.include({
+		init: function(){
+			this._super.apply(this, arguments);
+			if(this.context.ignore_search_model){
+				delete this.defaults.model;
+			}
+		}
+	});
+};