| Age | Commit message (Collapse) | Author |
|---|
|
Odoo used to declare two main colors: primary and optional (which are
purple and turquoise in enterprise). Those were respectively assigned
to the 'primary' bootstrap variable and the 'btn-primary' bootstrap
variable.
BS4, however, does not allow to have a different primary color for
buttons. Instead, the 'primary' color is used for all 'primary' related
components and utility classes, same as for all other colors. So, if we
want to keep our enterprise buttons green, our 'optional' colors had to
become our 'primary' color. The old odoo primary is then renamed to the
'odoo' color.
The palette of grays is now larger by default and is numbered from 100 to
900 alongside the $black and $white variables. The equivalence for older
variables and the way we used them is:
$gray-darker -> gray 900 (unused before)
$gray-dark -> gray 900
$gray -> gray 700
$gray-light -> gray 600
$gray-lighter-darker -> gray 400 (the old variable was created by us)
$gray-lighter-dark -> gray 300 (the old variable was created by us)
$gray-lighter -> gray 200
Fortunately, the 'lighter' variations we created fit well in the default
BS4 system ! Unfortunately, our $gray-lighter which carried the same
function as $gray-200 (see above) is very close to the new default
$gray-100 and quite distant from the new $gray-200. This will be handled
in the next commit.
|
|
BS4 do not provide vendor prefixes scss mixins anymore as it is meant
to be used with the 'autoprefixer' library. As we only support the last
version of every major browsers in Odoo, we took the decision to not
use the library as it was also complex to integrate in Odoo. We decided
to do the library's work by hand if it ever become necessary.
|
|
Unlike LESS, SCSS variables are not lazy loaded. Our system has thus
to be updated. This commit creates new templates which are t-called
in assets bundles (to replace the old less_helpers template):
- web._assets_utils: regroups the mixins and functions which *can*
(and so should) be available in every asset bundle
- web._assets_primary_variables: regroups the variables (or mixins
used as variables) which *can* (and so should) be available in
every asset bundle
- web._assets_secondary_variables: same as above but provides an
environnement where all the 'primary' ones are accessible. This is
for example useful to handle the community/enterprise split:
// Community primary variables
$o-pink-color: pink; // enterprise color
$o-brand-primary: blue;
// Enterprise primary variables
$o-brand-primary: $o-pink-color;
// Community secondary variables
$o-my-darker-primary: darken($o-brand-primary, 5%);
=> If there was only one variable template, enterprise edition would
have been able to define its primary color at the end but the
darker primary would not have been updated. Using the "!default"
system and putting enterprise definition above would not have
solved the problem as the $o-pink-color would not have been
accessible.
- web._assets_backend_helpers: regroups the variables, mixins and
functions which *can* (and so should) be available in the backend
asset bundle only. This is especially (only?) useful for bootstrap
variables overriddes.
- web._assets_frontend_helpers: regroups the variables, mixins and
functions which *can* (and so should) be available in the frontend
asset bundle only. This is especially (only?) useful for bootstrap
variables overriddes.
Note: bootstrap variables are not accessible in any of those anymore.
If you have variables that should depend on bootstrap, you have 3
solutions:
- Find another way: your variable is probably useless, use bootstrap
variables directly or create a variable that will influence the
value of bootstrap variables. E.g. instead of declaring:
`$myvar: $bootstrapvar * 3`
and using $myvar alone, declare:
`$myvar: 3` and use `$myvar * $bootstrapvar` where needed.
- Declare a copy of the bootstrap variable and use that one. In that
case, you should also force-set the real bootstrap one to be sure
they match (this should be done in appropriate templates mentioned
above). E.g.
```
$o-boostrapvar: 5;
...
$boostrapvar: $o-bootstrapvar;
```
- Set your variable to null and set it to your bootstrap expression
in the file you will need it (where bootstrap variables are accessible)
without forgetting to add the !default flag to allow overriddes.
```
$myvar: null;
...
$myvar: $bootstrapvar * 5 !default;
```
This commit also partly changes the variable names to follow the
convention:
$o-<app_id>-<name> where 'app_id' is the current's app name or a
meaningful unique identifier ("theme" for all themes for example, as
no multiple themes can be installed).
|
|
Convert content so that the assets compile on app installation. The
style is still broken after this as the variables/mixins/... are not
defined in the right order (as it did not matter in LESS but does in
SCSS).
This commit basically changes:
- Variables: @var_hello -> $var-hello
- Mixins: .mixin_world() {} -> @mixin mixin-world {}
- Classes used as mixin: .my_class() -> @extend .my_class
- Here there were no other solution than to convert the use of
a mixin call by the use of an extend as a first approximation
- LESS functions -> SCSS functions (e.g. fade -> rgba)
- Move first variable definition before the variable is used
- Still need to make sure last variable definition is at the
right place
|
|
This is a simple renaming without adaptation.
|
|
Resolve two "bugs" introduced with new design:
- Events kanban dropdown position
- Employees kanban tags position
|
|
|
|
- removed 'Edit' link on event vignette, as clicking on it redirect on the event
form view;
- fixed a glitch when hovering an event vignette
|
|
event:
- added tip
- default subscription/reminder/thanks templates for registrations are now using
the reply_to defined on the event
- fixed check of available seats: use seats_availability field, unlimited events
should never trigger the constraint
- added a sequence on scheduled emails on events
- config: wording improvements
- various improvements in event, registration, event_mail and event_report views
event_sale:
- removed override of seats_max: should not depend on available seats in
tickets. Indeed you may have less available places than the sum of seats for
each ticket type, for example if you have 0-10 VIP and 0-20 Standard tickets
for a 20-seats event.
- removed a duplicated view override
- added a seats_availability field on tickets, same meaning as on event.
- improved event form view: registration tab is now replaced by the tickets tab
when tickets are used
website_event:
- better management of sold-out event in the front-end, when doing registrations
website_event_sale:
- removed register link on the event kanban view. There is no need to to from
the back-end to the front-end from the kanban view. The published button on the
event form view already allows to go to the front-end view on the event
- better management of sold-out event in the front-end, when doing registrations
- fixed a template that was in customize and should not
website_event_track:
- wording improvements
- small improvements in the front-end of tracks
|
|
Added two features in kanban view
- having a data-routing attribute on the oe_kanban_global_click
container allow to have a custom routing instead of only
'form view' / 'edit view'. This is used for example to go to
the website view of events.
- allow type=url along with object, action, ... to have some specific
urls for links.
|
|
|
|
bzr revid: al@openerp.com-20130628100441-swpanf2jwcojygh4
|
|
bzr revid: vja@tinyerp.com-20121025090712-h3a7fls712w45fon
|
|
bzr revid: jra@tinyerp.com-20121015095749-yglvi7gur28q1vqu
|
|
bzr revid: fp@tinyerp.com-20121013104045-w552j40hzvqv9d89
|
|
bzr revid: apa@tinyerp.com-20121004123150-2hfqhhhhvzmm0rzg
|
|
bzr revid: rma@tinyerp.com-20121004104110-cy7koe2xiqt9xlde
|
|
getting the shadow effect.
bzr revid: psa@tinyerp.com-20121003131611-5i0fvvwjdm7hqety
|
|
bzr revid: al@openerp.com-20120525191127-v5o88etlbdq0jbzn
|
|
bzr revid: fp@tinyerp.com-20120525134306-3lz3127527hyly77
|
|
bzr revid: fp@tinyerp.com-20120525072829-34lyox1jl60ffye8
|
|
bzr revid: fp@tinyerp.com-20120525072114-x1ylvnbw2k3twbhy
|
|
bzr revid: atp@tinyerp.com-20120523134448-9vqtiufzjgmmaq0b
|
|
bzr revid: atp@tinyerp.com-20120523131956-ttslmltvzscz024o
|
|
specification.
bzr revid: atp@tinyerp.com-20120521132458-xozrh3vcz4wbo6t5
|
|
bzr revid: atp@tinyerp.com-20120517073046-i47jypr9p6ndckox
|
|
bzr revid: atp@tinyerp.com-20120511125434-pwz2hqbgxtmrurgy
|
|
bzr revid: atp@tinyerp.com-20120509173839-q3y5egsp8xliyfvi
|
|
bzr revid: atp@tinyerp.com-20120509121244-ougokpvpe9i5dxkx
|
|
bzr revid: atp@tinyerp.com-20120509114210-r3tp1nnn5rvoipqy
|
|
bzr revid: atp@tinyerp.com-20120505173340-1jmgy4clza1gy6sh
|
|
lp:~openerp-dev/openobject-addons/trunk-event_improvements-atp-event_page_with_google_map-nco
bzr revid: atp@tinyerp.com-20120504133632-qes40ecp3t17zcnv
|
|
bzr revid: nco@tinyerp.com-20120504114741-ik1ft1ln90188tpt
|
|
bzr revid: nco@tinyerp.com-20120504113136-ws9nxquin9sk95vu
|
|
bzr revid: vme@tinyerp.com-20120502071535-5h213fx2p5s0tlqi
|
|
bzr revid: atp@tinyerp.com-20120502070722-3twkfw14q89nznuo
|
|
lp:~openerp-dev/openobject-addons/trunk-event_improvements-atp-event_pageview-nco with some changes
bzr revid: atp@tinyerp.com-20120429180729-nscqe9nix9am0367
|
|
bzr revid: nco@tinyerp.com-20120427094634-foba34c88a4mn2ja
|
|
bzr revid: nco@tinyerp.com-20120427093242-o9srduq715lbqt8t
|
|
lp:~openerp-dev/openobject-addons/trunk-event_improvements-atp-improve-kanban-for-registration-bde
bzr revid: atp@tinyerp.com-20120420134326-i8m23eos2atpg4su
|
|
bzr revid: bde@tinyerp.com-20120418092637-uprsxgafbu1tl8vw
|
|
bzr revid: kbh@tinyerp.com-20120320103846-gt5dalg2tejw98lv
|
|
bzr revid: kbh@tinyerp.com-20120320102454-4q2hvlbg2rsouj1r
|
|
bzr revid: apa@tinyerp.com-20120320102217-80icy0kj5ronpfq4
|
|
bzr revid: dhr@tinyerp.com-20120307084418-uaemwhxf24f95fkw
|
|
bzr revid: dhr@tinyerp.com-20120307070004-wvmtqmqu8ybj0uz3
|
|
bzr revid: apa@tinyerp.com-20120306064902-rdx250ihctkpjph8
|
|
bzr revid: qdp-launchpad@openerp.com-20120229130041-anyfajbjvkjk7lbk
|
