Trigger new window in render, run events on main

[stevenmwade]

We currently need to login via a companies webpage (wordpress) so we must create a new window and run all those processes to get the user information. We have that working, but what we need is to trigger the window in the event process, but need to run the event emitters in the main process because it is highly suggest not to use remote for app and we need to write their information to a cached file.

Remote browser window says it is created in the main process but there is no way to run the emitters without an window ready or open. What would be the best way to go about this?

[leedohm]

A lot of people believe that they need to run stuff in the main process. In the vast majority of cases, you don’t and shouldn’t. See the discussion here:

Electron App Database File Structure/Code Structure

Hello Electron Community! Right to the question. I am using sqlite3 in my Electron application, and I was wondering as to where the logical place for the code pertaining to models and migrations to live. I have an image with my current file structure for my application. Thoughts? [image] Additionally, again pertaining to db usage conventions, where should db initialization and query logic live? As it currently stands, I initialize the db and attach it to the global in main.js on the Brows…

(The above discussion uses the old terminology … atom-shell → electron and browser process → main process)

[stevenmwade]

But if I’m not in the main process then I don’t have access to app and app.getPath so I can save user information. Do I really use remote with app?

[leedohm]

You can subclass BrowserWindow and pass whatever information you need across to it when you construct it, including app.getPath. You also have all of the Node libraries at your disposal … so you could call process.cwd() or something.