Separate API? and GUI code

[hal-shu-sato]

Is your feature request related to a problem? Please describe.

Now, we write both frontend process and backend process together. But, as we develop apm more, the code becomes difficult to read. We should separate them.

Describe the solution you'd like

Separate API? and GUI code.

Describe alternatives you've considered

Additional context

I can't find a good word that means backend process. If you have a good one, please let me know.

[mitosagi]

What part of the code do you want to separate exactly? To me it looks like the current apm is able to separate the code into each file pretty well.

[hal-shu-sato]

I had trouble with npm's package circulation before. And I think the error handling could be improved.

That's what I thought, but then I started to wonder if it happens only in libs. Maybe we should just refactor the libs.

[mitosagi]

I want to separate files that do not have internal dependencies such as apmJson and getHash from those that do such as mod and convertId.

[hal-shu-sato]

That's true. I agree with that.

Just now, I wanted to cut out the part of the file (fs module) that is related to #312. I create a new issue.

[hal-shu-sato]

I think the current code is too complicated... I want to refactor something... We may have to look at large scale as well.

[hal-shu-sato]

This is an important thing for developing the Electron app. In Electron's design to begin with, the idea seemed to be to separate the back-end and front-end code into a main process and a renderer process. It was because I used to be unaware of this that I started writing code. I still think it is necessary to separate them, so I am working on it.