Go-app is a package to build progressive web apps with Go programming language and WebAssembly.

Overview

go-app

Circle CI Go build Go Report Card GitHub release pkg.go.dev docs Twitter URL

Go-app is a package for building progressive web apps (PWA) with the Go programming language (Golang) and WebAssembly (Wasm).

Shaping a UI is done by using a declarative syntax that creates and compose HTML elements only by using the Go programing language.

It uses Go HTTP standard model.

An app created with go-app can out of the box run in its own window, supports offline mode, and are SEO friendly.

Documentation

go-app documentation

Install

go-app requirements:

go mod init
go get -u github.com/maxence-charriere/go-app/v8/pkg/app

Declarative syntax

Go-app uses a declarative syntax so you can write reusable component-based UI elements just by using the Go programming language.

Here is a Hello World component that takes an input and displays its value in its title:

type hello struct {
	app.Compo

	name string
}

func (h *hello) Render() app.UI {
	return app.Div().Body(
		app.H1().Body(
			app.Text("Hello, "),
			app.If(h.name != "",
				app.Text(h.name),
			).Else(
				app.Text("World!"),
			),
		),
		app.P().Body(
			app.Input().
				Type("text").
				Value(h.name).
				Placeholder("What is your name?").
				AutoFocus(true).
				OnChange(h.ValueTo(&h.name)),
		),
	)
}

Standard HTTP

Apps created with go-app complies with Go standard HTTP package interfaces.

func main() {
    // Components routing:
	app.Route("/", &hello{})
	app.Route("/hello", &hello{})
	app.RunWhenOnBrowser()

    // HTTP routing:
	http.Handle("/", &app.Handler{
		Name:        "Hello",
		Description: "An Hello World! example",
	})

	if err := http.ListenAndServe(":8000", nil); err != nil {
		log.Fatal(err)
	}
}

Getting started

Read the Getting Started document.

Contributors

Code Contributors

This project exists thanks to all the people who contribute. [Contribute].

Financial Contributors

Become a financial contributor and help us sustain go-app development. [Contribute]

Individuals

Organizations

Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]

Comments
  • Example crashing right away after go build or go run

    Example crashing right away after go build or go run

    I tried to just go build the example project then execute the binary, but it crashes right after it starts. The weird thing is if I use macpack to build it then it doesn't crash. I'm guessing the app wrapper provides data where the raw build does not.

    Go ENV

    GOARCH="amd64"
    GOBIN=""
    GOEXE=""
    GOHOSTARCH="amd64"
    GOHOSTOS="darwin"
    GOOS="darwin"
    GOPATH="/Users/euforic/go"
    GORACE=""
    GOROOT="/usr/local/Cellar/go/1.7.5/libexec"
    GOTOOLDIR="/usr/local/Cellar/go/1.7.5/libexec/pkg/tool/darwin_amd64"
    CC="clang"
    GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3x/0rnfwj_x1jz2p0gzh_gg7_600000gn/T/go-build912724629=/tmp/go-build -gno-record-gcc-switches -fno-common"
    CXX="clang++"
    CGO_ENABLED="1"
    

    Crash Output

    INFO  2017/01/30 14:00:47 driver.go:31: driver *mac.Driver is loaded
    INFO  2017/01/30 14:00:47 component.go:62: main.Hello has been registered under the tag Hello
    INFO  2017/01/30 14:00:47 component.go:62: main.AppMainMenu has been registered under the tag AppMainMenu
    INFO  2017/01/30 14:00:47 component.go:62: main.WindowMenu has been registered under the tag WindowMenu
    fatal error: unexpected signal during runtime execution
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7fffb3c24b52]
    
    runtime stack:
    runtime.throw(0x41a1554, 0x2a)
    	/usr/local/Cellar/go/1.7.5/libexec/src/runtime/panic.go:566 +0x95
    runtime.sigpanic()
    	/usr/local/Cellar/go/1.7.5/libexec/src/runtime/sigpanic_unix.go:12 +0x2cc
    
    goroutine 1 [syscall, locked to thread]:
    runtime.cgocall(0x4141160, 0xc42004df20, 0x0)
    	/usr/local/Cellar/go/1.7.5/libexec/src/runtime/cgocall.go:131 +0x110 fp=0xc42004def0 sp=0xc42004deb0
    github.com/murlokswarm/mac._Cfunc_Driver_Run()
    	??:0 +0x41 fp=0xc42004df20 sp=0xc42004def0
    github.com/murlokswarm/mac.(*Driver).Run(0xc420010280)
    	/Users/euforic/go/src/github.com/murlokswarm/mac/driver.go:56 +0x14 fp=0xc42004df28 sp=0xc42004df20
    github.com/murlokswarm/app.Run()
    	/Users/euforic/go/src/github.com/murlokswarm/app/app.go:43 +0x35 fp=0xc42004df40 sp=0xc42004df28
    main.main()
    	/Users/euforic/go/src/github.com/blevein/play/examples/mac/hello/main.go:31 +0x30 fp=0xc42004df48 sp=0xc42004df40
    runtime.main()
    	/usr/local/Cellar/go/1.7.5/libexec/src/runtime/proc.go:183 +0x1f4 fp=0xc42004dfa0 sp=0xc42004df48
    runtime.goexit()
    	/usr/local/Cellar/go/1.7.5/libexec/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc42004dfa8 sp=0xc42004dfa0
    
    goroutine 17 [syscall, locked to thread]:
    runtime.goexit()
    	/usr/local/Cellar/go/1.7.5/libexec/src/runtime/asm_amd64.s:2086 +0x1
    
    goroutine 5 [chan receive]:
    github.com/murlokswarm/app.startUIScheduler()
    	/Users/euforic/go/src/github.com/murlokswarm/app/ui.go:11 +0x51
    created by github.com/murlokswarm/app.init.1
    	/Users/euforic/go/src/github.com/murlokswarm/app/ui.go:17 +0x35
    
    opened by euforic 77
  • v9 Testing/Feedback

    v9 Testing/Feedback

    Hello there,

    I know it is pretty close to the v8 release but I had been working on a new version that removes the need to call Compo.Update() to update what is displayed on the screen.

    Unfortunately, it brings some API changes and since some of you are using this package, I wanted to share that work with you and get some feedback before releasing the new version.

    Install

    go get -u -v github.com/maxence-charriere/go-app/[email protected]
    

    Then replace your imports in your code

    What changed

    • No need to call Update anymore!
    • Compo.Defer() has been removed. Now all Dispatch()/Defer() are done from Context.Dispatch(func(Context))
    • Context.Dispatch(func()) is now Context.Dispatch(func(Context)), and UI elements are always checked before launching Component lifecycle event or HTML event handlers
    • Context has now a Defer(func(Context)) method that launches the given function after a component has been updated. It can be handy to perform action after the display is complete, like scrolling to a given location
    • Context has now an After() function that launches a function on the UI goroutine after the given time without blocking the UI
    • There is a new Component lifecycle event: OnUpdate(Context): it is launched only when a component gets updated by a parent, and should replace a scenario where a Compo.Defer() call was called in a Render() app.UI method
    • Context is now an interface. Fields are now methods:
      • Src => Src()
      • JSSrc => JSSrc()
      • AppUpdateAvailable => AppUpdateAvailable()
      • Page => Page()
    • Context has now a Context.Emit(func()) method that launches the given function and notifies parents to update their state. This should be used when implementing your own event handlers in your components, in order to properly update parent components that set a function to the event handler
    • Context has now method to encrypt and decrypt data
      • Encrypt(v interface{}) ([]byte, error)
      • Decrypt(crypted []byte, v interface{}) error
    • Context has now a method that returns device id: DeviceID() string
    • [EXPERIMENTAL] Changed the API for Stack()

    API design decisions

    • This release focuses mainly on getting the usage of the package more reactive
    • The API is designed to make unrecommended things difficult. A good example would be calling a Context.Dispatch() inside a Render() method
    • With the exception of Handler and JS-related things, everything that you might need is now available from Context. Still thinking about whether I should move Compo.ResizeContent() and Compo.ValueTo in Context though

    Please let me know what you think and where it makes things difficult to solve your problem. I will try to help you solve those and/or iterate to make things better.

    @pojntfx @beanpole135 @ZackaryWelch @mar1n3r0

    Thanks

    help wanted working on it 
    opened by maxence-charriere 41
  • Next: Windows

    Next: Windows

    Hello, some stuff are happening here. I'm writing changes that will bring better support for multi-platform dev. Would like to know what is the next driver you would like to be implement.

    opened by maxence-charriere 39
  • Recaptcha

    Recaptcha

    Hello. anyone know about getting recaptcha to properly work?

    I have it setup to prompt user with a captcha after they click register like so: https://streamable.com/4if31l

    However whenever the captcha submits the form it completely ignores my form submission handler:

    func (c *register) OnCaptchaComplete(ctx app.Context, e app.Event) {
    	e.PreventDefault()
    	print("Captcha complete")
    }
    

    here is the snippet for the element

    app.Div().Class("flex justify-center").Body(
    	app.Form().
    	ID("register-captcha-form").
    	OnSubmit(c.OnCaptchaComplete, nil).
    	Body(
    	&components.Captcha{Callback: "registerCaptchaCB"}),
    	),
    ),
    

    Is there a way to easily prevent the captcha from submitting normally and passing in the response and properly send to my handler with the recaptcha response so I can use the data to build a request to the api?

    I know I can just read the query value for the g-recaptcha-response but is there anyway I can prevent recaptcha from submitting a post / get request to the form action?

    opened by ItsVoltz 31
  • Support for push manager

    Support for push manager

    It would be nice to add subscription bootstrap into page.js (https://github.com/maxence-charriere/app/blob/c5fc1cb2b7861d05ca80284f2e38b1b7c46a69b7/internal/http/page.js)

    And callbacks to goapp.js

    opened by bgokden 28
  • How to make wasm reactive?

    How to make wasm reactive?

    The way Go treats wasm as an application means it runs and exits. This is quite limiting compared to modern JS frameworks with their reactive APIs which allow real-time reactivity on external changes. Is this even possible with the current state of things? Maybe keeping dedicated channels open infinite? This would allow all kind of things from state management stores to webhooks to websockets etc.

    Go takes a different approach, Go treats this as an application, meaning that you start a Go runtime, it runs, then exits and you can’t interact with it. This, coincidentally, is the error message that you’re seeing, our Go application has completed and cleaned up.

    To me this feels more closer to the .NET Console Application than it does to a web application. A web application doesn’t really end, at least, not in the same manner as a process.

    And this leads us to a problem, if we want to be able to call stuff, but the runtime want to shut down, what do we do?

    https://www.aaron-powell.com/posts/2019-02-06-golang-wasm-3-interacting-with-js-from-go/

    Here is an example:

    I would like to connect the app to an external state management store and make it re-render on state changes. By the time the state changed the runtime has exited, hence unless there is a channel open to keep it alive it can't react to external events after exit.

    opened by mar1n3r0 27
  • Custom Handler

    Custom Handler

    It would be nice if app made it easier to work with a custom Handler. For cases like #501 , I could implement my own handler and have fine grained control.

    opened by andrewrynhard 24
  • State management

    State management

    Looking for some broad feedback here.

    I have explored further the idea of implementing component composition also known as slots as described here: https://github.com/maxence-charriere/go-app/issues/434.

    While it definitely works in terms of simply compiling the HTML string the complexity it introduced in maintaining state between the root component and children components brought some questions up.

    The simplicity of using Go structs as state management pattern is very appealing but at the same time easily shows its limitations once the app goes beyond the scope of one page - one component structure. Surely with this pattern we can communicate between pages with HTML5 API storage solutions as long as there is no sensitive data. But as long as we outgrow this pattern in-memory state management becomes inevitable.

    This was an issue which most of JS frontend frameworks faced in their early stages and it evolved in to separate global state management modules and tools like Vuex for example.

    Global state management solves all those problems when scaling from small to enterprise-like apps but comes at a cost with it's own caveats and extra stuff to think about and handle.

    What are your thoughts on this ?

    Do you think this will become a hot topic in the near future as the project evolves or it's beyond the scope of current usage requirements ?

    Do you see the same pattern applied or a different technique Go can make use of to make it possible to scale apps ?

    opened by mar1n3r0 22
  • Implements custom elements with xml namespaces (for SVG)

    Implements custom elements with xml namespaces (for SVG)

    I added namespaces to elements and added a method to create custom tags. The reason is, that I wrote an auto converter that can translate HTML to go-app declarative syntax. While experimenting with it, I found that SVG support was missing. But adding all of the SVG seems to be a lot of work. After making a simple variant for custom elements I realized that this will not work for SVG because those elements need to be in a special namespace. So I added namespace support.

    I think my implementation is quite nice. I added a test and documentation with an example of the usage:

    func SVG(w, h int) app.HTMLCustom {
    	return app.Custom("svg", false, app.SVG).
    		Attr("width", w).Attr("height", h)
    }
    
    func Circle(cx, cy, r int, stroke string, width int, fill string) app.HTMLCustom {
    	return app.Custom("circle", false, app.SVG).
    		Attr("cx", cx).
    		Attr("cy", cy).
    		Attr("r", r).
    		Attr("stroke", stroke).
    		Attr("stroke-width", width).
    		Attr("fill", fill)
    }
    
    func (c *Dynamic) Render() app.UI {
    	return SVG(100, 100).Body(
    		Circle(50, 50, 40, "black", 3, "red"),
    		app.Text("Sorry, your browser does not support inline SVG"),
    	)
    }
    

    Of course, it adds the "xmlns" field to every element. But I think this is better than having another interface for SVG.

    I am contemplating if there should be an "xmlns" method instead which sets the namespace for every element. That may be a better solution than adding the namespace to the Custom() method. Maybe I try that too and push a commit that uses this later on.

    EDIT: There is another implementation using an XMLNS() method on the elements instead of the many parameters to Custom(). See below!

    opened by oderwat 21
  • v9.6.0

    v9.6.0

    Summary

    • Go requirement bumped to Go v1.18
    • Custom elements (Elem and ElemSelfClosing)
    • Prevent component update
    • Engine optimization that ensure a component update is done once per frame cycle
    • Customizable app-worker.js template
    • Some documentation tweak

    Fixes

    • fix #753
    opened by maxence-charriere 20
  • Added MFi Controller Support

    Added MFi Controller Support

    Summary

    I've written out a basic implementation for handling MFi controller events and providing Go callbacks that can be used to interact with the application.

    As per CONTRIBUTING.md:

    • use gofmt ✅
    • use govet ✅
    • use golint ✅
    • test coverage for . stay at 100% ✅
    • test coverage for ./internal/appjs stays at 100% ✅
    • test coverage for ./internal/bridge stays at 100% ✅
    • test coverage for ./internal/html stays at 100% ✅
    • test coverage for ./internal/core stays at 100% ✅
    • try to keep consistent coding style ✅
    • avoid naked returns (if you deal with a part of the code that have some, please refactor). ✅ (I tried my best at least 😄)
    • run goreportcard with your branch, everything that is not gocyclo must be 100%. ✅

    Fixes

    Using GameController/GCController.h, I setup handlers for the various buttons and dpads that comply with MFi. I've tested this with the Steelseries Nimbus and all keys register with their respective button.

    I wanted to add DOM events, but the contributing doc said not to get too crazy. Happy to add if this is good.

    Example

    This is how I've sandboxed the following changes:

    package main
    
    import (
    	"github.com/murlokswarm/app"
    	"github.com/murlokswarm/app/drivers/mac"
    )
    
    type MainWindow struct {
    	Controller app.Controller
    }
    
    func (mw *MainWindow) Config() app.HTMLConfig {
    
    	mw.Controller = app.NewController(app.ControllerConfig{
    		OnConnected: func() {
    			app.Log("OnConnected")
    		},
    		OnDisconnected: func() {
    			app.Log("OnDisconnected")
    		},
    		OnPause: func() {
    			app.Log("OnPause")
    		},
    		OnDpadChange: func(input app.ControllerInput, x float64, y float64) {
    			switch input {
    			case app.DirectionalPad:
    				app.Logf("OnDpad -- directional pad, x: %f, y: %f", x, y)
    			case app.LeftThumbstick:
    				app.Logf("OnDpad -- left thumbstick, x: %f, y: %f", x, y)
    			case app.RightThumbstick:
    				app.Logf("OnDpad -- right thumbstick, x: %f, y: %f", x, y)
    			}
    		},
    		OnButtonChange: func(input app.ControllerInput, value float64, pressed bool) {
    			switch input {
    			case app.A:
    				app.Logf("OnButtonChange -- a button, value: %f, pressed: %t", value, pressed)
    			case app.B:
    				app.Logf("OnButtonChange -- b button, value: %f, pressed: %t", value, pressed)
    			case app.X:
    				app.Logf("OnButtonChange -- x button, value: %f, pressed: %t", value, pressed)
    			case app.Y:
    				app.Logf("OnButtonChange -- y button, value: %f, pressed: %t", value, pressed)
    			case app.L1:
    				app.Logf("OnButtonChange -- l1 button, value: %f, pressed: %t", value, pressed)
    			case app.L2:
    				app.Logf("OnButtonChange -- l2 button, value: %f, pressed: %t", value, pressed)
    			case app.R1:
    				app.Logf("OnButtonChange -- r1 button, value: %f, pressed: %t", value, pressed)
    			case app.R2:
    				app.Logf("OnButtonChange -- r2 button, value: %f, pressed: %t", value, pressed)
    			}
    		},
    		OnClose: func() {
    			app.Log("OnClose")
    		},
    	})
    	// mw.Controller.Close()
    	return app.HTMLConfig{}
    }
    
    func (mw *MainWindow) Render() string {
    	return `
    	<div class="MainWindow">Example</div>
    	`
    }
    
    func init() {
    	mw := &MainWindow{}
    	app.Import(mw)
    }
    
    func main() {
    	app.Run(&mac.Driver{
    		URL: "/mainwindow",
    	})
    }
    

    edit: updated sandbox example

    opened by jamesalbert 19
  • Page that depens on the state

    Page that depens on the state

    Hi. I'm try to have a login feature in local go-app/docs. However, screen flickering may occurs when transition pages. Is there a way to avoid this?

    As shown below, I use the state management to determine the login state. This code is based on this repo v9.6.4.

    package main
    
    func main() {
    	app.Route("/login", newLoginPage())
    
    	app.Route("/", newHomePage())				// Assume private page
    	app.Route("/getting-started", newGettingStartedPage())	// Assume public page
    ...
    }
    
    type homePage struct {
    	app.Compo
    
    	userID string
    }
    
    func newHomePage() *homePage {
    	return &homePage{}
    }
    
    func (p *homePage) OnNav(ctx app.Context) {
    	ctx.GetState("userid", &p.userID)
    
    	if p.userID == "" {
    		ctx.Navigate("/login")
    		return
    	}
    }
    
    type loginPage struct {
    	app.Compo
    
    	name     string
    	password string
    }
    
    func newLoginPage() *loginPage {
    	return &loginPage{}
    }
    
    func (p *loginPage) login(ctx app.Context, event app.Event) {
    	if p.name != "hoge" || p.password != "foo" { // Quick check
    		return
    	}
    
    	ctx.SetState("userid", p.name,
    		app.Persist,
    		app.Encrypt,
    		app.ExpiresIn(time.Second*300),
    	)
    
    	ctx.Navigate("/")
    }
    

    When / page is accessed on the browser without being logged in, the client will redirect to /login page. However, the rendering of / page occurs at least once before it is navigated.

    Is it inappropriate to expect that the queued UI goroutines will be canceled by executing Navigate()?

    There are risks exposing content without user auth. So, I protect the content in Render().

    func (p *homePage) Render() app.UI {
    	if p.userID == "" {
    		return app.A().
    			Href("/login").
    			Text("You are being navigated.")
    	}
    
    	return ...  // Content that can be viewed after logging in.
    }
    

    After logged into / page, the screen flickers when transitioning from other page (ex. /getting-started). It also happens on reload of page. When the component was mounted, all member variables of the component are empty. I want to initialize a member with the state in OnInit(), but there is no way to do it.

    If my approach is inappropriate, please correct it.

    opened by isaribious 13
  • Prevent opening image in new tab

    Prevent opening image in new tab

    Hello, i have a following code

    app.A().Class("d-block mb-4 h-100 rounded").Body(
    					app.Img().Class("rounded img-fluid").Src("https://lipsum.app/id/61/400x300").Alt(""),
    				).DataSet("fancybox", "gallery").Href("https://lipsum.app/id/61/1600x1200"),
    			),
    

    normally this just zooms in the image, but in goApp it also opens the image in new tab, i tried intercepting the on click event, but then instead of blocking the opening image in new tab, it blocks the zoom from happening, but image get still open in new tab.

    I am not sure why this happens, if i for example put the static image, then it opens nicely, but when i close i get 404 error since now the url is not / but /web/nameofmyimage.png

    opened by zeljkosh 9
  • injecting scripts at the end of the HTML document

    injecting scripts at the end of the HTML document

    If I want to inject a javascript script I can do

    Scripts: []string{
    	"/web/js/prism.js",
    },
    

    in the app handler. Is there a place/way to inject them so they are loaded at the end of the HTML document rather than at the top? I realise I can probably do this per element, however it would be nice to do it globally across the app....

    opened by amlwwalker 9
  • Find way to have debug sessions directly from the IDE

    Find way to have debug sessions directly from the IDE

    I'm trying to build an application with go-app and created a simple form to check if the library would meet the requirements of the app. Fortunately, it does, but I cannot debug the application after it is compiled. The only thing that the IDE listens to is the main function and the first render of the main page.

    I would like to know if there is another way to debug it or if I am missing something like mappings that should be generated with the WASM (like JS mappings for chrome DevTools).

    opened by eakeur 2
  • Documentation suggestion in go-app page

    Documentation suggestion in go-app page

    Something I've noticed is that Go => WASM makes some pretty big files in general, and app.wasm size can contribute to slower page loads. I don't see a performance section in the docs, but if one were to be added it might be worth mentioning that making a cleaner separation between wasm code and server code can really reduce the wasm bundle size.

    How I did this is instead of putting the server startup code in main.go, I moved it to its own server.go file in the main package. Then I created another file called server_js.go where the same function is defined, but empty. Using the Hello World example (plus a little bit extra stuff) this single change shrank the app.wasm file from 13MB to 5MB. That can make a pretty big difference on resource constrained devices for that first impression page load.

    Original main.go

    package main
    
    import (
    	"context"
    	"github.com/maxence-charriere/go-app/v9/pkg/app"
    	"log"
    	"net/http"
    	"time"
    )
    
    type Frame struct {
    	app.Compo
    }
    
    func (f *Frame) Render() app.UI {
    	return app.Div().Class("frame").Body(
    		app.H1().Text("Hello World!"),
    	)
    }
    
    func main() {
    	app.Route("/", &components.Frame{})
    	app.RunWhenOnBrowser()
    
    	mux := http.NewServeMux()
    	mux.Handle("/", &app.Handler{
    		Name:        "Hello",
    		Description: "A Hello World! example",
    		Styles: []string{
    			"/web/main.css",
    		},
    	})
    
    	ctx := handleSignals()
    	srv := http.Server{
    		Addr:    ":8080",
    		Handler: mux,
    	}
    
    	done := make(chan struct{})
    	go func() {
    		<-ctx.Done()
    		timeout, cancel := context.WithTimeout(context.Background(), 10*time.Second)
    		defer cancel()
    		if err := srv.Shutdown(timeout); err != nil {
    			log.Printf("Error shutting down the server: %v\n", err)
    		}
    		close(done)
    	}()
    
    	log.Println("Starting todo app server")
    	if err := srv.ListenAndServe(); err != nil {
    		if err != http.ErrServerClosed {
    			log.Fatalf("Error starting server: %v\n", err)
    		}
    	}
    	<-done
    	log.Println("Server shut down")
    }
    

    Modified main.go to call the server function

    Note the reduction in imports. This means that there's a lot less needless stuff going into the app.wasm bundle.

    package main
    
    import (
    	"github.com/maxence-charriere/go-app/v9/pkg/app"
    )
    
    type Frame struct {
    	app.Compo
    }
    
    func (f *Frame) Render() app.UI {
    	return app.Div().Class("frame").Body(
    		app.H1().Text("Hello World!"),
    	)
    }
    
    func main() {
    	app.Route("/", &components.Frame{})
    	app.RunWhenOnBrowser()
    
    	server()
    }
    

    server_js.go

    Just an empty function. :)

    package main
    
    func server() {}
    

    server.go

    Moved all the server boilerplate to here with the !js build tag to make sure it isn't going into the wasm.

    //go:build !js
    
    package main
    
    import (
    	"context"
    	"github.com/maxence-charriere/go-app/v9/pkg/app"
    	"log"
    	"net/http"
    	"time"
    )
    
    func server() {
    	mux := http.NewServeMux()
    	mux.Handle("/", &app.Handler{
    		Name:        "Hello",
    		Description: "A Hello World! example",
    		Styles: []string{
    			"/web/main.css",
    		},
    	})
    
    	ctx := handleSignals()
    	srv := http.Server{
    		Addr:    ":8080",
    		Handler: mux,
    	}
    
    	done := make(chan struct{})
    	go func() {
    		<-ctx.Done()
    		timeout, cancel := context.WithTimeout(context.Background(), 10*time.Second)
    		defer cancel()
    		if err := srv.Shutdown(timeout); err != nil {
    			log.Printf("Error shutting down the server: %v\n", err)
    		}
    		close(done)
    	}()
    
    	log.Println("Starting todo app server")
    	if err := srv.ListenAndServe(); err != nil {
    		if err != http.ErrServerClosed {
    			log.Fatalf("Error starting server: %v\n", err)
    		}
    	}
    	<-done
    	log.Println("Server shut down")
    }
    
    opened by drognisep 4
Releases(v9.6.4)
  • v9.6.4(Aug 29, 2022)

    Summary

    • Loader label is not forced to be lowercase anymore
    • Proxy resources are now fetched from HTTP when TLS is set in a http.Handler. Thanks @oderwat
    Source code(tar.gz)
    Source code(zip)
  • v9.6.3(Aug 22, 2022)

  • v9.6.2(Aug 22, 2022)

  • v9.6.1(Aug 22, 2022)

    Summary

    • Go requirement bumped to Go v1.18
    • Custom elements (Elem and ElemSelfClosing)
    • Prevent component update
    • Engine optimization that ensure a component update is done once per frame cycle
    • Wasm progress
    • Customizable app-worker.js template
    • Documentation tweaks

    Thanks

    • @oderwat
    Source code(tar.gz)
    Source code(zip)
  • v9.5.1(May 10, 2022)

  • v9.5.0(May 10, 2022)

  • v9.4.1(Mar 26, 2022)

  • v9.3.0(Dec 27, 2021)

  • v9.2.1(Nov 8, 2021)

  • v9.2.0(Nov 3, 2021)

  • v9.1.2(Oct 25, 2021)

  • v9.1.1(Oct 18, 2021)

  • v9.0.0(Sep 22, 2021)

  • v8.0.4(Jun 20, 2021)

  • v8.0.3(Jun 20, 2021)

  • v8.0.2(Apr 20, 2021)

  • v8.0.1(Mar 30, 2021)

  • v8.0.0(Mar 25, 2021)

  • v7.3.0(Feb 19, 2021)

    A scope can be added to event handler in order to trigger event handler updates.

    In a scenario where we want to remove a element from a list, a solution is to create an EventHandler which got the element id set outside. The event handler returned will always have the same addr, which prevent the package to define that an update should be done on the given element.

    To solve this, a scope has been added to the methods that set EventHandler. Here is the an example:

    type issue499Data struct {
    	ID    int
    	Value string
    }
    
    type issue499 struct {
    	app.Compo
    
    	data []issue499Data
    }
    
    func newIssue499Data() *issue499 {
    	return &issue499{}
    }
    
    func (c *issue499) OnMount(app.Context) {
    	c.data = []issue499Data{
    		{11, "one"},
    		{22, "two"},
    		{33, "three"},
    		{44, "four"},
    		{55, "five"},
    		{66, "six"},
    		{77, "sever"},
    		{88, "eight"},
    		{99, "nine"},
    	}
    	c.Update()
    }
    
    func (c *issue499) Render() app.UI {
    	return app.Div().Body(
    		app.H1().Text("Issue 499"),
    		app.Div().
    			Body(
    				app.Range(c.data).Slice(func(i int) app.UI {
    					d := c.data[i]
    					return app.Button().
    						ID(fmt.Sprintf("elem-%v", d.ID)).
    						OnClick(c.newListener(d.ID), d.ID). // HERE the element ID is added in order to trigger the handler update since the func pointer returned by newListener is always the same.
    						Text(d.Value)
    				}),
    			),
    	)
    }
    
    func (c *issue499) newListener(id int) app.EventHandler {
    	return func(app.Context, app.Event) {
    		for i, d := range c.data {
    			if id == d.ID {
    				c.data = append(c.data[:i], c.data[i+1:]...)
    				c.Update()
    				return
    			}
    		}
    	}
    }
    
    Source code(tar.gz)
    Source code(zip)
  • v7.2.0(Jan 8, 2021)

    Hello there,

    This release brings a way to be notified that that app window size changed within components. It can be done by implementing the Resizer interface:

    type myCompo struct{
        app.Compo
    }
    
    func (c *myCompo) OnAppResize(ctx app.Context) {
        // Handle app resizing.
    }
    

    It can be quite a handful when building layout components. Shell and Flow has been refactored and now uses this mechanism.

    Source code(tar.gz)
    Source code(zip)
  • v7.1.2(Jan 5, 2021)

  • v7.1.1(Jan 5, 2021)

    Hello, Small patch today:

    • Fixed a bug that prevented _bank navigation for paths within the app host
    • Context now have a variable that reports whether the app has been updated in the background
    Source code(tar.gz)
    Source code(zip)
  • v7.1.0(Jan 4, 2021)

    Hello there,

    This version introduces the Updater interface. It allows a component to be notified that the app has been updated.

    This will allow notifying your users that the app has been updated and modifications are available by reloading the page.

    Check the Lifecycle article in the doc to see how to use it.

    Source code(tar.gz)
    Source code(zip)
  • v7.0.7(Dec 29, 2020)

  • v7.0.6(Nov 26, 2020)

    Hello there. Big update today since this release introduces a dogfooded documentation for the package:

    go-app documentation

    Next to this here are the fixes:

    • Iframe attributes have been added
    • Fixed crash when using Javascript function New and Call with interface{}
    • manifest.json has been renamed manifest.webmanifest in order to follow Google PWA guidelines

    This release also introduces some experimental widgets that are layout related:

    Those widgets are used in the documentation introduced above. Since they are experimental, their API may change.

    Source code(tar.gz)
    Source code(zip)
  • v7.0.5(Aug 25, 2020)

    Hello,

    This version provides the following changes:

    • Fixed a bug where boolean attributes were not updated
    • Min() and Max() HTML element functions now take an interface{} argument rather than string
    Source code(tar.gz)
    Source code(zip)
  • v7.0.4(Aug 12, 2020)

    Hello,

    Here is a small release that brings the following:

    • The handler now proxy an ads.txt file that is located at the root of the static files directory. This allows complying with AdSense requirements.
    • app.Input().Step(v int) has been changed to app.Input().Step(v float64) since step can be a decimal value.
    Source code(tar.gz)
    Source code(zip)
  • v7.0.3(Jul 11, 2020)

    Hello,

    Here is v7.0.3 which introduces the following changes:

    • Fixed bug that did not remove event handlers when components were dismounted
    • Refactored how scripts are loaded in the Handler by using defer attribute
    • Added Iframe missing attributes
    • Generated GitHub pages are now installable with Chrome
    # How to update:
    go get -u github.com/maxence-charriere/go-app/v7
    
    Source code(tar.gz)
    Source code(zip)
  • v7.0.2(Jun 28, 2020)

    Hello there, I'm thrilled to release version 7 of go-app.

    This version is focused on internal improvements that improve code quality and maintainability. Unfortunately, those improvements bring a few small changes in the API, which is why there is a version bump.

    What is new?

    • Context that is bound to a UI element lifecycle. The context can be used with functions that accept context.Context. Contexts are canceled when the UI element they are bound with is dismounted. It is passed in Mounter and Navigator interfaces, and event handlers.

    • TestMatch: testing api to unit test specific UI element:

      tree := app.Div().Body(
          app.H2().Body(
              app.Text("foo"),
          ),
          app.P().Body(
              app.Text("bar"),
          ),
      )
      
      // Testing root:
      err := app.TestMatch(tree, app.TestUIDescriptor{
          Path:     TestPath(),
          Expected: app.Div(),
      })
      // OK => err == nil
      
      // Testing h2:
      err := app.TestMatch(tree, app.TestUIDescriptor{
          Path:     TestPath(0),
          Expected: app.H3(),
      })
      // KO => err != nil because we ask h2 to match with h3
      
      // Testing text from p:
      err = app.TestMatch(tree, app.TestUIDescriptor{
          Path:     TestPath(1, 0),
          Expected: app.Text("bar"),
      })
      // OK => err == nil
      
    • Support for aria HTML element property: Fix #419

      app.Div().
          Aria("foo", "bar").
          Text("foobar")
      
    • A default logger can be set

    • go-app PWA can now be deployed a GitHub Page with the help of GenerateStaticWebsite function:

      package main
      
      import (
      	  "fmt"
      
      	  "github.com/maxence-charriere/go-app/v7/pkg/app"
      )
      
      func main() {
      	  err := app.GenerateStaticWebsite("DST_DIR", &app.Handler{
      		  Name:      "Github Pages Hello",
      		  Title:     "Github Pages Hello",
      		  Resources: app.GitHubPages("goapp-github-pages"),
      	  })
      
      	  if err != nil {
      		  fmt.Println(err)
      		  return
      	  }
      
      	  fmt.Println("static website generated")
      }
      

      It generates files that can directly be dropped into a GitHub repository to serve the PWA. See live example: https://maxence-charriere.github.io/goapp-github-pages/

    • Support for robots.txt: A robots file is now served by the Handler when /web/robots.txt exists

    • Internal code refactored to be more maintainable

    • Serving static resources can now be customized by implementing the ResourceProvider interface

    How to migrate from v6 to v7

    go-app v7 mainly introduced internal improvements. Despite trying to keep the API the same as v6, those changes resulted in API minor modifications that break compatibility.

    Here is a guide on how to adapt v6 code to make it work with v7.

    Imports

    Go import instructions using v6:

    import (
        "github.com/maxence-charriere/go-app/v6/pkg/app"
    )
    

    must be changed to v7:

    import (
        "github.com/maxence-charriere/go-app/v7/pkg/app"
    )
    
    

    http.Handler

    • RootDir field has been removed. Handler now uses the Resources field to define where app resources and static resources are located. This has a default value that is retro compatible with local static resources. If static resources are located on a remote bucket, use the following:

      app.Handler{
          Resources: app.RemoteBucket("BUCKET_URL"),
      }
      
    • UseMinimalDefaultStyles field has been removed. go-app now use CSS styles that only apply to the loading screen and context menus. The former default styles have been removed since they could conflict with some CSS frameworks.

    Component interfaces

    Some interfaces to deals with the lifecycle of components have been modified to take a context as the first argument. Component with methods that satisfies the following interfaces must be updated:

    • Mounter: OnMount() become OnMount(ctx app.Context)
    • Navigator: OnNav(u *url.URL) become OnNav(ctx app.Context u *url.URL)

    Event handlers

    EventHandler function signature has been also modified to take a context as the first argument:

    • func(src app.Value, e app.Event) become func(ctx app.Context, e app.Event)

    • Source is now accessed from the context:

      // Event handler that retrieve input value when onchange is fired:
      func (c *myCompo) OnChange(ctx app.Context, e app.Event) {
          v := ctx.JSSrc().Get("value")
      }
      
    Source code(tar.gz)
    Source code(zip)
  • v6.6.2(Jun 23, 2020)

Owner
Maxence Charriere
Maxence Charriere
🚀‏‏‎ ‎‏‏‎‏‏‎‎‎‎‎‎Copper is a Go toolkit complete with everything you need to build web apps.

Copper Copper is a Go toolkit complete with everything you need to build web apps. It focuses on developer productivity and makes building web apps in

Copper 867 Sep 13, 2022
Flamingo Framework and Core Library. Flamingo is a go based framework for pluggable web projects. It is used to build scalable and maintainable (web)applications.

Flamingo Framework Flamingo is a web framework based on Go. It is designed to build pluggable and maintainable web projects. It is production ready, f

Flamingo 317 Sep 27, 2022
beego is an open-source, high-performance web framework for the Go programming language.

Beego Beego is used for rapid development of enterprise application in Go, including RESTful APIs, web apps and backend services. It is inspired by To

astaxie 532 Sep 25, 2022
beego is an open-source, high-performance web framework for the Go programming language.

Beego Beego is used for rapid development of enterprise application in Go, including RESTful APIs, web apps and backend services. It is inspired by To

beego Framework 28.9k Sep 27, 2022
letgo is an open-source, high-performance web framework for the Go programming language.

high-performance Lightweight web framework for the Go programming language. golang web framework,高可用golang web框架,go语言 web框架 ,go web

wjp 350 Sep 23, 2022
henrylee2cn 1.6k Sep 16, 2022
A web app built using Go Buffalo web framework

Welcome to Buffalo Thank you for choosing Buffalo for your web development needs. Database Setup It looks like you chose to set up your application us

Mike Okoth 0 Feb 7, 2022
Web framework for creating apps using Go in Google AppEngine

Welcome to app.go v3.0 app.go is a simple web framework for use in Google AppEngine. Just copy the app folder to your working folder and import it fro

George Nava 46 Mar 21, 2021
Rest-and-go-master - A basic online store API written to learn Go Programming Language

rest-and-go(Not maintained actively) A basic online store API written to learn G

urobin84 0 Jan 12, 2022
Short basic introduction to Go programming language.

Go, Go! Short basic introduction to Go v1.17.6 programming language Go Logo is Copyright 2018 The Go Authors. All rights reserved. About This work was

Gábor 0 May 30, 2022
Vektor - Build production-grade web services quickly

Vektor enables development of modern web services in Go. Vektor is designed to simplify the development of web APIs by eliminating boilerplate, using secure defaults, providing plug-in points, and offering common pieces needed for web apps. Vektor is fairly opinionated, but aims to provide flexibility in the right places.

Suborbital 86 Sep 14, 2022
based on go lang build WEB development framework for go lang beginners .

based on go lang build WEB development framework for go lang beginners .

zhenfan.yu 1 Oct 31, 2021
Ozair Farahi 9 Sep 20, 2022
An app skeleton for very simple golang web applications

Golang App Skeleton This is a skeleton for a golang web application optimized for simplicity and rapid development. Prerequisites Go 1.15 or greater O

Ad Hoc 76 Sep 15, 2022
A framework for apps written entirely in YAML, powered by ytt.

yapp A framework for apps written entirely in YAML, powered by ytt. Highly experimental! Do not use! # start the server... go run . -f examples/hello-

Reid Mitchell 4 May 6, 2022
A high productivity, full-stack web framework for the Go language.

Revel Framework A high productivity, full-stack web framework for the Go language. Current Version: 1.0.0 (2020-07-11) Supports go.mod package managem

Revel Framework 12.7k Sep 30, 2022
Goal is a toolkit for high productivity web development in Go language in the spirit of Revel Framework that is built around the concept of code generation.

Goal Goal is a set of tools for high productivity web development in Go language. Goal, being mostly inspired by Revel Framework and its discussions,

null 88 Sep 27, 2021
⚡ Rux is an simple and fast web framework. support middleware, compatible http.Handler interface. 简单且快速的 Go web 框架,支持中间件,兼容 http.Handler 接口

Rux Simple and fast web framework for build golang HTTP applications. NOTICE: v1.3.x is not fully compatible with v1.2.x version Fast route match, sup

Gookit 82 Sep 27, 2022
Roche is a Code Generator and Web Framework, makes web development super concise with Go, CleanArch

It is still under development, so please do not use it. We plan to release v.1.0.0 in the summer. roche is a web framework optimized for microservice

Riita 14 Sep 19, 2022