A couple of things caught my eye during the ongoing refactor of the structure of v7, one of which is the odd choice of turning all shell components into app processes instead of system services. I'm talking about the following processes:
contextMenu (not sure if this can be a service because it has svelte code)SystemShortcutsProcTrayHostProcArcFindProc
I don't know why these aren't services, possibly because the service host wasn't a set-in-stone thing when these applications were first written, but regardless. These app processes should be services to be in-line with the rest of the architecture of v7. I'm not sure about contextMenu though, since it actually does make use of the rendering aspect of AppProcess to display the actual menu itself. One potential solution would be to pull apart the data- and rendering 'parts' of the process, but that's still left to be determined.
A couple of things caught my eye during the ongoing refactor of the structure of v7, one of which is the odd choice of turning all shell components into app processes instead of system services. I'm talking about the following processes:
contextMenu(not sure if this can be a service because it has svelte code)SystemShortcutsProcTrayHostProcArcFindProcI don't know why these aren't services, possibly because the service host wasn't a set-in-stone thing when these applications were first written, but regardless. These app processes should be services to be in-line with the rest of the architecture of v7. I'm not sure about
contextMenuthough, since it actually does make use of the rendering aspect ofAppProcessto display the actual menu itself. One potential solution would be to pull apart the data- and rendering 'parts' of the process, but that's still left to be determined.