I'm trying to understand why this project calls itself "based on Material Design"? The example screenshots in the README have nothing that looks like what's widely known as Material Design. (https://material.io/)
Layout is sort of the center of questions I have about it too.
There's a few built-in layout options: https://godoc.org/fyne.io/fyne/layout ... but not many; I think it'd be a stretch to say it's going to provide equivalents to many of the things one can very quickly and easily do in the web with a handful of divs and spans and (don't hit me) tables.
Most of the examples in https://github.com/fyne-io/examples/ don't shed further light on what complex applications might need: everything there appears to be things implemented with very simple and strict grids. Nothing looks like it proves out a feature like tables that are resizable or can automatically choose reasonable sizes based on content, which would be a huge boon for making development as rapid as web platforms can be.
The key interface for making your own layout logic appears to be https://godoc.org/fyne.io/fyne#Layout . The good news: it's definitely something you can implement without forking the core of the library. It looks a little... sparse, though.
Let's say I wanted to implement a system where each object I'm laying out can have collapsible margins, and it's the layout engine's responsibly to figure out the collective resolution of that. Is this interface enough? How would I proceed?
...
Maybe I just need more time with it to see the potential, but it's definitely something I find important to watch out for. I've been burned enough lately by investing time in systems (I'm looking at you, nuklear) just to find their layout primitives are so far off the mark that they're in "start over" territory. And I think we can also look to more ancient history like the Java Swing era to see that "layoutManager" objects that don't have _enough_ interface information to work with are pretty doomed, because they result in whole divergent non-compatible layout suites that the whole application has to opt into, which is just a nightmare for growing a community with reusable code.
Its pretty good, it is written by the author of "Hands-On GUI Application Development in Go" which covers pretty much every gui option in goland. Its the easiest to use, just use go modules and it compiles without messing around with external dependencies.
How easy is it to style these components? I've worked at a lot of IoT companies that run full-blown android just to get access to the UI libraries on android. I've been looking for something high level that can be used to build a completely customized kiosk interface on low end hardware. You shouldn't need a 4core CPU with 2GB of RAM to get reasonably clean user interfaces working.
I'd think Qt on embedded linux could do much the same with a lot less, or littlevgl if you want to go even lower. The cost is in finding good people for a reasonable wage.
You can also use PySlide or PyQT5 to write all the base in Python with Qt components. Python+QT works really well if you build good unit tests. I used it recently to build an mpv front-end:
This looks very interesting. Congrats on the mobile support!
Is there an example Android APK of an app built with Fyne? I had a few issues getting `fyne package` to work with the calculator example[1], despite following the instructions[2]. I'm really curious how it looks/works on mobile.
I suppose any native platform access (sensors, camera, etc.) is out of scope for a UI framework. Any ideas how feasible this is nowadays as a Java/Kotlin/Flutter/Swift alternative? Is there some native bridge layer for Go?
