วีดีโอ

@@pythonantole9892 that is so great to hear, thanks. Be sure to ask if you have any questions as you progress.

@@Fyneio Thanks. Will do.

@@AgustinCouding that’s very kind to say. I hope you continue to enjoy the project as we keep pushing forward

Thank you very much! Hopefully you enjoyed it too

Our pleasure! It’s thrilling to see all the great apps people are building!

Thanks a lot!

It is a brave new world @@jabthejewboy :)

@@RobertFletcherOBE we use a combination of mutexes and event queues to ensure those methods are safe to call. Older toolkits do indeed require you to run on the main thread, but that is just them pushing a complex problem to the developer 😉.

It just means there was no FyneApp.toml file. If you don’t want one you can ignore it, if you have one and it’s not working then open a bug. docs.fyne.io/started/metadata

The system tray library will let you do that. However the Fyne systray menu abstraction doesn’t because that’s not the expected behaviour on some systems

Can you be more specific about what you would like to see? If it's complete apps then all the items at apps.fyne.io are open source too!

@@Fyneio I've recently started learning Fyne, but I'm finding it challenging to customize the theme due to the constantly changing API. Specifically, I'm struggling to create three different colored buttons correctly. Perhaps a to-do list or chat application would be a suitable demonstration of Fyne's capabilities. Moreover, I think SQLite would be sufficient for most use cases, but if we were to use Supabase as the backend, we could achieve more in a real-world project

@@j8ge the API has not had a breaking change since v2.0 around 3 years ago. Perhaps you mean the button colour changing? Look at “Button.Importance” to use the intent based API for button types. If you want to return to the older transparent buttons with background underlay you can set the theme button colour to transparent with a custom theme. For app demos have you looked at apps.fyne.io?

It is a Scottish word / place name :)

Thanks so much, great to hear you are enjoying it :)

Visual studio does nothing fancy, the code would work on the command line. `makeUI` is defined in the main.go file, in the same folder - it will be found automatically. Perhaps you are asking it to “build only this test file”? Just running the tests using the standard tools, or building/testing the package as a whole will work.

@@Fyneio Thank you. Now I know about multiple files compilation. When I build it all by "go build main.go main_test.go" or "go build main_test.go main.go" command in cmd and run the compiled .exe file, the application runs and test results are not shown. This may be beyond my understanding for now.

@@MFT9170 to run tests use “go test” not “go build”

Yes, you can find out more at fysion.app

The “fyne package” command will apply all these optimisations. It is designed to make it easy to always get the right output for your OS. Just using the go build won’t bundle an app icon or metadata. developer.fyne.io/started/packaging

@@Fyneio After go build -ldflags "-s -w -H windowsgui" hello.go I get only 16 MB hello.exe But after fyne package -os windows I get 34 MB exe. My Icon.png has only 1 KB.

Windows can cache icons so the may not actually be a problem - it should resolve later (maybe next reboot?)

Windows has included a suitable version of OpenGL in graphics drivers since 2008… maybe your install isn’t fully working?

fyne executable folder should be in your PATH

Yup, more info for fixing this at developer.fyne.io/faq/troubleshoot

Thanks so much 😊

No plans. Hot reload is a different direction to the unit testing and validating components that Go encourages. Of course there are different approaches such as having development tooling that supports building graphically - consider checking out fysion.app (a proof of concept was demoed in FyneConf 2023 video 4: FyshOS).

You can set the border colour in a custom theme.

Love the enthusiasm, thanks 😊

It’s great to hear you found it so useful 😀

You can help spread the word 😀

@@Fyneio ok

We agree :) thanks!

Thanks to everyone who contributes (including everyone who presented, watched or attended) the events and made libraries or apps that were presented or enabled the content to be put together!

Thank you for joining the live stream!

Thank you for joining the live stream :)

Not yet. It’s on the roadmap though

The table cells can contain whatever you want. Put an Entry widget in there and you will get an editable table…

This usually means your path doesn’t include the go binaries directory developer.fyne.io/faq/troubleshoot

That’s a big topic and probably outside the scope of a little demo like this. There is a “login form” in fyne_demo that covers the front-end portion though, and the rest is likely a more general question. Why not join one of our chat rooms? fyne.io/support/

The live feed did drop sound at that point, however the edited video we released later is fixed th-cam.com/video/nQztRVhxSiE/w-d-xo.html

you need to run 'go mod tidy' THEN 'go run .' if it fails for you with newer go version than shown here

@@craigdanielmaceacher good catch. “Go mod tidy” fixes lots of issues on a modern go install. I swear it was easier to get started before modules!

Yes, good point. Fyne v2.0.0 was released 2 years ago (Jan 2021) and we don’t support 1.4 or earlier any more.

@@Fyneio Thank you for reply. It would be better if there was 'depricated' word on GO DEV.

You could try one of our support channels fyne.io/support/

We could do more setup videos indeed. For now check the docs at developer.fyne.io/started/mobile. Basically “fyne package -os android” and “fyne install -os android”

I think you can do this with a menu item that is disabled…

Thanks! Based on the example in this video, I've use something like this and it works. Is there away to update the text to reflect a dynamic state like the clock widget example? I've tried different ideas and none seemed to work, even the Menu.Refresh() didn't help. func MyNewMenuItem(label string) *fyne.MenuItem { return &fyne.MenuItem{Label: label, Disabled: true} }

@@sorrowseal yup Menu.Refresh is your friend. Perhaps you did not set the updated label into the menu item correctly before refreshing. I’d recommend one of the support channels (Slack, Discord etc) linked from our website to get more assistance