dskinner / material Goto Github PK

Am wanting to play around, but currently cant run Material due to a func in snd changing.
i am pretty sure on this because i deleted the snd and simplex folder before go getting.

x-MacBook-Pro:bin apple$ go get dasa.cc/material
# dasa.cc/material
../src/dasa.cc/material/anim.go:59: anim.Sig.SampleUnit undefined (type snd.Discrete has no field or method SampleUnit)
../src/dasa.cc/material/anim.go:87: interp.Sig.SampleUnit undefined (type snd.Discrete has no field or method SampleUnit)

x-MacBook-Pro:bin apple$ go version
go version go1.7.4 darwin/amd64

x-MacBook-Pro:bin apple$ go env
GOARCH="amd64"
GOBIN="/Users/apple/workspace/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/apple/workspace/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/wp/ff6sz9qs6g71jnm12nj2kbyw0000gp/T/go-build161440261=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"

Hi, I'm wondering, what's the issue/cause so this project discontinued?

I know this project is discontinued, I'm working through it to try to figure out graphics in gomobile and thinking about writing a UI package based on it. From a design standpoint, was there any particular reason you decided to make the lower left corner 0,0,0, rather than the upper left? It makes it a bit confusing when translating the Y coordinate from a touch.Event

This is really nice package to use.
It's a opengl runtime in essence.

I am wondering if any thought has been given to the use cases of when a develop need to incorporate / invoke native controls such as a calendar widget etc ?

I am thinking that a bridge using gomobile could work but really guessing here. Hence why I am asking.

And I also read on the readme that this project is scoped only to the material design aspects. I am asking because I am looking at doing this work myself

I'm writing a very simple password manager in go and would like to develop an android app for it. I would like to stick to pure go. Since the app will be extremely simple, I think I may be able to use your library for it. I will basically need things like a lists of sites (that have associated usernames/passwords etc), press and hold menus for elements of those lists, master password entry, etc. It may be a good test case for the library and I could help contribute some components that would be necessary if they don't exist.

Let me know where you are in the development and how this sounds, and hopefully I can help contribute to your library.

this is due to treating the layout within window bounds as a maximization problem with (0, 0) origin at bottom left. This should produce an error instead of hanging.

Material content can act independently of the material itself, being clipped by the material's bounds. There's a lot of interesting cases for interactions with this such as resolving content layout that is masked and clipped by a floating action button that on click removes mask and animates to the encompass content's bounds.

The question then becomes, what is content .. but the layout of text and images, both of which are supported to some degree by the Material type today. So, how should this be laid out and how should the various types interact? Is a distinction of material vs content required at the type level or is this an api issue? I'm leaning towards the latter.

Cool project.
I am interested in hotspot profiling this to see if we can get its fps higher.

Any ideas ? Pprof runs on mobile ?

This code is coming along really well.
I am curious what your own thoughts about layout code is, since your so close to this.
I saw damsel for example.
Keeping all of it in golang seems smart too for easy compile time errors etc.
Qml is another approach. I use qml and the nice part is it's turtles all the way down in terms of composition and slots and signals for events and databinding.

Having said all that there is a good GUI tree layout system that is golang / gopherjs here:
https://github.com/gu-io/gu

It's not my baby but i use it and help on it.
Checkout the tree folder. It's independent of the GUI. Can target the Dom if anything else. It's super easy to use and put strongly type events and binding in it.

We have been discussing the idea of supporting shiny / gomobile for a bit as a bit of an experiment

Have a look at it. Would be cool if some synergy is there

Currently, roundness has a hard cut-off which can look jagged given the right combination of colors. The fix for this isn't immediately obvious given the current fragment shader which supports everything from rounded corners to ellipses in a single implementation.

this was previously compensated for in the transform since the difference is exact but that has since been removed and gen.go should be fixed.

material-glyphs shaders are not included in the repo so the example cannot be run.

• rewrite core methods for eta factorization (revised simplex)
• handle unrestricted variables
• factor out single variable inequalities
• provide user hints for fixing unbounded problems