4 ms·

Using the browser installed in the system instead would reduce resource usage even further </ironic>

by bigato 8y ago

oblio 8y ago
You're kidding, but it should.
kodablah 8y ago
Some systems don't allow their most modern browser to be easily consumed. Also, Chromium has features that some default-distro browsers don't. Finally, using browsers on the system don't always give flexibility that Electron does and even when they do, the abstraction to the greatest common factors just so you can work cross-platform leave a lot out.
ttoinou 8y ago
There's https://nodekit.io/ https://nodekit.io/ But it seems it's a dead project :-( And https://github.com/zserge/webview https://github.com/zserge/webview doesn't seem to offer a lot of cross platform functionality
- 52-6F-62 8y ago
  > And https://github.com/zserge/webview https://github.com/zserge/webview doesn't seem to offer a lot of cross platform functionality Not to drag this too far off topic—but outside of the API differences between webviews— what do you mean? I imagine it could be used to serve something like Slack's web app for example which [I imagine] would have been built to bend to each of those browsers' functionality to begin with.
  - RussianCow 8y ago
    The point is that you would have to re-implement Node's/Electron's APIs on top of each browser engine, so that OS functionality could be exposed to the JavaScript code. That webview project does not expose very much in the way of system API calls, which is what the parent was referring to.
    - 52-6F-62 8y ago
      I see now. So basically for anything beyond replicating a web app or pointing to (à la Slack, HipChat, Stride, etc)—or anything else that doesn't require native access. It's a very cool library outside of that—for any gawkers here.
      - ttoinou 8y ago
        That would be a cool project to try to make electron without blink
  - ttoinou 8y ago
    Unified API for UI dialogs, file handling, file drag and drop, clipboard, keyboard shortcuts, http(s) requests, image loading, OS notifications, OS menus etc.. ? Maybe one should use the webview repo in conjunction with another GUI cross platform library ?
Spivak 8y ago
Kind of defeats the purpose of bundling your runtime for the purpose of having a single target to test against.
nkkollaw 8y ago
Yes but then what if apps are built for another version?
- RussianCow 8y ago
  Apps like Slack that expose a web version of the product are tested across different browsers anyway, so that wouldn't change unless your Electron app was desktop-only.
- pjmlp 8y ago
  That is the whole purpose of the Web.

Using the browser installed in the system instead would reduce resource usage even further </ironic>

by bigato 8y ago

Using the browser installed in the system instead would reduce resource usage even further </ironic>

oblio 8y ago

You're kidding, but it should.

kodablah 8y ago

Some systems don't allow their most modern browser to be easily consumed. Also, Chromium has features that some default-distro browsers don't. Finally, using browsers on the system don't always give flexibility that Electron does and even when they do, the abstraction to the greatest common factors just so you can work cross-platform leave a lot out.

ttoinou 8y ago

There's https://nodekit.io/ https://nodekit.io/ But it seems it's a dead project :-( And https://github.com/zserge/webview https://github.com/zserge/webview doesn't seem to offer a lot of cross platform functionality

52-6F-62 8y ago
> And https://github.com/zserge/webview https://github.com/zserge/webview doesn't seem to offer a lot of cross platform functionality Not to drag this too far off topic—but outside of the API differences between webviews— what do you mean? I imagine it could be used to serve something like Slack's web app for example which [I imagine] would have been built to bend to each of those browsers' functionality to begin with.
- RussianCow 8y ago
  The point is that you would have to re-implement Node's/Electron's APIs on top of each browser engine, so that OS functionality could be exposed to the JavaScript code. That webview project does not expose very much in the way of system API calls, which is what the parent was referring to.
  - 52-6F-62 8y ago
    I see now. So basically for anything beyond replicating a web app or pointing to (à la Slack, HipChat, Stride, etc)—or anything else that doesn't require native access. It's a very cool library outside of that—for any gawkers here.
    - ttoinou 8y ago
      That would be a cool project to try to make electron without blink
- ttoinou 8y ago
  Unified API for UI dialogs, file handling, file drag and drop, clipboard, keyboard shortcuts, http(s) requests, image loading, OS notifications, OS menus etc.. ? Maybe one should use the webview repo in conjunction with another GUI cross platform library ?

Spivak 8y ago

Kind of defeats the purpose of bundling your runtime for the purpose of having a single target to test against.

nkkollaw 8y ago

Yes but then what if apps are built for another version?

RussianCow 8y ago
Apps like Slack that expose a web version of the product are tested across different browsers anyway, so that wouldn't change unless your Electron app was desktop-only.
pjmlp 8y ago
That is the whole purpose of the Web.