I was wrong about the DOM. Verified from Odoo 19 source on entech:
web/static/src/views/fields/float/float_field.xml
web/static/src/views/fields/char/char_field.xml
web/static/src/views/list/list_renderer.xml
Float/Char fields render as a BARE <span> (read mode) or BARE
<input class="o_input"> (edit mode) directly inside the <td>.
There is NO .o_field_widget wrapper. So all my prior CSS targeting
.o_field_widget matched nothing.
Also discovered: Odoo's getCellClass() in list_renderer.js calls
canUseFormatter() which strips custom <field> classes when the
column has widget="..." set:
canUseFormatter(column, record) {
if (column.widget) {
return false; // ← class stripped here
}
...
}
So o_fp_iw_value class doesn't even land on cells with
widget="boolean_toggle"/"image". Those cells render natively;
boolean toggle and image styling now targets the widgets directly
wherever they appear (.o_boolean_toggle, .o_field_image).
Fix: put visible chrome (border, bg, padding, min-height) on the
<td> itself for prompt/meta/value/extras cells. Make inner span
and input transparent + inherit. Focus ring travels up via
:focus-within on the td.
Cells now look like obvious input boxes from first paint, regardless
of whether the user has clicked into edit mode.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
93 lines
4.2 KiB
Python
93 lines
4.2 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
{
|
|
'name': 'Fusion Plating — Native Jobs',
|
|
'version': '19.0.8.16.3',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Native plating job model — replaces mrp.production / mrp.workorder bridge.',
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'maintainer': 'Nexa Systems Inc.',
|
|
'support': 'support@nexasystems.ca',
|
|
'price': 0.00,
|
|
'currency': 'CAD',
|
|
'description': """
|
|
Native Plating Job Bridge
|
|
=========================
|
|
|
|
Bridges fp.job and fp.job.step (defined in fusion_plating core, Phase 1 of
|
|
the migration spec dated 2026-04-25) to the rest of the Fusion Plating
|
|
module family — configurator, portal, logistics, quality, certificates.
|
|
|
|
Coexists with fusion_plating_bridge_mrp during the migration period.
|
|
Activate native jobs via the x_fc_use_native_jobs settings flag (default:
|
|
False). When False, SO confirm continues to create mrp.production records
|
|
through bridge_mrp. When True, SO confirm creates fp.job records here.
|
|
|
|
19.0.4.0.0 (2026-04-24): Operator UI consolidation. The parallel
|
|
OWL/controller stack (job_process_tree, job_plant_overview,
|
|
job_manager_dashboard, job_tablet) was removed. The canonical
|
|
operator-facing UIs now live in fusion_plating_shopfloor and bind
|
|
directly to fp.job / fp.job.step. This module retains lifecycle hooks,
|
|
SO → fp.job creation, reports, and the QR-scan redirect.
|
|
|
|
See docs/superpowers/specs/2026-04-25-fp-native-job-model-design.md for
|
|
full design rationale and §6.2 of the implementation plan for task list.
|
|
""",
|
|
'depends': [
|
|
'fusion_plating', # fp.job, fp.job.step, fp.work.centre
|
|
'fusion_plating_batch', # fusion.plating.batch (Phase 3)
|
|
'fusion_plating_certificates', # fp.certificate, fp.thickness.reading
|
|
'fusion_plating_configurator', # fp.part.catalog, fp.coating.config
|
|
'fusion_plating_kpi', # fusion.plating.kpi.value (Phase 4)
|
|
'fusion_plating_logistics', # fusion.plating.delivery
|
|
'fusion_plating_notifications', # fp.notification.template (Phase 4)
|
|
'fusion_plating_portal', # fusion.plating.portal.job
|
|
'fusion_plating_quality', # fusion.plating.customer.spec, fusion.plating.quality.hold
|
|
'fusion_plating_receiving', # fp.racking.inspection (Phase 3)
|
|
'fusion_plating_reports', # paperformat helpers, customer_line_header (Phase 5)
|
|
'fusion_plating_shopfloor', # canonical operator UI consoles
|
|
],
|
|
'data': [
|
|
'security/legacy_groups.xml',
|
|
'security/ir.model.access.csv',
|
|
'data/fp_cron_data.xml',
|
|
'views/res_config_settings_views.xml',
|
|
'views/fp_job_step_quick_look_views.xml',
|
|
'views/fp_job_form_inherit.xml',
|
|
'views/fp_job_quality_buttons.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/fp_certificate_views.xml',
|
|
'views/fp_job_consumption_views.xml',
|
|
'views/fp_step_priority_views.xml',
|
|
'views/jobs_in_shopfloor_menu.xml',
|
|
'views/legacy_menu_hide.xml',
|
|
'wizards/fp_job_step_move_wizard_views.xml',
|
|
'wizards/fp_job_step_input_wizard_views.xml',
|
|
'report/report_fp_job_sticker.xml',
|
|
'report/report_fp_job_traveller.xml',
|
|
'report/report_fp_job_wo_detail.xml',
|
|
'report/report_fp_job_margin.xml',
|
|
],
|
|
'assets': {
|
|
# Sub 12d — Step Details quick-look modal styles + Sub 12e — Record
|
|
# Inputs Wizard v3 card layout. Registered in both bundles so
|
|
# light + dark mode each compile correctly
|
|
# ($o-webclient-color-scheme branches at compile time per
|
|
# CLAUDE.md note).
|
|
'web.assets_backend': [
|
|
'fusion_plating_jobs/static/src/scss/fp_step_quick_look.scss',
|
|
'fusion_plating_jobs/static/src/scss/fp_job_step_input_wizard_v3.scss',
|
|
],
|
|
'web.assets_web_dark': [
|
|
'fusion_plating_jobs/static/src/scss/fp_step_quick_look.scss',
|
|
'fusion_plating_jobs/static/src/scss/fp_job_step_input_wizard_v3.scss',
|
|
],
|
|
},
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
'license': 'OPL-1',
|
|
}
|