PyPI - odoo-addon-shopfloor-mobile - Versions diffs - 18.0.1.0.0.3__py3-none-any.whl → 18.0.1.0.1__py3-none-any.whl - Mend

odoo-addon-shopfloor-mobile 18.0.1.0.0.3py3-none-any.whl → 18.0.1.0.1py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (18) hide show

odoo/addons/shopfloor_mobile/README.rst CHANGED Viewed

@@ -11,7 +11,7 @@ Shopfloor mobile
    !! This file is generated by oca-gen-addon-readme !!
    !! changes will be overwritten.                   !!
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-   !! source digest: sha256:72c521eb98798688bdc15454ac31dcfc7a5d0ab70bff691f621d9b212c1ab6d1
+   !! source digest: sha256:5343b7be8eb4f58f7548ae53194c5554d3a7d9ac639fb64e27cae31cf8cd2766
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 .. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
@@ -34,35 +34,35 @@ Shopfloor mobile
 Frontend for Shopfloor app.
-The work is organized in scenario.
-A scenario represents a process in the warehouse (eg: receive, deliver).
-The app allows to start each process through the main menu.
-Each scenario is linked to a specific menu item which can be configured in the backend.
-Each scenario drives you through the work to do.
+The work is organized in scenario. A scenario represents a process in
+the warehouse (eg: receive, deliver). The app allows to start each
+process through the main menu.
+Each scenario is linked to a specific menu item which can be configured
+in the backend. Each scenario drives you through the work to do.
 Tech details
-~~~~~~~~~~~~
+------------
-* This frontend is built on top of `VueJS <vuejs.org>`_  and `VuetifyJS <vuetifyjs.com/>`_
-  and relies on `shopfloor` module that exposes REST API in Odoo
-  (based in turn on `base_rest <https://github.com/OCA/rest-framework/tree/13.0/base_rest>`_).
+- This frontend is built on top of `VueJS <vuejs.org>`__ and
+  `VuetifyJS <vuetifyjs.com/>`__ and relies on shopfloor module that
+  exposes REST API in Odoo (based in turn on
+  `base_rest <https://github.com/OCA/rest-framework/tree/13.0/base_rest>`__).
-* The whole business logic comes from `shopfloor` module,
-  this module takes care of providing a nice and reactive UI to work with.
+- The whole business logic comes from shopfloor module, this module
+  takes care of providing a nice and reactive UI to work with.
-* No Odoo JS is used, no assets machinery used.
+- No Odoo JS is used, no assets machinery used.
   Static assets are loaded straight, served by a specific controller.
   This app is a Single Page App, hence resources are loaded only once.
-  The version of the module appended to the URL of each resources
-  makes sure it's not cached when the version changes.
+  The version of the module appended to the URL of each resources makes
+  sure it's not cached when the version changes.
-* When developing you can use a demo mode which allows to define interactive scenario
-  with pure JS demo data, without interacting with Odoo.
-  Nothing to deal with Odoo demo data.
+- When developing you can use a demo mode which allows to define
+  interactive scenario with pure JS demo data, without interacting with
+  Odoo. Nothing to deal with Odoo demo data.
 **Table of contents**
@@ -73,78 +73,92 @@ Usage
 =====
 Pre-requisites
-~~~~~~~~~~~~~~
+--------------
-* Your Odoo instance is accessible via mobile device
-* You have an API Key configured
+- Your Odoo instance is accessible via mobile device
+- You have an API Key configured
 Start the app
-~~~~~~~~~~~~~
+-------------
-* Go to "Inventory -> Configuration -> Shopfloor -> Shopfloor App"
-* In the login screen fill in your API key
-* Hit "Login"
+- Go to "Inventory -> Configuration -> Shopfloor -> Shopfloor App"
+- In the login screen fill in your API key
+- Hit "Login"
 Select a profile
-~~~~~~~~~~~~~~~~
+----------------
-Several profiles can be configured in the backend,
-you must choose one before starting.
+Several profiles can be configured in the backend, you must choose one
+before starting.
-* Tap on "Configure profile"
-* Select a profile
+- Tap on "Configure profile"
+- Select a profile
 This will load all available menu items for the selected profile.
 Change language
-~~~~~~~~~~~~~~~
+---------------
-* Go to "Settings -> Language"
-* Select a language
+- Go to "Settings -> Language"
+- Select a language
 Customization
-~~~~~~~~~~~~~
+-------------
-Please refer to `shopfloor_mobile_custom_example`.
+Please refer to shopfloor_mobile_custom_example.
 Known issues / Roadmap
 ======================
-* Split module by scenario
-* Improve documentation and demo data
-* Document each component
-* Document demo mode
-* Find / create a nice icon
-* Finish base translations (move all UI strings to translatable terms)
-* Use SCSS
-* Refactor states definition
-  States are now part of the scenario data. They should be specific objects with their own class.
-  They should also provide all the actions that should be displayed w/ their handlers when needed.
-  Actions can be popup actions or buttons at the bottom of the screen.
-  The tricky part here could be how to register this states for the given component.
-  Today states have access to the full object of the scenario component as they are part of it.
-  `_get_state_spec` could probably lookup for registered states
-  (eg: when you register a component in the registry you should provide states as well).
-  When we'll have states in this fashion we should also consider if they should provide their own template.
-  This way the component template will hold only the generic bits of the scenario.
-* Back buttons should be smarter
-  In some cases getting back using history is fine but very often this could lead to outdated data display.
-  To mitigate this in particular scenario's steps, custom handlers for the back action have been implemented.
-  For instance, in cluster_picking when you hit back on manual selection it forces the state to go to start and reload.
-  For starting we should provide `on_back` property to all states where we want to display it
-  (no more specific check on the state to display this button).
-  This part is also related to "Refactor states definition".
-* Go through `_.forEach` and similar calls to replace them w/ vanilla JS (eg: `.map()`)
+- Split module by scenario
+- Improve documentation and demo data
+- Document each component
+- Document demo mode
+- Find / create a nice icon
+- Finish base translations (move all UI strings to translatable terms)
+- Use SCSS
+- Refactor states definition
+  States are now part of the scenario data. They should be specific
+  objects with their own class. They should also provide all the actions
+  that should be displayed w/ their handlers when needed. Actions can be
+  popup actions or buttons at the bottom of the screen. The tricky part
+  here could be how to register this states for the given component.
+  Today states have access to the full object of the scenario component
+  as they are part of it. \_get_state_spec could probably lookup for
+  registered states (eg: when you register a component in the registry
+  you should provide states as well). When we'll have states in this
+  fashion we should also consider if they should provide their own
+  template. This way the component template will hold only the generic
+  bits of the scenario.
+- Back buttons should be smarter
+  In some cases getting back using history is fine but very often this
+  could lead to outdated data display. To mitigate this in particular
+  scenario's steps, custom handlers for the back action have been
+  implemented. For instance, in cluster_picking when you hit back on
+  manual selection it forces the state to go to start and reload. For
+  starting we should provide on_back property to all states where we
+  want to display it (no more specific check on the state to display
+  this button). This part is also related to "Refactor states
+  definition".
+- Go through \_.forEach and similar calls to replace them w/ vanilla JS
+  (eg: .map())
 Changelog
 =========
 13.0.1.0.0
-~~~~~~~~~~
+----------
 First official version.
@@ -162,39 +176,38 @@ Credits
 =======
 Authors
-~~~~~~~
+-------
 * Camptocamp
 * BCIM
 * Akretion
 Contributors
-~~~~~~~~~~~~
+------------
-* Simone Orsi <simahawk@gmail.com>
-* Thierry Ducrest <thierry.ducrest@camptocamp.com>
-* Guewen Baconnier <guewen.baconnier@camptocamp.com>
-* Raphaël Reverdy <raphael.reverdy@akretion.com>
-* Sébastien Beau <sebastien.beau@akretion.com>
-* Jacques-Etienne Baudoux <je@bcim.be>
+- Simone Orsi <simahawk@gmail.com>
+- Thierry Ducrest <thierry.ducrest@camptocamp.com>
+- Guewen Baconnier <guewen.baconnier@camptocamp.com>
+- Raphaël Reverdy <raphael.reverdy@akretion.com>
+- Sébastien Beau <sebastien.beau@akretion.com>
+- Jacques-Etienne Baudoux <je@bcim.be>
-Design
-~~~~~~
+**Design**
-* Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
-* Jacques-Etienne Baudoux <je@bcim.be>
+- Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
+- Jacques-Etienne Baudoux <je@bcim.be>
 Other credits
-~~~~~~~~~~~~~
+-------------
 **Financial support**
-* Cosanum
-* Camptocamp R&D
-* Akretion R&D
+- Cosanum
+- Camptocamp R&D
+- Akretion R&D
 Maintainers
-~~~~~~~~~~~
+-----------
 This module is maintained by the OCA.

odoo/addons/shopfloor_mobile/__manifest__.py CHANGED Viewed

@@ -5,7 +5,7 @@
 {
     "name": "Shopfloor mobile",
     "summary": "Mobile frontend for WMS Shopfloor app",
-    "version": "18.0.1.0.0",
+    "version": "18.0.1.0.1",
     "depends": ["shopfloor", "shopfloor_mobile_base"],
     "author": "Camptocamp, BCIM, Akretion, Odoo Community Association (OCA)",
     "maintainers": ["simahawk"],

odoo/addons/shopfloor_mobile/readme/CONTRIBUTORS.md ADDED Viewed

@@ -0,0 +1,11 @@
+- Simone Orsi \<<simahawk@gmail.com>\>
+- Thierry Ducrest \<<thierry.ducrest@camptocamp.com>\>
+- Guewen Baconnier \<<guewen.baconnier@camptocamp.com>\>
+- Raphaël Reverdy \<<raphael.reverdy@akretion.com>\>
+- Sébastien Beau \<<sebastien.beau@akretion.com>\>
+- Jacques-Etienne Baudoux \<<je@bcim.be>\>
+**Design**
+- Joël Grand-Guillaume \<<joel.grandguillaume@camptocamp.com>\>
+- Jacques-Etienne Baudoux \<<je@bcim.be>\>

odoo/addons/shopfloor_mobile/readme/CREDITS.md ADDED Viewed

@@ -0,0 +1,5 @@
+**Financial support**
+- Cosanum
+- Camptocamp R&D
+- Akretion R&D

odoo/addons/shopfloor_mobile/readme/DESCRIPTION.md ADDED Viewed

@@ -0,0 +1,30 @@
+Frontend for Shopfloor app.
+The work is organized in scenario. A scenario represents a process in
+the warehouse (eg: receive, deliver). The app allows to start each
+process through the main menu.
+Each scenario is linked to a specific menu item which can be configured
+in the backend. Each scenario drives you through the work to do.
+## Tech details
+- This frontend is built on top of [VueJS](vuejs.org) and
+  [VuetifyJS](vuetifyjs.com/) and relies on shopfloor module that
+  exposes REST API in Odoo (based in turn on
+  [base_rest](https://github.com/OCA/rest-framework/tree/13.0/base_rest)).
+- The whole business logic comes from shopfloor module, this module
+  takes care of providing a nice and reactive UI to work with.
+- No Odoo JS is used, no assets machinery used.
+  Static assets are loaded straight, served by a specific controller.
+  This app is a Single Page App, hence resources are loaded only once.
+  The version of the module appended to the URL of each resources makes
+  sure it's not cached when the version changes.
+- When developing you can use a demo mode which allows to define
+  interactive scenario with pure JS demo data, without interacting with
+  Odoo. Nothing to deal with Odoo demo data.

odoo/addons/shopfloor_mobile/readme/{HISTORY.rst → HISTORY.md} RENAMED Viewed

@@ -1,4 +1,3 @@
-13.0.1.0.0
-~~~~~~~~~~
+## 13.0.1.0.0
 First official version.

odoo/addons/shopfloor_mobile/readme/ROADMAP.md ADDED Viewed

@@ -0,0 +1,43 @@
+- Split module by scenario
+- Improve documentation and demo data
+- Document each component
+- Document demo mode
+- Find / create a nice icon
+- Finish base translations (move all UI strings to translatable terms)
+- Use SCSS
+- Refactor states definition
+  States are now part of the scenario data. They should be specific
+  objects with their own class. They should also provide all the actions
+  that should be displayed w/ their handlers when needed. Actions can be
+  popup actions or buttons at the bottom of the screen. The tricky part
+  here could be how to register this states for the given component.
+  Today states have access to the full object of the scenario component
+  as they are part of it. \_get_state_spec could probably lookup for
+  registered states (eg: when you register a component in the registry
+  you should provide states as well). When we'll have states in this
+  fashion we should also consider if they should provide their own
+  template. This way the component template will hold only the generic
+  bits of the scenario.
+- Back buttons should be smarter
+  In some cases getting back using history is fine but very often this
+  could lead to outdated data display. To mitigate this in particular
+  scenario's steps, custom handlers for the back action have been
+  implemented. For instance, in cluster_picking when you hit back on
+  manual selection it forces the state to go to start and reload. For
+  starting we should provide on_back property to all states where we
+  want to display it (no more specific check on the state to display
+  this button). This part is also related to "Refactor states
+  definition".
+- Go through \_.forEach and similar calls to replace them w/ vanilla JS
+  (eg: .map())

odoo/addons/shopfloor_mobile/readme/USAGE.md ADDED Viewed

@@ -0,0 +1,29 @@
+## Pre-requisites
+- Your Odoo instance is accessible via mobile device
+- You have an API Key configured
+## Start the app
+- Go to "Inventory -\> Configuration -\> Shopfloor -\> Shopfloor App"
+- In the login screen fill in your API key
+- Hit "Login"
+## Select a profile
+Several profiles can be configured in the backend, you must choose one
+before starting.
+- Tap on "Configure profile"
+- Select a profile
+This will load all available menu items for the selected profile.
+## Change language
+- Go to "Settings -\> Language"
+- Select a language
+## Customization
+Please refer to shopfloor_mobile_custom_example.

odoo/addons/shopfloor_mobile/static/description/index.html CHANGED Viewed

@@ -372,34 +372,35 @@ ul.auto-toc {
 !! This file is generated by oca-gen-addon-readme !!
 !! changes will be overwritten.                   !!
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-!! source digest: sha256:72c521eb98798688bdc15454ac31dcfc7a5d0ab70bff691f621d9b212c1ab6d1
+!! source digest: sha256:5343b7be8eb4f58f7548ae53194c5554d3a7d9ac639fb64e27cae31cf8cd2766
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
 <p><a class="reference external image-reference" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/license-AGPL--3-blue.png" /></a> <a class="reference external image-reference" href="https://github.com/OCA/stock-logistics-shopfloor/tree/18.0/shopfloor_mobile"><img alt="OCA/stock-logistics-shopfloor" src="https://img.shields.io/badge/github-OCA%2Fstock--logistics--shopfloor-lightgray.png?logo=github" /></a> <a class="reference external image-reference" href="https://translation.odoo-community.org/projects/stock-logistics-shopfloor-18-0/stock-logistics-shopfloor-18-0-shopfloor_mobile"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external image-reference" href="https://runboat.odoo-community.org/builds?repo=OCA/stock-logistics-shopfloor&amp;target_branch=18.0"><img alt="Try me on Runboat" src="https://img.shields.io/badge/runboat-Try%20me-875A7B.png" /></a></p>
 <p>Frontend for Shopfloor app.</p>
-<p>The work is organized in scenario.
-A scenario represents a process in the warehouse (eg: receive, deliver).
-The app allows to start each process through the main menu.</p>
-<p>Each scenario is linked to a specific menu item which can be configured in the backend.
-Each scenario drives you through the work to do.</p>
+<p>The work is organized in scenario. A scenario represents a process in
+the warehouse (eg: receive, deliver). The app allows to start each
+process through the main menu.</p>
+<p>Each scenario is linked to a specific menu item which can be configured
+in the backend. Each scenario drives you through the work to do.</p>
 <div class="section" id="tech-details">
 <h2>Tech details</h2>
 <ul>
-<li><p class="first">This frontend is built on top of <a class="reference external" href="vuejs.org">VueJS</a>  and <a class="reference external" href="vuetifyjs.com/">VuetifyJS</a>
-and relies on <cite>shopfloor</cite> module that exposes REST API in Odoo
-(based in turn on <a class="reference external" href="https://github.com/OCA/rest-framework/tree/13.0/base_rest">base_rest</a>).</p>
+<li><p class="first">This frontend is built on top of <a class="reference external" href="vuejs.org">VueJS</a> and
+<a class="reference external" href="vuetifyjs.com/">VuetifyJS</a> and relies on shopfloor module that
+exposes REST API in Odoo (based in turn on
+<a class="reference external" href="https://github.com/OCA/rest-framework/tree/13.0/base_rest">base_rest</a>).</p>
 </li>
-<li><p class="first">The whole business logic comes from <cite>shopfloor</cite> module,
-this module takes care of providing a nice and reactive UI to work with.</p>
+<li><p class="first">The whole business logic comes from shopfloor module, this module
+takes care of providing a nice and reactive UI to work with.</p>
 </li>
 <li><p class="first">No Odoo JS is used, no assets machinery used.</p>
 <p>Static assets are loaded straight, served by a specific controller.
 This app is a Single Page App, hence resources are loaded only once.</p>
-<p>The version of the module appended to the URL of each resources
-makes sure it’s not cached when the version changes.</p>
+<p>The version of the module appended to the URL of each resources makes
+sure it’s not cached when the version changes.</p>
 </li>
-<li><p class="first">When developing you can use a demo mode which allows to define interactive scenario
-with pure JS demo data, without interacting with Odoo.
-Nothing to deal with Odoo demo data.</p>
+<li><p class="first">When developing you can use a demo mode which allows to define
+interactive scenario with pure JS demo data, without interacting with
+Odoo. Nothing to deal with Odoo demo data.</p>
 </li>
 </ul>
 <p><strong>Table of contents</strong></p>
@@ -429,8 +430,8 @@ Nothing to deal with Odoo demo data.</p>
 </div>
 <div class="section" id="select-a-profile">
 <h2>Select a profile</h2>
-<p>Several profiles can be configured in the backend,
-you must choose one before starting.</p>
+<p>Several profiles can be configured in the backend, you must choose one
+before starting.</p>
 <ul class="simple">
 <li>Tap on “Configure profile”</li>
 <li>Select a profile</li>
@@ -446,7 +447,7 @@ you must choose one before starting.</p>
 </div>
 <div class="section" id="customization">
 <h2>Customization</h2>
-<p>Please refer to <cite>shopfloor_mobile_custom_example</cite>.</p>
+<p>Please refer to shopfloor_mobile_custom_example.</p>
 <div class="section" id="known-issues-roadmap">
 <h3>Known issues / Roadmap</h3>
 <ul>
@@ -465,25 +466,32 @@ you must choose one before starting.</p>
 <li><p class="first">Use SCSS</p>
 </li>
 <li><p class="first">Refactor states definition</p>
-<p>States are now part of the scenario data. They should be specific objects with their own class.
-They should also provide all the actions that should be displayed w/ their handlers when needed.
-Actions can be popup actions or buttons at the bottom of the screen.
-The tricky part here could be how to register this states for the given component.
-Today states have access to the full object of the scenario component as they are part of it.
-<cite>_get_state_spec</cite> could probably lookup for registered states
-(eg: when you register a component in the registry you should provide states as well).
-When we’ll have states in this fashion we should also consider if they should provide their own template.
-This way the component template will hold only the generic bits of the scenario.</p>
+<p>States are now part of the scenario data. They should be specific
+objects with their own class. They should also provide all the actions
+that should be displayed w/ their handlers when needed. Actions can be
+popup actions or buttons at the bottom of the screen. The tricky part
+here could be how to register this states for the given component.
+Today states have access to the full object of the scenario component
+as they are part of it. _get_state_spec could probably lookup for
+registered states (eg: when you register a component in the registry
+you should provide states as well). When we’ll have states in this
+fashion we should also consider if they should provide their own
+template. This way the component template will hold only the generic
+bits of the scenario.</p>
 </li>
 <li><p class="first">Back buttons should be smarter</p>
-<p>In some cases getting back using history is fine but very often this could lead to outdated data display.
-To mitigate this in particular scenario’s steps, custom handlers for the back action have been implemented.
-For instance, in cluster_picking when you hit back on manual selection it forces the state to go to start and reload.
-For starting we should provide <cite>on_back</cite> property to all states where we want to display it
-(no more specific check on the state to display this button).
-This part is also related to “Refactor states definition”.</p>
+<p>In some cases getting back using history is fine but very often this
+could lead to outdated data display. To mitigate this in particular
+scenario’s steps, custom handlers for the back action have been
+implemented. For instance, in cluster_picking when you hit back on
+manual selection it forces the state to go to start and reload. For
+starting we should provide on_back property to all states where we
+want to display it (no more specific check on the state to display
+this button). This part is also related to “Refactor states
+definition”.</p>
 </li>
-<li><p class="first">Go through <cite>_.forEach</cite> and similar calls to replace them w/ vanilla JS (eg: <cite>.map()</cite>)</p>
+<li><p class="first">Go through _.forEach and similar calls to replace them w/ vanilla JS
+(eg: .map())</p>
 </li>
 </ul>
 </div>
@@ -524,9 +532,7 @@ If you spotted it first, help us to smash it by providing a detailed and welcome
 <li>Sébastien Beau &lt;<a class="reference external" href="mailto:sebastien.beau&#64;akretion.com">sebastien.beau&#64;akretion.com</a>&gt;</li>
 <li>Jacques-Etienne Baudoux &lt;<a class="reference external" href="mailto:je&#64;bcim.be">je&#64;bcim.be</a>&gt;</li>
 </ul>
-</div>
-<div class="section" id="design">
-<h2>Design</h2>
+<p><strong>Design</strong></p>
 <ul class="simple">
 <li>Joël Grand-Guillaume &lt;<a class="reference external" href="mailto:joel.grandguillaume&#64;camptocamp.com">joel.grandguillaume&#64;camptocamp.com</a>&gt;</li>
 <li>Jacques-Etienne Baudoux &lt;<a class="reference external" href="mailto:je&#64;bcim.be">je&#64;bcim.be</a>&gt;</li>

{odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info → odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info}/METADATA RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: odoo-addon-shopfloor_mobile
-Version: 18.0.1.0.0.3
+Version: 18.0.1.0.1
 Requires-Python: >=3.10
 Requires-Dist: odoo-addon-shopfloor==18.0.*
 Requires-Dist: odoo-addon-shopfloor_mobile_base==18.0.*
@@ -29,7 +29,7 @@ Shopfloor mobile
    !! This file is generated by oca-gen-addon-readme !!
    !! changes will be overwritten.                   !!
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-   !! source digest: sha256:72c521eb98798688bdc15454ac31dcfc7a5d0ab70bff691f621d9b212c1ab6d1
+   !! source digest: sha256:5343b7be8eb4f58f7548ae53194c5554d3a7d9ac639fb64e27cae31cf8cd2766
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 .. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
@@ -52,35 +52,35 @@ Shopfloor mobile
 Frontend for Shopfloor app.
-The work is organized in scenario.
-A scenario represents a process in the warehouse (eg: receive, deliver).
-The app allows to start each process through the main menu.
-Each scenario is linked to a specific menu item which can be configured in the backend.
-Each scenario drives you through the work to do.
+The work is organized in scenario. A scenario represents a process in
+the warehouse (eg: receive, deliver). The app allows to start each
+process through the main menu.
+Each scenario is linked to a specific menu item which can be configured
+in the backend. Each scenario drives you through the work to do.
 Tech details
-~~~~~~~~~~~~
+------------
-* This frontend is built on top of `VueJS <vuejs.org>`_  and `VuetifyJS <vuetifyjs.com/>`_
-  and relies on `shopfloor` module that exposes REST API in Odoo
-  (based in turn on `base_rest <https://github.com/OCA/rest-framework/tree/13.0/base_rest>`_).
+- This frontend is built on top of `VueJS <vuejs.org>`__ and
+  `VuetifyJS <vuetifyjs.com/>`__ and relies on shopfloor module that
+  exposes REST API in Odoo (based in turn on
+  `base_rest <https://github.com/OCA/rest-framework/tree/13.0/base_rest>`__).
-* The whole business logic comes from `shopfloor` module,
-  this module takes care of providing a nice and reactive UI to work with.
+- The whole business logic comes from shopfloor module, this module
+  takes care of providing a nice and reactive UI to work with.
-* No Odoo JS is used, no assets machinery used.
+- No Odoo JS is used, no assets machinery used.
   Static assets are loaded straight, served by a specific controller.
   This app is a Single Page App, hence resources are loaded only once.
-  The version of the module appended to the URL of each resources
-  makes sure it's not cached when the version changes.
+  The version of the module appended to the URL of each resources makes
+  sure it's not cached when the version changes.
-* When developing you can use a demo mode which allows to define interactive scenario
-  with pure JS demo data, without interacting with Odoo.
-  Nothing to deal with Odoo demo data.
+- When developing you can use a demo mode which allows to define
+  interactive scenario with pure JS demo data, without interacting with
+  Odoo. Nothing to deal with Odoo demo data.
 **Table of contents**
@@ -91,78 +91,92 @@ Usage
 =====
 Pre-requisites
-~~~~~~~~~~~~~~
+--------------
-* Your Odoo instance is accessible via mobile device
-* You have an API Key configured
+- Your Odoo instance is accessible via mobile device
+- You have an API Key configured
 Start the app
-~~~~~~~~~~~~~
+-------------
-* Go to "Inventory -> Configuration -> Shopfloor -> Shopfloor App"
-* In the login screen fill in your API key
-* Hit "Login"
+- Go to "Inventory -> Configuration -> Shopfloor -> Shopfloor App"
+- In the login screen fill in your API key
+- Hit "Login"
 Select a profile
-~~~~~~~~~~~~~~~~
+----------------
-Several profiles can be configured in the backend,
-you must choose one before starting.
+Several profiles can be configured in the backend, you must choose one
+before starting.
-* Tap on "Configure profile"
-* Select a profile
+- Tap on "Configure profile"
+- Select a profile
 This will load all available menu items for the selected profile.
 Change language
-~~~~~~~~~~~~~~~
+---------------
-* Go to "Settings -> Language"
-* Select a language
+- Go to "Settings -> Language"
+- Select a language
 Customization
-~~~~~~~~~~~~~
+-------------
-Please refer to `shopfloor_mobile_custom_example`.
+Please refer to shopfloor_mobile_custom_example.
 Known issues / Roadmap
 ======================
-* Split module by scenario
-* Improve documentation and demo data
-* Document each component
-* Document demo mode
-* Find / create a nice icon
-* Finish base translations (move all UI strings to translatable terms)
-* Use SCSS
-* Refactor states definition
-  States are now part of the scenario data. They should be specific objects with their own class.
-  They should also provide all the actions that should be displayed w/ their handlers when needed.
-  Actions can be popup actions or buttons at the bottom of the screen.
-  The tricky part here could be how to register this states for the given component.
-  Today states have access to the full object of the scenario component as they are part of it.
-  `_get_state_spec` could probably lookup for registered states
-  (eg: when you register a component in the registry you should provide states as well).
-  When we'll have states in this fashion we should also consider if they should provide their own template.
-  This way the component template will hold only the generic bits of the scenario.
-* Back buttons should be smarter
-  In some cases getting back using history is fine but very often this could lead to outdated data display.
-  To mitigate this in particular scenario's steps, custom handlers for the back action have been implemented.
-  For instance, in cluster_picking when you hit back on manual selection it forces the state to go to start and reload.
-  For starting we should provide `on_back` property to all states where we want to display it
-  (no more specific check on the state to display this button).
-  This part is also related to "Refactor states definition".
-* Go through `_.forEach` and similar calls to replace them w/ vanilla JS (eg: `.map()`)
+- Split module by scenario
+- Improve documentation and demo data
+- Document each component
+- Document demo mode
+- Find / create a nice icon
+- Finish base translations (move all UI strings to translatable terms)
+- Use SCSS
+- Refactor states definition
+  States are now part of the scenario data. They should be specific
+  objects with their own class. They should also provide all the actions
+  that should be displayed w/ their handlers when needed. Actions can be
+  popup actions or buttons at the bottom of the screen. The tricky part
+  here could be how to register this states for the given component.
+  Today states have access to the full object of the scenario component
+  as they are part of it. \_get_state_spec could probably lookup for
+  registered states (eg: when you register a component in the registry
+  you should provide states as well). When we'll have states in this
+  fashion we should also consider if they should provide their own
+  template. This way the component template will hold only the generic
+  bits of the scenario.
+- Back buttons should be smarter
+  In some cases getting back using history is fine but very often this
+  could lead to outdated data display. To mitigate this in particular
+  scenario's steps, custom handlers for the back action have been
+  implemented. For instance, in cluster_picking when you hit back on
+  manual selection it forces the state to go to start and reload. For
+  starting we should provide on_back property to all states where we
+  want to display it (no more specific check on the state to display
+  this button). This part is also related to "Refactor states
+  definition".
+- Go through \_.forEach and similar calls to replace them w/ vanilla JS
+  (eg: .map())
 Changelog
 =========
 13.0.1.0.0
-~~~~~~~~~~
+----------
 First official version.
@@ -180,39 +194,38 @@ Credits
 =======
 Authors
-~~~~~~~
+-------
 * Camptocamp
 * BCIM
 * Akretion
 Contributors
-~~~~~~~~~~~~
+------------
-* Simone Orsi <simahawk@gmail.com>
-* Thierry Ducrest <thierry.ducrest@camptocamp.com>
-* Guewen Baconnier <guewen.baconnier@camptocamp.com>
-* Raphaël Reverdy <raphael.reverdy@akretion.com>
-* Sébastien Beau <sebastien.beau@akretion.com>
-* Jacques-Etienne Baudoux <je@bcim.be>
+- Simone Orsi <simahawk@gmail.com>
+- Thierry Ducrest <thierry.ducrest@camptocamp.com>
+- Guewen Baconnier <guewen.baconnier@camptocamp.com>
+- Raphaël Reverdy <raphael.reverdy@akretion.com>
+- Sébastien Beau <sebastien.beau@akretion.com>
+- Jacques-Etienne Baudoux <je@bcim.be>
-Design
-~~~~~~
+**Design**
-* Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
-* Jacques-Etienne Baudoux <je@bcim.be>
+- Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
+- Jacques-Etienne Baudoux <je@bcim.be>
 Other credits
-~~~~~~~~~~~~~
+-------------
 **Financial support**
-* Cosanum
-* Camptocamp R&D
-* Akretion R&D
+- Cosanum
+- Camptocamp R&D
+- Akretion R&D
 Maintainers
-~~~~~~~~~~~
+-----------
 This module is maintained by the OCA.

{odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info → odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info}/RECORD RENAMED Viewed

@@ -1,19 +1,19 @@
-odoo/addons/shopfloor_mobile/README.rst,sha256=UbMcxyA0oVWCcIbuMD1pGSx2AgjwZS9Eg8ffe_3kJVo,7535
+odoo/addons/shopfloor_mobile/README.rst,sha256=UmHT0U7vbLx-7twlKbc9yBMFyr-9zuYWAS6fFKVJT7I,7544
 odoo/addons/shopfloor_mobile/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-odoo/addons/shopfloor_mobile/__manifest__.py,sha256=69ve-61qicPHLsCtqdzWYi2z4RlAt_gHy9MU-d5MIpc,705
+odoo/addons/shopfloor_mobile/__manifest__.py,sha256=5NRg1zBM05mcz3MRQ_S0fPLfz5gJbJAbGTAPcXceQVA,705
 odoo/addons/shopfloor_mobile/i18n/de.po,sha256=6eRN27NdcMT5a9_rC7t-L1IyssIf4d0sV8XcBlxYETU,411
 odoo/addons/shopfloor_mobile/i18n/es_AR.po,sha256=8mGWCcMew3na_BE6yzC9aGqTSHNwLq_fu1r-JnZnYGE,1149
 odoo/addons/shopfloor_mobile/i18n/it.po,sha256=Fuhk7nf_wDaq10_RJlCCe4xE6u8qKIml2r_4nUJ1O1w,412
 odoo/addons/shopfloor_mobile/i18n/pt_BR.po,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 odoo/addons/shopfloor_mobile/i18n/shopfloor_mobile.pot,sha256=2nkV-O77dcHWhLBfGldb2hwKdpsp_Iq_PU5QMeyP-mo,341
-odoo/addons/shopfloor_mobile/readme/CONTRIBUTORS.rst,sha256=AEECRuaiP1U4xBwIQOYsHFr-Tgx2-LqBQPmFejH6OIs,392
-odoo/addons/shopfloor_mobile/readme/CREDITS.rst,sha256=gvM_pe6NW3J9LsH6xxFxvRsY1AY8T8fVLeRzce2RKhY,65
-odoo/addons/shopfloor_mobile/readme/DESCRIPTION.rst,sha256=uA0FkgekxpCEfqLjiUlpPWbe-8QKOiVDB6QvoyJ7bJg,1245
-odoo/addons/shopfloor_mobile/readme/HISTORY.rst,sha256=Ibf54quZVYNg74R-oWzny0XeMee1wp8T4Og1gaGo3OQ,47
-odoo/addons/shopfloor_mobile/readme/ROADMAP.rst,sha256=Nm8uyGJvPQWMQtYwwxt8P4WBuLLpUZjZ_p8eqTrFRbM,1726
-odoo/addons/shopfloor_mobile/readme/USAGE.rst,sha256=5NNHChxhLwFVo4m6XhCaSlagf_bpNaZgsF8oSGSQ2WY,677
+odoo/addons/shopfloor_mobile/readme/CONTRIBUTORS.md,sha256=9fV8XRI7FHlu1rZooxvlWcoD188t7zC5Frd8eUHz3tk,421
+odoo/addons/shopfloor_mobile/readme/CREDITS.md,sha256=mijiEMeb8qlUh8sbIa_3gn03LhbjHBFrlNCF_9CZELM,65
+odoo/addons/shopfloor_mobile/readme/DESCRIPTION.md,sha256=tsBMHhIrbnsPP5KBIRgtnmjxPvdHhVbCmjglGgU6tOA,1225
+odoo/addons/shopfloor_mobile/readme/HISTORY.md,sha256=uDTaJkR5ECI5b0x32Vuj4ONzBVvfsfMjPm20jISB5Ps,39
+odoo/addons/shopfloor_mobile/readme/ROADMAP.md,sha256=GMldnYqUvyrfgwUbIjZ_68wJtHmOyE1Tb_vQZtAplOo,1741
+odoo/addons/shopfloor_mobile/readme/USAGE.md,sha256=0rRYeb0UEsTSg2EiEB0WHlOGdEMX8sCJT5blDcF0fFU,618
 odoo/addons/shopfloor_mobile/static/description/icon.png,sha256=6xBPJauaFOF0KDHfHgQopSc28kKvxMaeoQFQWZtfZDo,9455
-odoo/addons/shopfloor_mobile/static/description/index.html,sha256=6oBWayb187QODeaw1KlSFkg9OeG8WrDXcCNA-fO59NU,18469
+odoo/addons/shopfloor_mobile/static/description/index.html,sha256=zSP52hzehSed3XuUyyweJqU57UnnQwYSXuqPXGGoZ54,18351
 odoo/addons/shopfloor_mobile/static/wms/.gitignore,sha256=rQCFL3FQm3Lll35BRUETzj1HYlakdld--GvTGLPeHpE,214
 odoo/addons/shopfloor_mobile/static/wms/src/screen.esm.js,sha256=77TQgYSfpnErCuhV9FjQujMFlrKU7EZ6OdeTJnZutV8,1461
 odoo/addons/shopfloor_mobile/static/wms/src/wms_utils.esm.js,sha256=89d19IbDlfFavsgsinKfEtyaSTbRZduITxwxAHnnLbE,12178
@@ -53,7 +53,7 @@ odoo/addons/shopfloor_mobile/static/wms/src/scenario/location_content_transfer.e
 odoo/addons/shopfloor_mobile/static/wms/src/scenario/single_pack_transfer.esm.js,sha256=ipc8fKBtv4_KRZBEBV5pmmefjtHnSOarx5KUnfyjNoE,6114
 odoo/addons/shopfloor_mobile/static/wms/src/scenario/zone_picking.esm.js,sha256=mNcE39AtO9vPfjSrNybjV9hiNoSErMyJ0ev1PgOOxd0,44849
 odoo/addons/shopfloor_mobile/templates/assets.xml,sha256=K9Tu1nUq_t8WquSEV4GHigPd5QuYY-2rqbt4V9sWkxs,7993
-odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info/METADATA,sha256=yDGuulMEomM9O7NwoEhl7EY6f3_TP2mhUGQ2WgYs1x0,8223
-odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info/WHEEL,sha256=ZhOvUsYhy81Dx67gN3TV0RchQWBIIzutDZaJODDg2Vo,81
-odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info/top_level.txt,sha256=QE6RBQ0QX5f4eFuUcGgU5Kbq1A_qJcDs-e_vpr6pmfU,4
-odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info/RECORD,,
+odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info/METADATA,sha256=hcd_wcQGd53whR2AclzUUOdX__BMFxXqCA9yVKaok9k,8230
+odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info/WHEEL,sha256=ZhOvUsYhy81Dx67gN3TV0RchQWBIIzutDZaJODDg2Vo,81
+odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info/top_level.txt,sha256=QE6RBQ0QX5f4eFuUcGgU5Kbq1A_qJcDs-e_vpr6pmfU,4
+odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info/RECORD,,

odoo/addons/shopfloor_mobile/readme/CONTRIBUTORS.rst DELETED Viewed

@@ -1,12 +0,0 @@
-* Simone Orsi <simahawk@gmail.com>
-* Thierry Ducrest <thierry.ducrest@camptocamp.com>
-* Guewen Baconnier <guewen.baconnier@camptocamp.com>
-* Raphaël Reverdy <raphael.reverdy@akretion.com>
-* Sébastien Beau <sebastien.beau@akretion.com>
-* Jacques-Etienne Baudoux <je@bcim.be>
-Design
-~~~~~~
-* Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
-* Jacques-Etienne Baudoux <je@bcim.be>

odoo/addons/shopfloor_mobile/readme/CREDITS.rst DELETED Viewed

@@ -1,5 +0,0 @@
-**Financial support**
-* Cosanum
-* Camptocamp R&D
-* Akretion R&D

odoo/addons/shopfloor_mobile/readme/DESCRIPTION.rst DELETED Viewed

@@ -1,31 +0,0 @@
-Frontend for Shopfloor app.
-The work is organized in scenario.
-A scenario represents a process in the warehouse (eg: receive, deliver).
-The app allows to start each process through the main menu.
-Each scenario is linked to a specific menu item which can be configured in the backend.
-Each scenario drives you through the work to do.
-Tech details
-~~~~~~~~~~~~
-* This frontend is built on top of `VueJS <vuejs.org>`_  and `VuetifyJS <vuetifyjs.com/>`_
-  and relies on `shopfloor` module that exposes REST API in Odoo
-  (based in turn on `base_rest <https://github.com/OCA/rest-framework/tree/13.0/base_rest>`_).
-* The whole business logic comes from `shopfloor` module,
-  this module takes care of providing a nice and reactive UI to work with.
-* No Odoo JS is used, no assets machinery used.
-  Static assets are loaded straight, served by a specific controller.
-  This app is a Single Page App, hence resources are loaded only once.
-  The version of the module appended to the URL of each resources
-  makes sure it's not cached when the version changes.
-* When developing you can use a demo mode which allows to define interactive scenario
-  with pure JS demo data, without interacting with Odoo.
-  Nothing to deal with Odoo demo data.

odoo/addons/shopfloor_mobile/readme/ROADMAP.rst DELETED Viewed

@@ -1,29 +0,0 @@
-* Split module by scenario
-* Improve documentation and demo data
-* Document each component
-* Document demo mode
-* Find / create a nice icon
-* Finish base translations (move all UI strings to translatable terms)
-* Use SCSS
-* Refactor states definition
-  States are now part of the scenario data. They should be specific objects with their own class.
-  They should also provide all the actions that should be displayed w/ their handlers when needed.
-  Actions can be popup actions or buttons at the bottom of the screen.
-  The tricky part here could be how to register this states for the given component.
-  Today states have access to the full object of the scenario component as they are part of it.
-  `_get_state_spec` could probably lookup for registered states
-  (eg: when you register a component in the registry you should provide states as well).
-  When we'll have states in this fashion we should also consider if they should provide their own template.
-  This way the component template will hold only the generic bits of the scenario.
-* Back buttons should be smarter
-  In some cases getting back using history is fine but very often this could lead to outdated data display.
-  To mitigate this in particular scenario's steps, custom handlers for the back action have been implemented.
-  For instance, in cluster_picking when you hit back on manual selection it forces the state to go to start and reload.
-  For starting we should provide `on_back` property to all states where we want to display it
-  (no more specific check on the state to display this button).
-  This part is also related to "Refactor states definition".
-* Go through `_.forEach` and similar calls to replace them w/ vanilla JS (eg: `.map()`)

odoo/addons/shopfloor_mobile/readme/USAGE.rst DELETED Viewed

@@ -1,34 +0,0 @@
-Pre-requisites
-~~~~~~~~~~~~~~
-* Your Odoo instance is accessible via mobile device
-* You have an API Key configured
-Start the app
-~~~~~~~~~~~~~
-* Go to "Inventory -> Configuration -> Shopfloor -> Shopfloor App"
-* In the login screen fill in your API key
-* Hit "Login"
-Select a profile
-~~~~~~~~~~~~~~~~
-Several profiles can be configured in the backend,
-you must choose one before starting.
-* Tap on "Configure profile"
-* Select a profile
-This will load all available menu items for the selected profile.
-Change language
-~~~~~~~~~~~~~~~
-* Go to "Settings -> Language"
-* Select a language
-Customization
-~~~~~~~~~~~~~
-Please refer to `shopfloor_mobile_custom_example`.

{odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info → odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info}/WHEEL RENAMED Viewed

File without changes

{odoo_addon_shopfloor_mobile-18.0.1.0.0.3.dist-info → odoo_addon_shopfloor_mobile-18.0.1.0.1.dist-info}/top_level.txt RENAMED Viewed

File without changes

odoo-addon-shopfloor-mobile 18.0.1.0.0.3__py3-none-any.whl → 18.0.1.0.1__py3-none-any.whl

odoo-addon-shopfloor-mobile 18.0.1.0.0.3py3-none-any.whl → 18.0.1.0.1py3-none-any.whl