Roadmap? about cycle-electron-driver HOT 5 OPEN

The approach I had been taking was going through the electron API item by item (starting with the app object) and figuring out how to categorize the item to fit logically within a driver. I tried to make sure there was documentation + tests for each iteration. After the app object, I planned on just moving on to the next piece of the API.

My roadmap wasn't really any more sophisticated than having complete electron API coverage. The project has been collecting dust for so long that the API may have diverged from what I was working with originally, and even back then there was a lot of work left to do.

from cycle-electron-driver.

It may be helpful to flesh out the API mappings with the entire electron API so there's an idea of % complete and what's left to cover.

from cycle-electron-driver.

Good idea! I'll proceed with the API mappings.

from cycle-electron-driver.

Hi @apoco, I've realized I'm not going to use cycle for the main process. Besides a fairly complete electron driver I'd need additional drivers for the node features I want, and that's not worth the effort. Much simpler to use cycle in the renderer process only. The renderer API is also much smaller. I'm building some drivers for the renderer as part of my current project, and will eventually publish them elsewhere. Thanks anyway for your work and support!

from cycle-electron-driver.

Great, look forward to seeing your work on the renderer process. Good idea to focus on the important bits.

from cycle-electron-driver.