fix!: set buttons and textfields to be 35px high

[Feichtmeier]

This is setting the height for buttons and togglebuttons to 35 The matching icon size seems to be 16 🤷 I adapted the example (the control view really needs some love to reduce code copy pasting at some point)

Fixes #369

[Feichtmeier]

needs a bit more work for textfield adaption

[jpnurmi]

Hmm, was it so that there was no clean way to control the size but you could only tweak the padding to make it coincidentally match by default? I hope this won't ruin the whole plan... :( On a related note, looks like text fields were 42px back when we were still on M2.

[Feichtmeier]

you can control both the size and the content padding for the child inside

[Feichtmeier]

Also the example s*cks because the rows try to force a specific height

I'll rework the example a bit Then fix the textfield height

Do you have a specific time pressure on this issue? I don't know if I can finish it today

[jpnurmi]

There's no time pressure. I just noticed some mismatching button heights (36px vs. 40px) in the installer and started wondering what was going on and where the 36px even came from...

[Feichtmeier]

There's no time pressure. I just noticed some mismatching button heights (36px vs. 40px) in the installer and started wondering what was going on and where the 36px even came from...

ok :) Also to be sure I better do this on buntu when I am home 👴

[Feichtmeier]

Okay slowly getting there, though it is a bit more complicated because many things affect the text field @jpnurmi

Things that need changing for this:

• text theme body large from 16 to 14
• input decoration theme

Things that can still totally ruin the textfields:

• bouncing label moves the hint 2 px down -.-
• prefix icons even with reduced icon size in the whole theme and then increased back for headerbar and navigation bars

I must admit this already looks much better. But can we live with the hint bouncing and the prefix icon alignment? given that the prefix icon can be always adapted in for example yaru widgets ?

[Feichtmeier]

[Feichtmeier]

@jpnurmi okay this is really weird

I found most of the things to be controllable inside the textfield, except the actual editable text ... It can be controlled later when you instantiate a TextField though easily with fontSize But there is no property in InputDecorationTheme that lets you control the actual fontSize of the text you can edit :facepalm:

What we could do is to keep those changes here because they overall look better with buttons and textfields being smaller but then create a YaruTextField or something like this in yaur widgets forwarding every single property of textfield but then changing the font size to 14 :S

what do you suggest in general and what should be the scope of this PR?

[jpnurmi]

It's painful to wrap something like TextField that has tons of properties but I guess that's the only way to go until the font will be themable. :(

• https://github.com/flutter/flutter/issues/118267

[Feichtmeier]

Alternative would be to expose a kYaruTextFieldFontSize = 14.0 in yaru.dart and just remember us every time we use a text field to use this constant?

or good ol inheritance?

import 'package:flutter/material.dart';

class YaruTextField extends TextField {
  const YaruTextField({super.key});

  @override
  StrutStyle? get strutStyle => ...;

  @override
  TextStyle? get style {
    return const TextStyle(fontSize: 14);
  }
}

[Feichtmeier]

I tested this a little more and maybe we could come back to your old idea of using the VisualDensity API ? @jpnurmi Because these sizes look super tiny when used on the web now, especially if on a mobile device

[jpnurmi]

Or just go with the flow and accept 40px buttons :sob:

[Feichtmeier]

Or just go with the flow and accept 40px buttons :sob:

Maybe we can have both. Even the current button height is too low for the weird mobile aspect ratio. Just open yaru.dart GitHub website on mobile.

[Feichtmeier]

playing around with a vanilla material3 theme and visual density. this visual density api is more than incomplete. I would rather call it dysfunctional and confusing because basically only buttons change. thinking about this a lot lately and also thinking about that flutter is still cross platform and we should have a way to have comfortable sizes for mobile apps with our colors. I could very well imagine someone wanting to create a mobile app with yaru.dart. eventually we should move all size manipulations in yaru.dart to yaru_widgets and provide wrapper for buttons and textfields. then eventually we could have some kind of mapping for i.e. YaruIconButton -> isAndroid ? IconButton : YaruCompactIconButton or something

opinions @jpnurmi @Jupi007 ?

edit: also the font and icon sizes are often way too large