This was the one may things which decided to go for the renderer or another method to use as downloader helper. another issue is it cannot be customized even setting simple header. This is also easy to do, you can use the electron downloader api, but there’re few issues for example if you want to cancel an downloading item it’s easy but after restarting the app or losing the download item you won’t be able to resume it. also will work on the browser, so you’re not depend on the main process.ĭo i need to have actions? (Cancel, Pause, Resume) This is what you need to show the progress/status on downloading items. You should also consider the web version in the client side there is not main process and there is no IPC module to communicate through the channels. This is important thing when you have to deal with files and buffers in your application. ![]() Just renderer code base and ignoring the native dependencies. Has or Will have my application a website version? Like Slack. Here are some topics and questions you may need ask yourself before start coding: You should think about the consequences and be independent. ![]() An action could be choosing a library or framework or installing a simple package from npmjs. If your project is growing fast and the future is important for you, Then you need to think about every thing before any actions. ![]() I was developing an Electron application a while ago and one of the challenges was downloading files and did some researches about it and saw that the Electron download API wasn’t the only option and it was tricky to use. My own downloader, will be live soon □the icons are fake for now □ If you want to deal with downloading files, better read this before start coding □
0 Comments
Leave a Reply. |