You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #15, there is no need for the frontend and backend to be split into two separate processes. Moving them into the same process (probably in separate threads, with a new backend thread created for each task) would have some benefits:
It would allow removing the awkward message passing over pipes, instead doing simpler communication between threads.
The front end would have admin privileges, allowing issues such as Edit menu button #12 to be trivial, instead of needing to pass messages to the backend.
There is less possibility of a one of the two processes dying while the other lives. Currently, if the frontend dies, the backend might sit in the background indefinitely, while if the backend dies, the frontend may appear to be unresponsive.
lickdir_t can be more complex, allowing the use of pointers, lists, etc.
Since almost all of the GUI code would need to be refactored, it would probably be beneficial to completely rewrite it. This would include:
Changing the GUI toolkit or language. This can either allow Windows 9x support (Support GUI in Win 9x #6), or it can be decided a Windows 9x GUI is not worth the effort. I'm leading towards the latter, because I have not received any feature requests for 9x support. In that case, it might be possible to use another toolkit, or even another language.
A redesign of the architecture. The current architecture focuses on the backend taking simple commands. A new architecture could give the backend a scenario or list of commands, with the frontend simply providing feedback to the user.
After #15, there is no need for the frontend and backend to be split into two separate processes. Moving them into the same process (probably in separate threads, with a new backend thread created for each task) would have some benefits:
lickdir_t
can be more complex, allowing the use of pointers, lists, etc.Since almost all of the GUI code would need to be refactored, it would probably be beneficial to completely rewrite it. This would include:
The text was updated successfully, but these errors were encountered: