|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Vugu||4,570||2||30||3 months ago||14||January 31, 2022||101||mit||Go|
|Vugu: A modern UI library for Go+WebAssembly (experimental)|
|Tg Luci||8||5 years ago||2||Shell|
|Package Files required for build of Luci|
|Netconn||7||8 months ago||n,ull|
|An open-source router and firewall with a web GUI for Linux. Utilizes XDP for fast packet processing. Currently in development.|
|Probemap||7||3 years ago||2||mit||Python|
|Gather and Google Map router names in probe requests. GUI, SQLite DB.|
|Go Gui||5||2 years ago||Go|
|一键生成 golang gin+gorm crud 代码|
|Gloomhaven Helper Headless||5||2 years ago||mit||Shell|
|Headless Gloomhaven Helper server in Docker|
|Maze Router Lee Algorithm||3||a year ago||mit||C|
|Single Layer Maze Router|
|Ed Router||3||5 years ago||other||C#|
|Desktop neutron router, a helper for Elite: Dangerous|
|Cppcam||3||2 years ago||1||C++|
|a rudimentary but functional 3D CAD/CAM program for generating basic tool-paths for routers and lathes.|
|Vnoc20||2||7 years ago||1||C|
|This is a flexible trace-driven cycle-accurate simulator for homogeneous NoCs. It has integrated Orion 2 power model as well as a simple GUI, useful for debugging and displaying routers congestion. In addition, it has frequency throttle and frequency boost based DVFS (dynamic voltage and frequency scaling) implemented at router level. It is meant to be used as either an NoC simulation tool or a platform for implementing and investigating DVFS ideas.|
Vugu is an experimental library for web UIs written in Go and targeting webassembly. Guide and docs at https://www.vugu.org. Godoc at https://godoc.org/github.com/vugu/vugu.
If you've ever wanted to write a UI not in JS but pure Go... and run it in your browser, right now... That (experimental;) future is here!
Introducing Vugu (pronounced /ˈvuː.ɡuː/), a VueJS-inspired library in Go targeting wasm.
No node. No JS. No npm. No node_modules folder competing with your music library for disk space.
vg-html='vugu.HTML("...")'(see https://www.vugu.org/doc/files/markup#vg-content) and existing DOMEvent code should fix by simply removing the pointer i.e. change
event vugu.DOMEvent- and also make sure to
go get -u github.com/vugu/vugu/cmd/vugugenagain. I generally try to avoid these sorts of breaking changes but it's better to do them sooner rather than later.
vg-comptag now allows programmatic component selection. A pattern for wiring large applications with lots of components is in place and will be tested further as dev moves forward. Next steps include just a bit more dev and testing on the router and then updating vugu.org to use these new features and bring the documentation up to date.
.prop=syntax implemented, various cleanup, imports are deduplicated automatically now, started on nested component implementation and all of that craziness.
<html>tag) now supported on component-refactor branch, updated CSS and JS support figured out and implementation in-progress
Join the conversation: Gophers on Slack, channel #vugu
Get started: http://www.vugu.org/doc/start
Still a work in progress, but a lot of things are already functional. Some work really well.
It's built more like a library than a framework. While Vugu does do code generation for your .vugu component files, (and will even output a default main_wasm.go for a new project and build your program automatically upon page refresh), fundamentally you are still in control. Overall program flow, application wiring and initialization, the render loop that keeps the page in sync with your components - you have control over all of that. Frameworks call your code. Vugu is a library, your code calls it (even if Vugu generates a bit of that for you in the beginning to make things easier). One of the primary goals for Vugu, when it comes to developers first encountering it, was to make it very fast and easy to get started, but without imposing unnecessary limitations on how a project is structured. Go build tooling (and now the module system) is awesome. The idea is to leverage that to the furthest extent possible, rather than reprogramming the wheel.
So you won't find a vugu command line tool that runs a development server, instead
you'll find in the docs an appropriate snippet of code you can paste in a file and
go run yourself. For the code
generation while there is an http.Handler that can do this upon page refresh, you also can (and should!) run
go generate. There are many small decisions in Vugu which follow this philosophy: wherever reasonably possible,
just use the existing mechanism instead of inventing anew. And keep doing that until there's proof that something
else is really needed. So far it's been working well. And it allows Vugu to focus on the specific things it
brings to the table.