Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building Cross-Platform GUI Applications with Fyne

You're reading from   Building Cross-Platform GUI Applications with Fyne Create beautiful, platform-agnostic graphical applications using Fyne and the Go programming language

Arrow left icon
Product type Paperback
Published in Jan 2021
Publisher Packt
ISBN-13 9781800563162
Length 318 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Andrew Williams Andrew Williams
Author Profile Icon Andrew Williams
Andrew Williams
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section 1: Why Fyne? The Reason for Being and a Vision of the Future
2. Chapter 1: A Brief History of GUI Toolkits and Cross-Platform Development FREE CHAPTER 3. Chapter 2: The Future According to Fyne 4. Section 2: Components of a Fyne App
5. Chapter 3: Window, Canvas, and Drawing 6. Chapter 4: Layout and File Handling 7. Chapter 5: Widget Library and Themes 8. Chapter 6: Data Binding and Storage 9. Chapter 7: Building Custom Widgets and Themes 10. Section 3: Packaging and Distribution
11. Chapter 8: Project Structure and Best Practices 12. Chapter 9: Bundling Resources and Preparing for Release 13. Chapter 10: Distribution – App Stores and Beyond 14. Other Books You May Enjoy Appendix A: Developer Tool Installation 1. Appendix B: Installing Mobile Build Tools 2. Appendix C: Cross-Compiling

Organizing your project

One of the design principles of the Go language is that you can start simple and build more structure into your project as it grows. Following this mantra, you can simply start a GUI project with a single main.go file inside a directory that's been created for the project. This will initially contain your entire application, starting from its main() function.

Starting simple

Once your user interface has grown from the very basics, it is a good idea to split it into a new file, perhaps named ui.go. Splitting the code in this way makes it clearer which code is simply booting an application (the main() function and helpers) compared to what is actually building the user interface.

By this time, you should be thinking about adding unit tests (if you have not already added them!). These tests will live in a file, alongside your code, that ends in _test.go – for example, ui_test.go. It is good practice to test all of your code, and for each new...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime