4 ms·

Hi, I am one of the developers. You seem to be mistaken, it is not a WebKit shell (we are currently working on a web engine variant). It is actually a standalon

Hi, I am one of the developers. You seem to be mistaken, it is not a WebKit shell (we are currently working on a web engine variant). It is actually a standalone Lisp program that defines a protocol for client browser implementations. Please see the following file for more information: https://github.com/atlas-engineer/next/blob/master/ports/README.org https://github.com/atlas-engineer/next/blob/master/ports/REA... Eventually we would like to make our own web-renderer, but we recognize that it is a lot of work, and a bit away

deleted 7y ago
[deleted]
msla 7y ago
> Hi, I am one of the developers. You seem to be mistaken, it is not a WebKit shell (we are currently working on a web engine variant). It is actually a standalone Lisp program that defines a protocol for client browser implementations. OK, looking through the README in the ports/ directory, I see this: > Next is made of two programs: > The Lisp core which offers the user full control over the browsing. It’s 100% Common Lisp. > The “platform port”, which only purpose is to display a window with two components: the minibuffer and the web view. > The two parts communicate via D-Bus, an RPC system. The Lisp core sends a D-Bus request to the platform port (for example, “open this URL”); the platform port acts upon it and sends a D-Bus response back to the Lisp core. So you've put the WebKit stuff into another process, but your browser is WebKit based, unless I completely misunderstood what I just read. You couldn't use Next to drive Firefox, for example, without some interesting re-writes on the Firefox end. (Just to make it abundantly clear: I think this is a really neat hack and a good way to separate concerns, but the way you phrased things confused me until I dug into the README you linked to and read some source code.)
- bryanrasmussen 7y ago
  I wonder if you could do what remote browser does and drive Firefox by the web extensions api, https://github.com/intoli/remote-browser https://github.com/intoli/remote-browser.
  - jmercouris 7y ago
    I wonder that as well, that is a very fascinating link, thank you!

deleted 7y ago

[deleted]

msla 7y ago

> Hi, I am one of the developers. You seem to be mistaken, it is not a WebKit shell (we are currently working on a web engine variant). It is actually a standalone Lisp program that defines a protocol for client browser implementations. OK, looking through the README in the ports/ directory, I see this: > Next is made of two programs: > The Lisp core which offers the user full control over the browsing. It’s 100% Common Lisp. > The “platform port”, which only purpose is to display a window with two components: the minibuffer and the web view. > The two parts communicate via D-Bus, an RPC system. The Lisp core sends a D-Bus request to the platform port (for example, “open this URL”); the platform port acts upon it and sends a D-Bus response back to the Lisp core. So you've put the WebKit stuff into another process, but your browser is WebKit based, unless I completely misunderstood what I just read. You couldn't use Next to drive Firefox, for example, without some interesting re-writes on the Firefox end. (Just to make it abundantly clear: I think this is a really neat hack and a good way to separate concerns, but the way you phrased things confused me until I dug into the README you linked to and read some source code.)

bryanrasmussen 7y ago
I wonder if you could do what remote browser does and drive Firefox by the web extensions api, https://github.com/intoli/remote-browser https://github.com/intoli/remote-browser.
- jmercouris 7y ago
  I wonder that as well, that is a very fascinating link, thank you!