cd20b56693224e7f49ebffd44cb6fb0bf305990c
+7








cd20b56693
[REF] *:
Milk, webclient redesign
This pull request introduces an overall redesign that encompasses significant improvements in both usability and aesthetic. Codenamed "**milk**", the project's primary goal is to enhance the overall UX and provide a visually appealing interface that promotes intuitive interaction. ### Key Design Features: - **Improved use of `primary`color** Previously, **all** action buttons were indistinctly assigned `primary`, regardless of their importance in the user flow. The only exception were "_hyper-secondary_" actions, which were intentionally de-emphasized to the extent of being represented solely by text. However, this approach proved to be problematic for users since the UI failed to effectively guide them through the workflow. Now, each view has a limited number of primary buttons that serve as clear **call-to-action** elements. The design of secondary buttons has been enhanced to give them more prominence and visual weight. - **Control panel** The redesign employs a consistent and responsive layout that prioritise clarity and simplicity while maintaining the component original functionalities. The information hierarchy has been reviewed, ensuring that essential actions are prominently displayed, while less critical elements are appropriately de-emphasized. - **The new "_Cog Menu_"** It consolidates actions specific to the current entry only, streamlining the user interface by centralizing functionalities that were previously scattered (e.g., Archive/Import/Export).  - **Font-size Enhancement** The base font-size has been increased from `13px` to `14px` across the entire UI. This enhancement significantly improves readability, ensuring that text content is more legible and accessible to users. Moreover, the rendering of `fa` icons achieves now optimal clarity since were initially designed on a `14px` font-size base. Furthermore, the `oi` icons have also been updated to the new font-size. Although this change may seem small, it has significant consequences on the overall visual appearance, as spacing needs to be adjusted accordingly. While we are considering allowing users to customize these options, the current change represents a step forward in readability by reducing the amount of information displayed on the screen. - **Badges** Badges have been redesigned to provide a more consolidated design while ensuring comfortable readability. The color palette has been reviewed to strike a balance between aesthetics and readability, allowing the badge content to stand out while ensuring comfortable viewing. - **AppIcons, Pictograms and users' avatars** Deviate from the previous "fontAwesome design-line" and introduce a fresh design language that aligns with our branding strategy. All the assets now possess a unique and cohesive visual style, enhancing the overall user experience and strengthening our brand identity. ### SCSS: - **Separate "Bootstrap Review" for Frontend and Backend Bundles** Prior to this pull request, both the frontend and backend bundles were using the same `bootstrap_review.scss` file. However, as our backend design started to deviate from Bootstrap default, it became necessary to have a dedicated way to "review" Bootstrap styles specifically for the backend. This pull request introduces two new stylesheets: `bootstrap_review_frontend.scss` and `bootstrap_review_backend.scss`. The original `bootstrap_review.scss` file remains as a shared asset, containing customizations needed by all bundles. With this separation, we can now maintain distinct Bootstrap styles for the frontend and backend, enhancing clarity and flexibility of our codebase. - **[NEW] `bootstrap_review_backend.scss`** Reduce the need for cumbersome and unsightly overrides. By adopting a flexible and modular approach, we introduce a more consistent way of defining custom classes and custom legacy classes (e.g., `bg-black-50`). See `bootstrap_review_backend.scss`. - **[NEW] `utilities_custom_backend.scss`** Manage/limit/fine-tune the generation of Bootstrap utility classes for the backend. - **[NEW] `functions.scss`** Unlike `utils.scss`, this file is accessible at any stage of the compilation process. - **[NEW] `o_avatar` class** Uniform avatars designs defining a common class shared across different modules. - **[NEW] `o_tag` class** Define a common class for any type entry generated by the `TagsList` component (either badges or avatars) - **[IMP] overall spacing system** Solved a long-standing issue regarding spacing variables in Odoo (e.g., `$o-horizontal-padding`) and Bootstrap default spacing. By harmonizing these two systems, we now enable the seamless utilization of Bootstrap utility classes to manage webclient spacing. This enhancement ensures a consistent and uniform spacing experience throughout the application closes odoo/odoo#116641 Related: odoo/upgrade#4652 Related: odoo/enterprise#38775 Signed-off-by: Pierre Paridans (app) <app@odoo.com> Co-authored-by: Aaron Bohy <aab@odoo.com> Co-authored-by: Antoine (anso) <anso@odoo.com> Co-authored-by: Brieuc-brd <brd@odoo.com> Co-authored-by: Damien Bouvy <dbo@odoo.com> Co-authored-by: Dardenne Florent (dafl) <dafl@odoo.com> Co-authored-by: Elisabeth Dickinson <edi@odoo.com> Co-authored-by: Florian Charlier <flch@odoo.com> Co-authored-by: Julien Carion (juca) <juca@odoo.com> Co-authored-by: Mathieu (mano) <mano@odoo.com> Co-authored-by: Pierre Paridans <app@odoo.com> Co-authored-by: Romain Estievenart <res@odoo.com> Co-authored-by: Romeo Fragomeli <rfr@odoo.com> Co-authored-by: chrysanthe(chgo) <chgo@odoo.com> Co-authored-by: luvi <luvi@odoo.com> Co-authored-by: stefanorigano (SRI) <sri@odoo.com> Co-authored-by: xlu-odoo <xlu@odoo.com>
…
…
…
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials
Languages
Python
49.6%
JavaScript
47.8%
SCSS
2%
CSS
0.3%
HTML
0.2%