* upgrade to bootstrap 3.3.6
* new Header, port website LESS
- Add the new header
- Modify sub-header in order to handle “back” button and version
switcher
- Port website’s Less:
* Use same variables’ names
* Review fonts and colours in order to fit the new style
* add new footer
* Review and optimise JS code in order properly handle the new header,
footer and card.top animations
* replace banner images
This is a big update of the posbox documentation in
addons/hw_proxy/doc. The main reason for this big change is v13 of the
posbox image which is vastly different from all the images that came
before it. On top of that, the documentation was also further updated to
look a bit better when rendered to HTML instead of PDF, which is what we
used before.
* by-application (odoo-wise) grouping
* use part of the accounting TOC defined on pad
* support for "internal" tocs & fixup front toc
* various changes and improvements to extensions
May be missing: inherited document banners?
dd.alternatives triggers "widget", each (dt, dd) is an alternative with
dt being the alternative (and radio button) label and dd being the
actual content to display on selection.
By default "iterating" a set will use a setseq which may still uniquify
information if it finds duplicates (but it may not as it's lazy &
al). #flatten conserves the seq type, so if there are two equal
operation items amongst all selected operations they may get
deduplicated, with the end result of operations disappearing in the
final formatted result.
In entries explanations and configuration, make it possible to "split"
the list in multiple sub-lists visually: a ``null`` item should just
create an empty space, not display a list item "dot"
Hiding of 0-values was only for accounts which hadn't been operated
on (for balance, or operations which had not happened for
debit/credit). Balanced account balances should not be hidden.
* interaction is terrible, select is ugly but radio buttons take way too
much vertical space, no matter whether they're on the left or the
right
* may be possible to unify operations lists between chart of accounts
and entries? Not currently selected set, just the list of possible ops
Only do so if the last user action was enabling said operation,
otherwise things get confusing.
=> keep a separate 'active' value which is unset when an operation is
disabled
* move chart of accounts higher in document
* rewrite text a bit
* split controls to left-hand column
* remove dependencies between operations
* highlight result of last-applied operation (not very good looking atm)
* convert listickles to React widget
* add interactive hooks to introduction/definition paragraphs
* add highlighting to various items based on (2)
todo: ragged bottom edge using a SVG border-image?
After discussion with fp this probably isn't the direction (ish), but
want to checkpoint this in order to work on other stuff earlier in the
document, but not commit a single gigantic blob of stuff.
