学习 | Odoo Connects Everything

odoo tree view link text url widget

原生列表视图的url组件会将链接也显式的填充到字段列，如果遇到该字段的链接特别长且参数众多，表格就会撑的很难看，这就需要量身为其定制一种纯显示链接文字的widget：

var core = require('web.core');
var list_widget_registry = core.list_widget_registry;
var _t = core._t;
/**
 * author: i@renjie.me
 */
var Column = list_widget_registry.get('field');
var ColumnLink = Column.extend({
    PROTOCOL_REGEX: /^(?!\w+:?\/\/)/,
    _format: function(row_data, options) {
        var value = row_data[this.id].value;
        if (value) {
            return _.template("<a href='<%-href%>' target='_blank'><%-text%></a>")({
                href: value.trim().replace(this.PROTOCOL_REGEX, '//'),
                text: _t("Link")
            });
        }
        return this._super(row_data, options);
    }
});
list_widget_registry.add('field.link', ColumnLink);

var core = require('web.core');

var list_widget_registry = core.list_widget_registry;

var _t = core._t;

/**

* author: i@renjie.me

var Column = list_widget_registry.get('field');

var ColumnLink = Column.extend({

PROTOCOL_REGEX: /^(?!\w+:?\/\/)/,

_format: function(row_data, options) {

var value = row_data[this.id].value;

if (value) {

return _.template("<a href='<%-href%>' target='_blank'><%-text%></a>")({

href: value.trim().replace(this.PROTOCOL_REGEX, '//'),

text: _t("Link")

});

}

return this._super(row_data, options);

}

});

list_widget_registry.add('field.link', ColumnLink);

之后就可以在列表视图中直接使用诸如<field name=”content_url” widget=”link”/>形式的链接文字字段组件

odoo search view default show filters advanced menu

odoo搜索视图默认是隐藏高级搜索菜单栏，虽然可以打开记住状态，但换台电脑或浏览器默认又是关闭，这就需要改变其缺省机制，源码如下：

var SearchView = require('web.SearchView');
SearchView.include({
    init: function () {
        var self = this;
        self._super.apply(self, arguments);
        self.visible_filters = (localStorage.visible_search_menu !== 'false');
    }
});

var SearchView = require('web.SearchView');

SearchView.include({

init: function () {

var self = this;

self._super.apply(self, arguments);

self.visible_filters = (localStorage.visible_search_menu !== 'false');

}

});

python decompress http response gzip and deflate Content-Encoding

deflate与gzip解压的方法几乎相同，源码如下：

import zlib
import urllib2

def get_url_content(url):
    headers = {
        'Accept-Encoding': 'gzip, deflate',
    }
    response = urllib2.urlopen(urllib2.Request(url, headers=headers))
    content = response.read()
    content_encode = response.info().get('Content-Encoding')
    if content_encode == 'gzip':
        content = zlib.decompress(content, zlib.MAX_WBITS|16)
    elif content_encode == 'deflate':
        content = zlib.decompress(content, -zlib.MAX_WBITS)
    return content

import zlib

import urllib2

def get_url_content(url):

headers = {

'Accept-Encoding': 'gzip, deflate',

}

response = urllib2.urlopen(urllib2.Request(url, headers=headers))

content = response.read()

content_encode = response.info().get('Content-Encoding')

if content_encode == 'gzip':

content = zlib.decompress(content, zlib.MAX_WBITS|16)

elif content_encode == 'deflate':

content = zlib.decompress(content, -zlib.MAX_WBITS)

return content

odoo disabled website homepage

odoo有些模块包含website功能，这就依赖了website这个重量级模块
很多时候仅仅想用其核心功能，并不想因此造成首页变成企业网站

# -*- coding: utf-8 -*-
import logging

from openerp import http
from openerp.http import request
from openerp.addons.website.controllers.main import Website

logger = logging.getLogger(__name__)

class WebsiteDisabled(Website):
    @http.route(auth="none", website=False)
    def index(self, **kw):
        return http.local_redirect('/web', query=request.params, keep_hash=True)

# -*- coding: utf-8 -*-

import logging

from openerp import http

from openerp.http import request

from openerp.addons.website.controllers.main import Website

logger = logging.getLogger(__name__)

class WebsiteDisabled(Website):

@http.route(auth="none", website=False)

def index(self, **kw):

return http.local_redirect('/web', query=request.params, keep_hash=True)

python ldap userPassword salt sha md5 encrypt

odoo自带的auth_ldap模块虽然实现了ldap统一账户的验证，但如果用户一旦修改密码就变成同名的本地用户。这是因为odoo默认先验证本地res.users信息，如果没有记录，或者有记录但密码字段为空才会去ldap服务器验证

根据其原理，可以在修改密码的时候对接上ldap的密码信息就完美了，但用modify指令写入的userPassword值是原文存储，即明文直接写入在服务器也是明文，这就需要在请求端预先加密成ldap标准的密文格式

网上看到有很多php的实现都是要写点代码什么的，照葫芦折腾几下才发现python的passlib库居然有现成拿来即用的函数

>>> from passlib.hash import ldap_salted_sha1 as ssha
>>> ssha.encrypt("test", salt_size=16)
'{SSHA}tiULq3HOY1XRLW+bjGkHe3awnZCHcE5JSam1tnaOce49B4Dw'

>>> from passlib.hash import ldap_salted_sha1 as ssha

>>> ssha.encrypt("test", salt_size=16)

'{SSHA}tiULq3HOY1XRLW+bjGkHe3awnZCHcE5JSam1tnaOce49B4Dw'

以此类推

>>> import passlib.hash
>>> dir(passlib.hash)
['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__format__', '__getattr__', '__getattribute__', '__hash__', '__init__', '__module__', '__name__', '__new__', '__package__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'apr_md5_crypt', 'atlassian_pbkdf2_sha1', 'bcrypt', 'bcrypt_sha256', 'bigcrypt', 'bsd_nthash', 'bsdi_crypt', 'cisco_pix', 'cisco_type7', 'crypt16', 'cta_pbkdf2_sha1', 'des_crypt', 'django_bcrypt', 'django_bcrypt_sha256', 'django_des_crypt', 'django_disabled', 'django_pbkdf2_sha1', 'django_pbkdf2_sha256', 'django_salted_md5', 'django_salted_sha1', 'dlitz_pbkdf2_sha1', 'fshp', 'grub_pbkdf2_sha512', 'hex_md4', 'hex_md5', 'hex_sha1', 'hex_sha256', 'hex_sha512', 'htdigest', 'ldap_bcrypt', 'ldap_bsdi_crypt', 'ldap_des_crypt', 'ldap_hex_md5', 'ldap_hex_sha1', 'ldap_md5', 'ldap_md5_crypt', 'ldap_pbkdf2_sha1', 'ldap_pbkdf2_sha256', 'ldap_pbkdf2_sha512', 'ldap_plaintext', 'ldap_salted_md5', 'ldap_salted_sha1', 'ldap_sha1', 'ldap_sha1_crypt', 'ldap_sha256_crypt', 'ldap_sha512_crypt', 'lmhash', 'md5_crypt', 'msdcc', 'msdcc2', 'mssql2000', 'mssql2005', 'mysql323', 'mysql41', 'nthash', 'oracle10', 'oracle11', 'pbkdf2_sha1', 'pbkdf2_sha256', 'pbkdf2_sha512', 'phpass', 'plaintext', 'postgres_md5', 'roundup_plaintext', 'scram', 'sha1_crypt', 'sha256_crypt', 'sha512_crypt', 'sun_md5_crypt', 'unix_disabled', 'unix_fallback']

>>> import passlib.hash

>>> dir(passlib.hash)

['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__format__', '__getattr__', '__getattribute__', '__hash__', '__init__', '__module__', '__name__', '__new__', '__package__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'apr_md5_crypt', 'atlassian_pbkdf2_sha1', 'bcrypt', 'bcrypt_sha256', 'bigcrypt', 'bsd_nthash', 'bsdi_crypt', 'cisco_pix', 'cisco_type7', 'crypt16', 'cta_pbkdf2_sha1', 'des_crypt', 'django_bcrypt', 'django_bcrypt_sha256', 'django_des_crypt', 'django_disabled', 'django_pbkdf2_sha1', 'django_pbkdf2_sha256', 'django_salted_md5', 'django_salted_sha1', 'dlitz_pbkdf2_sha1', 'fshp', 'grub_pbkdf2_sha512', 'hex_md4', 'hex_md5', 'hex_sha1', 'hex_sha256', 'hex_sha512', 'htdigest', 'ldap_bcrypt', 'ldap_bsdi_crypt', 'ldap_des_crypt', 'ldap_hex_md5', 'ldap_hex_sha1', 'ldap_md5', 'ldap_md5_crypt', 'ldap_pbkdf2_sha1', 'ldap_pbkdf2_sha256', 'ldap_pbkdf2_sha512', 'ldap_plaintext', 'ldap_salted_md5', 'ldap_salted_sha1', 'ldap_sha1', 'ldap_sha1_crypt', 'ldap_sha256_crypt', 'ldap_sha512_crypt', 'lmhash', 'md5_crypt', 'msdcc', 'msdcc2', 'mssql2000', 'mssql2005', 'mysql323', 'mysql41', 'nthash', 'oracle10', 'oracle11', 'pbkdf2_sha1', 'pbkdf2_sha256', 'pbkdf2_sha512', 'phpass', 'plaintext', 'postgres_md5', 'roundup_plaintext', 'scram', 'sha1_crypt', 'sha256_crypt', 'sha512_crypt', 'sun_md5_crypt', 'unix_disabled', 'unix_fallback']

其中ldap_bcrypt,ldap_bsdi_crypt,ldap_des_crypt,ldap_hex_md5,ldap_hex_sha1,ldap_md5,ldap_md5_crypt,ldap_pbkdf2_sha1,ldap_pbkdf2_sha256,ldap_pbkdf2_sha512,ldap_plaintext,ldap_salted_md5,ldap_salted_sha1,ldap_sha1,ldap_sha1_crypt,ldap_sha256_crypt,ldap_sha512_crypt等都是ldap加密相关的兄弟函数，可谓是应有尽有非常丰富，看来在odoo端直接集成phpLDAPadmin里各种类型的加密密码更新都是易事了

freeswitch http https ws wss nginx domain default port config

现代H5浏览器产业链越来越丰富，http+websocket+webrtc+sip组合已经是一种非常成熟的web原生音视频通讯解决方案

FreeSWITCH是一个开源的电话软交换平台，早在SIP年代就非常有名，自从支持WebSocket传输sip信令后与Web结合玩法多了许多

WebRTC提供了音视频通讯的核心技术，包括音视频的采集、编解码、网络传输、显示等功能，并且还支持跨平台，但就是没有信令协议部分

Chrome、Firefox等浏览器为了从保护用户隐私绝对安全角度考虑，纷纷提高了Web原生应用访问摄像头、麦克风的门槛：如不是用https、wss安全协议则会有各种警告及确认甚至直接拒绝

WS、WSS其实就是HTTP、HTTPS的WebSocket协议名称，其使用方式及默认端口都完全一致

综上所述，如果都用同一个域名地址承载web sip相关服务方便用户使用，就需要在nginx上做一些优雅的配置

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen       80;
    listen       443 ssl;
    root         /var/www/sip;

    proxy_read_timeout 3600;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;

    location / {
        if ($scheme = 'http') {
            set $ws_port 5066;
        }
        if ($scheme = 'https') {
            set $ws_port 7443;
        }
        if ($http_upgrade = 'websocket') {
            proxy_pass    $scheme://$server_addr:$ws_port;
        }
    }
}

map $http_upgrade $connection_upgrade {

default upgrade;

'' close;

}

server {

listen 80;

listen 443 ssl;

root /var/www/sip;

proxy_read_timeout 3600;

proxy_http_version 1.1;

proxy_set_header Upgrade $http_upgrade;

proxy_set_header Connection $connection_upgrade;

location / {

if ($scheme = 'http') {

set $ws_port 5066;

}

if ($scheme = 'https') {

set $ws_port 7443;

}

if ($http_upgrade = 'websocket') {

proxy_pass $scheme://$server_addr:$ws_port;

}

其对应freeswitch相关端口配置片断如下

<!-- Internal SIP Profile -->
<X-PRE-PROCESS cmd="set" data="internal_sip_port=5060"/>
<!-- RTP port range -->
<param name="rtp-start-port" value="16384"/>
<param name="rtp-end-port" value="32768"/>
<!-- for sip over websocket support -->
<param name="ws-binding"  value=":5066"/>
<!-- for sip over secure websocket support -->
<param name="wss-binding" value=":7443"/>

<X-PRE-PROCESS cmd="set" data="internal_sip_port=5060"/>

注：
sip和rtp端口不经nginx直连，但需要防火墙做相应的白名单
ws5066端口和wss7443端口间接通过nginx的http端口和https端口反向代理提供服务
nginx默认的http80端口和https443端口又用来提供webrtc前端相关资源访问

阿里云ecs部署freeswitch默认event socket listen port 8021 ipv6问题

阿里云ecs服务器目前还不支持ipv6
freeswitch默认event_socket模块配置
/etc/freeswitch/autoload_configs/event_socket.conf.xml

<configuration name="event_socket.conf" description="Socket Client">
  <settings>
    <param name="nat-map" value="false"/>
    <param name="listen-ip" value="::"/>
    <param name="listen-port" value="8021"/>
    <param name="password" value="ClueCon"/>
    <!--<param name="apply-inbound-acl" value="loopback.auto"/>-->
    <!--<param name="stop-on-bind-error" value="true"/>-->
  </settings>
</configuration>

</settings>

</configuration>

里的<param name=”listen-ip” value=”::”/>是ipv6地址的表现形式，其等同于ipv4的0.0.0.0
这就造成服务启动后，由于无法绑定ipv6地址，也就不能通过fs_cli命令行进行控制台管理了
这就解释了同样的配置在本机一切正常，部署到阿里云上就无法管理

知道原理解决起来就简单了，将listen-ip的value根据实际需要改成127.0.0.1、0.0.0.0或内外网卡的ipv4地址即可

odoo addons xml develop debug auto update

odoo以开发者模式运行的话，能自动检测所有的addons目录的代码变动情况自动进行reload
这个机制对于python代码来说是够用的，但是对csv安全规则、xml数据及视图模版来说还需要更新模块才能使其生效

今天由于逐个测试安全规则条目，不断的手工更新模块不胜其烦，只好深入研究一下

odoo9开始已经将开发者模式依赖的pyinotify替换为watchdog，可能是后者的应用范围更广把，不仅提供python库，还附带shell工具

那就学习下这个叫watchmedo的命令行工具吧

(python)[srj@x1c odoo9]$ watchmedo --help
usage: watchmedo [-h] [--version]
                 
                 {tricks-from,tricks-generate-yaml,log,shell-command,auto-restart}
                 ...

positional arguments:
  {tricks-from,tricks-generate-yaml,log,shell-command,auto-restart}
    tricks-from         Subcommand to execute tricks from a tricks
                        configuration file. :param args: Command line argument
                        options.
    tricks-generate-yaml
                        Subcommand to generate Yaml configuration for tricks
                        named on the command line. :param args: Command line
                        argument options.
    log                 Subcommand to log file system events to the console.
                        :param args: Command line argument options.
    shell-command       Subcommand to execute shell commands in response to
                        file system events. :param args: Command line argument
                        options.
    auto-restart        Subcommand to start a long-running subprocess and
                        restart it on matched events. :param args: Command
                        line argument options.

optional arguments:
  -h, --help            show this help message and exit
  --version             show program's version number and exit

(python)[srj@x1c odoo9]$ watchmedo --help

usage: watchmedo [-h] [--version]

{tricks-from,tricks-generate-yaml,log,shell-command,auto-restart}

...

positional arguments:

{tricks-from,tricks-generate-yaml,log,shell-command,auto-restart}

tricks-from Subcommand to execute tricks from a tricks

configuration file. :param args: Command line argument

options.

tricks-generate-yaml

Subcommand to generate Yaml configuration for tricks

named on the command line. :param args: Command line

argument options.

log Subcommand to log file system events to the console.

:param args: Command line argument options.

shell-command Subcommand to execute shell commands in response to

file system events. :param args: Command line argument

options.

auto-restart Subcommand to start a long-running subprocess and

restart it on matched events. :param args: Command

line argument options.

optional arguments:

-h, --help show this help message and exit

--version show program's version number and exit

看到auto-restart参数后真是让人眼前一亮，根据提示继续学习二级参数

(python)[srj@x1c odoo9]$ watchmedo auto-restart -h
usage: watchmedo auto-restart [-h] [-d directory] [-p PATTERNS]
                              [-i IGNORE_PATTERNS] [-D] [-R]
                              [--interval TIMEOUT] [--signal SIGNAL]
                              [--kill-after KILL_AFTER]
                              command [arg [arg ...]]

    Subcommand to start a long-running subprocess and restart it
    on matched events.

    :param args:
        Command line argument options.
    

positional arguments:
  command               Long-running command to run in a subprocess.
  arg                   Command arguments. Note: Use -- before the command
                        arguments, otherwise watchmedo will try to interpret
                        them. (default: -)

optional arguments:
  -h, --help            show this help message and exit
  -d directory, --directory directory
                        Directory to watch. Use another -d or --directory
                        option for each directory. (default: -)
  -p PATTERNS, --pattern PATTERNS, --patterns PATTERNS
                        matches event paths with these patterns (separated by
                        ;). (default: '*')
  -i IGNORE_PATTERNS, --ignore-pattern IGNORE_PATTERNS, --ignore-patterns IGNORE_PATTERNS
                        ignores event paths with these patterns (separated by
                        ;). (default: '')
  -D, --ignore-directories
                        ignores events for directories (default: False)
  -R, --recursive       monitors the directories recursively (default: False)
  --interval TIMEOUT, --timeout TIMEOUT
                        use this as the polling interval/blocking timeout
                        (default: 1.0)
  --signal SIGNAL       stop the subprocess with this signal (default SIGINT)
                        (default: 'SIGINT')
  --kill-after KILL_AFTER
                        when stopping, kill the subprocess after the specified
                        timeout (default 10) (default: 10.0)

(python)[srj@x1c odoo9]$ watchmedo auto-restart -h

usage: watchmedo auto-restart [-h] [-d directory] [-p PATTERNS]

[-i IGNORE_PATTERNS] [-D] [-R]

[--interval TIMEOUT] [--signal SIGNAL]

[--kill-after KILL_AFTER]

command [arg [arg ...]]

Subcommand to start a long-running subprocess and restart it

on matched events.

:param args:

Command line argument options.

positional arguments:

command Long-running command to run in a subprocess.

arg Command arguments. Note: Use -- before the command

arguments, otherwise watchmedo will try to interpret

them. (default: -)

optional arguments:

-h, --help show this help message and exit

-d directory, --directory directory

Directory to watch. Use another -d or --directory

option for each directory. (default: -)

-p PATTERNS, --pattern PATTERNS, --patterns PATTERNS

matches event paths with these patterns (separated by

;). (default: '*')

-i IGNORE_PATTERNS, --ignore-pattern IGNORE_PATTERNS, --ignore-patterns IGNORE_PATTERNS

ignores event paths with these patterns (separated by

;). (default: '')

-D, --ignore-directories

ignores events for directories (default: False)

-R, --recursive monitors the directories recursively (default: False)

--interval TIMEOUT, --timeout TIMEOUT

use this as the polling interval/blocking timeout

(default: 1.0)

--signal SIGNAL stop the subprocess with this signal (default SIGINT)

(default: 'SIGINT')

--kill-after KILL_AFTER

when stopping, kill the subprocess after the specified

timeout (default 10) (default: 10.0)

真是太强大了，本以为还要写点小代码什么的，没想到几个选项就可以灵活组合出一个小型的监控工具

watchmedo auto-restart -R -p="*.py;*.xml;*.csv" -d /home/srj/Git/Odoo/custom_addons/account_simple/ -- ./odoo.py -c c.conf -d test9 -u account_simple

1	watchmedo auto-restart -R -p=".py;.xml;*.csv" -d /home/srj/Git/Odoo/custom_addons/account_simple/ -- ./odoo.py -c c.conf -d test9 -u account_simple

-R是目录递归监控
-p是文件模式匹配，主要是排除前端资源和pyc
-d是指定监控目录
–是watchmedo与odoo各自的命令行参数分割线

至此odoo的模块开发效率又提高了一个层次：）

centos odoo decoder jpeg not available

云服务器上传jpg图片提示IOError错误

  File "/usr/lib64/python2.7/site-packages/PIL/ImageFile.py", line 200, in load
    d = Image._getdecoder(self.mode, d, a, self.decoderconfig)
  File "/usr/lib64/python2.7/site-packages/PIL/Image.py", line 417, in _getdecoder
    raise IOError("decoder %s not available" % decoder_name)
IOError: decoder jpeg not available

File "/usr/lib64/python2.7/site-packages/PIL/ImageFile.py", line 200, in load

d = Image._getdecoder(self.mode, d, a, self.decoderconfig)

File "/usr/lib64/python2.7/site-packages/PIL/Image.py", line 417, in _getdecoder

raise IOError("decoder %s not available" % decoder_name)

IOError: decoder jpeg not available

初步判断是python pil库依赖的底层jpeg lib问题
但是本机正常无法重现，于是检查环境

[srj@x1c ~]$ yum list installed|grep jpeg
libjpeg-turbo.x86_64               1.2.90-5.el7                        @anaconda
libjpeg-turbo-devel.x86_64         1.2.90-5.el7                        @anaconda
openjpeg-libs.x86_64               1.5.1-10.el7                        @anaconda

[srj@x1c ~]$ yum list installed|grep jpeg

libjpeg-turbo.x86_64 1.2.90-5.el7 @anaconda

libjpeg-turbo-devel.x86_64 1.2.90-5.el7 @anaconda

openjpeg-libs.x86_64 1.5.1-10.el7 @anaconda

对比了下发现服务器环境没有libjpeg-turbo-devel.x86_64立马补装一个，重启odoo服务错误依旧，于是继续更新Pillow库

[root@demo ~]# pip install --upgrade Pillow
Collecting Pillow
  Downloading Pillow-3.1.0.tar.gz (9.9MB)
    100% |████████████████████████████████| 9.9MB 42kB/s 
Installing collected packages: Pillow
  Found existing installation: Pillow 2.7.0
    Uninstalling Pillow-2.7.0:
      Successfully uninstalled Pillow-2.7.0
  Running setup.py install for Pillow
Successfully installed Pillow-3.1.0

[root@demo ~]# pip install --upgrade Pillow

Collecting Pillow

Downloading Pillow-3.1.0.tar.gz (9.9MB)

100% |████████████████████████████████| 9.9MB 42kB/s

Installing collected packages: Pillow

Found existing installation: Pillow 2.7.0

Uninstalling Pillow-2.7.0:

Successfully uninstalled Pillow-2.7.0

Running setup.py install for Pillow

Successfully installed Pillow-3.1.0

重启odoo服务问题解决
最后回顾了下odoo requirements.txt：
odoo8 Pillow==2.5.1
odoo9 Pillow==2.7.0
其实所谓更新无非是重新安装编译一下Pillow库，没想到直接升级到3.1.0版本，希望没有什么副作用：）

odoo Many2one field create use custom view open

odoo联系人相关的信息全部存储在res.partner对象里，包括供应商、客户、员工等个人及公司相关的信息都可以归纳入内

partner_id = fields.Many2one('res.partner', required=True)

1	partner_id = fields.Many2one('res.partner', required=True)

二次开发经常会直接关联该对象可以少造很多轮子，但由于其新建联系人的默认视图view_partner_form是一个非常重且包含好多类型设置又被各种业务模块继承扩展过的大视图，这就需要为不同的应用场景开发对应业务信息的轻量级自定义视图

最开始我是从继承res.partner并重写其@api.model的fields_view_get方法来完成的

@api.model
def fields_view_get(self, view_id=None, view_type=False, toolbar=False, submenu=False):
    def get_view_id(name):
        view = self.env['ir.ui.view'].search([('name', '=', name)], limit=1)
        if not view:
            return None
        return view.id
    context_view_name = self._context.get('view_name')
    if context_view_name:
        ##重置context指定视图
        view_id = get_view_id(context_view_name)
    return super(res_partner, self).fields_view_get(
        view_id=view_id, view_type=view_type, toolbar=toolbar, submenu=submenu)

@api.model

def fields_view_get(self, view_id=None, view_type=False, toolbar=False, submenu=False):

def get_view_id(name):

view = self.env['ir.ui.view'].search([('name', '=', name)], limit=1)

if not view:

return None

return view.id

context_view_name = self._context.get('view_name')

if context_view_name:

##重置context指定视图

view_id = get_view_id(context_view_name)

return super(res_partner, self).fields_view_get(

view_id=view_id, view_type=view_type, toolbar=toolbar, submenu=submenu)

使用很简单view context新增一个view_name属性指定自定义视图名称即可

<field name="partner_id" context="{'view_name': 'res.partner.daybook.form'}"/>

1	<field name="partner_id" context="{'view_name': 'res.partner.daybook.form'}"/>

当后来对其它对象也有同样需求的时候就基本确定我悲剧的造了一个小轮子
因为这个需求是非常合理，如果要一个个对象去继承重写是非常不实现的，至少也要在共同的父类上做对接
根据这个思路从openerp.osv.Model一直寻找到openerp.models.Model的fields_view_get父级方法，其中有一段代码让人眼前一亮

# try to find a view_id if none provided
if not view_id:
    # <view_type>_view_ref in context can be used to overrride the default view
    view_ref_key = view_type + '_view_ref'
    view_ref = context.get(view_ref_key)
    if view_ref:
        if '.' in view_ref:
            module, view_ref = view_ref.split('.', 1)
            cr.execute("SELECT res_id FROM ir_model_data WHERE model='ir.ui.view' AND module=%s AND name=%s", (module, view_ref))
            view_ref_res = cr.fetchone()
            if view_ref_res:
                view_id = view_ref_res[0]

# try to find a view_id if none provided

if not view_id:

# <view_type>_view_ref in context can be used to overrride the default view

view_ref_key = view_type + '_view_ref'

view_ref = context.get(view_ref_key)

if view_ref:

if '.' in view_ref:

module, view_ref = view_ref.split('.', 1)

cr.execute("SELECT res_id FROM ir_model_data WHERE model='ir.ui.view' AND module=%s AND name=%s", (module, view_ref))

view_ref_res = cr.fetchone()

if view_ref_res:

view_id = view_ref_res[0]

这不就是传说中解决分类自选视图的相关代码：类型、模块名、视图ID确定一个视图
马上删除之前所有相关代码，view context按如下规则修改直接应用

<field name="partner_id" context="{'form_view_ref': '模块名.视图ID'}"/>

1	<field name="partner_id" context="{'form_view_ref': '模块名.视图ID'}"/>

至此，对odoo一切都是models的理念又有了进一步的理解