It runs on all major platforms and uses a combination of Chromium and Node. The main component here is NW.js (previously known as node-webkit). gowdĭesktop UI with GO, HTML, CSS and NW.js. This (commercial) package can made cross-platform and embeddable user interface with JavaScript, CSS, HTML. This is essentially a Go binding for Sciter.
Go bindings for Sciter: the Embeddable HTML/CSS/script engine for modern desktop UI development. There is a demo app which shows a rather nice interface. Go-astilectron are Go bindings for the Astilectron app. That means your app will run inside a special Chromium browser.Īstilectron is an Electron app, it provides an API over a TCP socket that allows executing Electron’s method as well as capturing Electron’s events. You can make an app with HTML/JS/CSS and it’s cross platformĮlectron is made with Node.js and Chromium. The go-astilectron package is an Electron based setup.
Meaning other platforms are not supported. There seems to be only a MacOS and web driver. A driver contains allows the app package to work on a platform. The app package can create apps with GO, HTML and CSS. Which package is best depends on your needs. One advantage of this is that apps will work on many different operating systems (Mac, Windows). Many apps are going in the web-based direction, think Google apps or Cloud apps. The most common are web-based and desktop-based. There are several packages for making go gui’s. the debugger's gone a little wonky on me a couple of times while using it (that could have been due to it being for mozilla plugins, though), but otherwise it seems straightforward enough to me.A GUI can be created with a go package. it lets you use your cross platform or existing c++ code for your application logic and then use obj-c for your ui and platform specific stuff. You won't want to mix those two in the same app (though it can be done).Ok, I'm not sure where I'm going with this, but to summarize: learn obj-c, you'll be glad you did.edit: obj-c++ isn't that bad. As an exception, HIToolbox (carbon gui toolkit) has a c interface whereas AppKit (cocoa gui toolkit) is objective-c (and others). Just link in both the Cocoa and Carbon frameworks, do the appropriate imports, and name the file. I often find myself using functionality from both in the same programs. Carbon is not going away.In general, the Objective-C interfaces (Cocoa) are nicer than their procedural c (carbon) counterparts, so if you go through the trouble of learning obj-c you may as well use them.It turns out that the division between carbon and cocoa is not as sharp as some would have you think.
A lot of Carbon and Cocoa is just becoming interfaces to the same code.
0 kommentar(er)
