[trunk - base_calendar] exrule field without functionality [IMP]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Confirmed
|
Wishlist
|
OpenERP R&D Addons Team 1 |
Bug Description
Hi,
I'm interesting in base_calendar module, it's great. I found some bugs.
For example the field exrule isn't implemented, this field is very useful because in dateutil rules you can set exceptions with a rule. I'm implemented this functionality with this field. I attached an improvement. Please take a look to file and maybe can improve my source, but the functionality it's ok and it's works.
If I set exrule fields to: FREQ=WEEKLY;
Maybe could create a wizard to set exrule field as custom rule wizard.
Then in my attachment I fixed a bug in compute_
summary: |
- [base_calendar] exrule field without functionality [IMP] + [trunk - base_calendar] exrule field without functionality [IMP] |
Changed in openobject-addons: | |
importance: | Undecided → Wishlist |
assignee: | nobody → rpa (Open ERP) (rpa-openerp) |
Changed in openobject-addons: | |
status: | New → In Progress |
Changed in openobject-addons: | |
status: | In Progress → Confirmed |
Changed in openobject-addons: | |
assignee: | rpa (Open ERP) (rpa-openerp) → nobody |
Changed in openobject-addons: | |
assignee: | nobody → OpenERP R&D Addons Team 1 (openerp-dev-addons1) |
Hi rpa,
I reattached the file with new improvements about read and search methods, please review the file because with large quantity of registries it only show in calendar view the 100 or default limit registries by date not filtered, now it uses the dates and recursion params calculating visible registries and then it was very slow in read because it was reading for each id and virtual id in read again all same data, now first read all data and then maps it and creates virtual ids.
Thanks