remarkable VS webview

Simultaneously the #1 trending developer on GitHub across all languages (out of ~17 million developers at the time) with multiple #1 trending projects: Remarkable (https://github.com/jonschlinkert/remarkable), a markdown parser and compiler (also across all languages, out of ~7 million projects), Enquirer (https://github.com/enquirer/enquirer), a stylish, user-friendly prompt system.

Since then they've made things that are IMO quite useful, like enquirer, micromatch, and remarkable.

mdview (sources) uses RemarkableJS for MD->HTML conversion.

will give you split-view out-of-the-box. But web dev's will start looking for frameworks in order to achieve this simple task that browser have internally already.

TL;DR: Web and desktop UIs use inherently different models. You can share parts between these two different platforms but only parts, really.

[1] Remarkable JS: https://github.com/jonschlinkert/remarkable

I have a project I started last year using https://github.com/webview/webview developing on macOS Mojave. I'm working on an update currently adding new features and suddenly I'm getting all sorts of errors just trying to `go get` the library either to update or pull for a test project. The errors have everything to do with CGO and I'm not much of a C/C++ dev. But I've worked through most of those errors. Now after upgrading to Big Sur I'm facing a whole new slew of problems. I've once again spent days working through many of the issues but now am stumped and need help.

you can also have a look at webview wraper like https://github.com/webview/webview . This comes with Java binding as well, but it meant to be running in headful environmemt

Neutralino itself doesn't leverage a thing, it uses Serge Zaitsev's Webview as I already mentioned.

Go has https://github.com/webview/webview and the embed package so you can actually embed all the JS and assets and the web browser in <5MB, much better than electron

https://github.com/webview/webview lets you use webview without all the bloat added by electron.

the webview library is a great solution if you just want a webview implementation and don't need all the other api of the system. If your are making a PWA kind app (like a email client), you should take a look into it. Server Side Blazor apps are also welcome, because this library also have a C# binding. This library implements the from scratch part that I have talked before, It has a implementation for windows (with the new Chromium Edge), one for OSX (using Webkit) and one for linux (also using webkit). If we are talking about compatibility, then a problem arrives, dealing with 3 different rendering engines (webkitgtk is not the same as webkit in my opinion) support for specific features that only exist in one Rendering engine may lead you to creating them from scratch from other systems. Not to mention that you don't have a api for open system dialogs and message boxes out of the box.

{ "name": "gowebview", "buildsystem": "simple", "build-options": { "env": { "GOBIN": "/app/bin/" } }, "build-commands": [ ". /usr/lib/sdk/golang/enable.sh; export GOPATH=$PWD; go env -w GO111MODULE=off; go install github.com/webview/webview" ], "sources":[ { "type": "git", "url": "https://github.com/webview/webview", "commit": "9c1b0a888aa40039d501c1ea9f60b22a076a25ea", "dest": "src/github.com/webview/webview" } ] }, { "name": "discordlogin", "buildsystem": "simple", "build-options": { "env": { "GOBIN": "/app/bin/" } }, "build-commands": [ "mkdir -p src/github.com/diamondburned/discordlogin; mv -vn ./* src/github.com/diamondburned/discordlogin; . /usr/lib/sdk/golang/enable.sh; export GOPATH=$PWD; go env -w GO111MODULE=off; go install github.com/diamondburned/discordlogin" ], "sources": [ { "type": "git", "url": "https://github.com/diamondburned/discordlogin", "commit": "5772dfbb1dc132263b1ba396c478a93937710880" }, { "type": "patch", "path":"./patches/0002-fix-webview-dependency.patch", "use-git": true } ] },

No problem. Here is an additional thought: Instead of injecting your assets like their example shows, your game could instead run its own web server and your webview could connect to it at localhost:12345 (where 12345 is the port you started it on). You could use any C/C++ webserver library you want.

You might consider webview which is a C++ single header, cross-platform webview library. It uses WebKit (on Mac and Linux) and Edge with Chromium backend (on Windows). Unlike CEF and Electron, since it uses each platforms native webview control, the resulting binary is kilobytes in size rather than hundreds of megabytes. They have a code example demonstrating how C++ and JavaScript can communicate. You could easily write the bulk of your game logic in C++ and use HTML, CSS, and JavaScript for display only. Heck, since it's a full browser, you could even setup an NPM package for your game, bring in web dependencies if you wish, and code in a type-safe language that compiles to JavaScript, like TypeScript.

I need to do this, because Neutralino.js documentation is currently broken, and webview/webview documentation sucks; and I don't know how to maximize in Tauri.