Pablo Fuentes

@okocsis Sounds great, thanks for sharing it :), I will take a look. Are you planning to merge your work (when it is finished) in this repository or just keeping...

> The current behaviour is technically more in line with what the Go developers suggestions to have a global error variable and then just returning the same value Yes, indeed...

@andydotxyz Isn't it possible to just add a new field to `canvas.Rectangle` called `BorderRadius`? Then the canvas.Rectangle could be any kind of rectangle rounded or not. `BorderRadius` could be private...

@AlbinoGeek You are right. The app in the video I had to develop it quickly, so I just wanted to do something functional. I worked over the current release of...

@andydotxyz So what should be next step? Will widget.Entry be redesigned to satisfy material design specs?

@andydotxyz hmm and that means editing widget.Entry or creating another one called TextField and deprecating widget.Entry? Then TextFormField will use a TextField internally to render an input with the label....

@AlbinoGeek I think `widget.Form` needs to be changed anyways to be more flexible, and as it is going to be a new major version (2.0), I think is a good...

> > @andydotxyz hmm and that means editing widget.Entry or creating another one called TextField and deprecating widget.Entry? > > We should, if we can, continue with the current Entry...

> so reserving space fits better with how we have designed to now. Sorry, I don't understand very much what do you mean by "reserving space" 😅. Does it mean...

@AlbinoGeek maybe widget.Entry could have a min height of 37 + 16 (when using helper text or error text), to avoid changing dramatically the size of this widget? Min width...