-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[17.0][MIG] web_timeline: Migration to 17.0 #2874
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Avoid to display all items of group_by model * Remove unnecessary readgroup * Remove dependency on project. Modify module structure. Imporve readme file. * Add setup.py
* [FIX] Correct write when grouped by * Remove blank lines * Minor changes
* Update the vis.js framework to latest stable version (v4.20.1) to add new functionality and save almost 400ko of source code in odoo assets (the vis dev team has isolate the code for timeline widget from the rest of their widgets) * Add the possibility to display events with no duration (instantaneous) as the same time has regular events * Add the possibility to choose between two scroll mode : - zoom in time resolution (default) or - vertical scroll (web browser default behaviour) Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
…same as base Calendar view) In Odoo calendar view, the attribute date_delay is an alternative to date_stop, to provides the duration of the event instead of its end date. This commit integrate this attribute to the Timeline view, but contrary to the base Calendar view the Timeline view could use both arguments (date_stop and date_delay) simultaneously. Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
The default window display all the events (aka 'fit'), in case of events spread over the year, the events are invisibles (too small to be readable) Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
Change the attribute 'default_window' to 'mode' like the Odoo calendar view (to be iso functional)
CSS classes have changed with the updated version of vis.js
* Update Version in Manifest * Remove enconding in .py files * Rewrite the view definition according to version 11
[IMP] web_timeline: Templates implementation like kanban [ADD] Check if template exists Update README.rst
[UPD] Version number [UPD] README
Update README.rst [FIX] Remove console.log [ADD] Make timeline.fit optional [FIX] Use stringified points [IMP] Reversed the arrow head and fixed lint issues [IMP] Use options parameter for line color and width [FIX] Version number [IMP] Minor improvements
[IMP] Prevent flickering [IMP] Fixed headers [ADD] Create new record by date range selection Remove roadmap item from readme [FIX] minimal height
[FIX] web_timeline: Reloading view [FIX] web_timeline: Reloading view
Currently translated at 100.0% (13 of 13 strings) Translation: web-16.0/web-16.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_timeline/tr/
Currently translated at 100.0% (13 of 13 strings) Translation: web-16.0/web-16.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_timeline/hr/
On library version update a new feature was added at Timeline creation level to allow modifying the xss. By keeping it active the css classes are not showed As the view is on backend, has no sense to keep it active. So we deactivate the feature to allow show the timeline correctly. TT43238
…e (cannot be null)
Currently translated at 100.0% (13 of 13 strings) Translation: web-16.0/web-16.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_timeline/es/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: web-16.0/web-16.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_timeline/
Currently translated at 100.0% (13 of 13 strings) Translation: web-16.0/web-16.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_timeline/pt_BR/
Currently translated at 100.0% (13 of 13 strings) Translation: web-16.0/web-16.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_timeline/it/
Currently translated at 100.0% (13 of 13 strings) Translation: web-16.0/web-16.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_timeline/fr/
By contract the first argument of the `fields_get` method is supposed to be a list. Before this fix, `web_timeline` would call `fields_get` with a string instead of a list. Fortunately in case only 1 field is being grouped, this worked as Odoo does an `x in y` comparison in its `fields_get` implementation, which does pass in a simple `"project_id" in "project_id"` case. But that call remains invalid and can break when `fields_get` has been tweaked by other modules.
This way we can showcase this module without project_timeline.
When an item label does not fit in its date-range box, overflow according to https://visjs.github.io/vis-timeline/examples/timeline/items/rangeOverflowItem.html Previous CSS code was already trying to do that, but was selecting `.vis-item.vis-item-content` instead of `.vis-item .vis-item-content`. Displaying overflow text brings up layout issues solved by removing the forced-100% width instruction. This change also adds highlight when hovering a box, which is useful on text that has overflown (as it has no borders).
This avoids somewhat ugly very large "Unassigned" first row.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.