solprop.service#
The service between a front end and solprop: messages, kernel, runs, machines.
A front end (the desktop window of solprop-gui) talks to this layer through one set
of request and event messages (solprop.service.messages). The window’s process
imports only the light modules; the heavy ones run in its children. Nothing here imports
Qt, and nothing else in solprop imports this package.
The kernel, a warm solprop answering checks, previews, design tools and readings as plain data:
solprop.service.clientandsolprop.service.kernel(the process) andsolprop.service.handlers(the request table), drawing ondesign,explore,sheet,waveguide,results,radial_pages,postprocessandfigures;beam,reduce,scan_reductionsandrecipesare shared with the runs and the window.Runs, each a job of its own that writes its record:
solprop.service.worker(the spec),solprop.service.runandsolprop.service.job(running it),solprop.service.recordandsolprop.service.frames(its record),solprop.service.runsandsolprop.service.states(their states).Other machines:
solprop.service.machines,solprop.service.agent,solprop.service.launchandsolprop.service.install.
This is front-end support, not part of the user interface: it changes without notice.
The design is docs/dev/gui/design.md (13.3, 13.4).
Its design is the desktop front end’s (docs/dev/gui/design.md, sections 13.3 and
13.4); its modules are documented in their source.