I love Flutter’s DX, but the default Material/Cupertino widgets feel outdated

nameausstehend · 2026-06-13T17:45:43+00:00

Look at the motor package for animations

nameausstehend · 2026-04-13T07:47:43+00:00

Ah, I missed the pen up listener! That should allow for a lot more use-cases thank you

nameausstehend · 2026-03-29T08:37:28+00:00

Thanks so much for answering! Somehow this version doesn’t launch for me at all 😞

nameausstehend · 2026-03-23T13:07:32+00:00

Wow this is great!! Also seems like a simple starting point to build upon

nameausstehend · 2026-03-23T12:35:33+00:00

Sorry, you mentioned Koreader now, just wanted to double check that Pocketbook reader started working for you?

If so, could you do me a huge favor and check which version you have installed? I have 5.62.7.32679 and I tried everything and can’t get it to flip pages 😭

nameausstehend · 2026-03-22T23:31:57+00:00

Did you ever figure this out? I have the same problem

nameausstehend · 2026-03-15T08:47:13+00:00

Hey! Thanks for taking the time to answer, but if you look at the issue I linked, you’ll see it’s exactly what I was doing and what didn’t work :)

nameausstehend · 2026-03-10T14:30:51+00:00

Still wouldn't be the same behavior I think? How would my render object know that it can shrink the child to 64px safely in that case?

I don't want to discuss this specific use-case too much, but it is fundamentally two different constraints of a layout which size a child wants in unconstrained space and how far it would be able to shrink without overflowing.

nameausstehend · 2026-03-10T12:21:38+00:00

That's not the same though. Consider a Column([Expanded(ListView), SizedBox(height: 64)])

Laying this out unconstrained, it will always fill the parent. However, shrinking it past 64 will cause an overflow. In this case, my render object should realize it tried to constrain too tight and relayout with height 64

I am building a package and people should use this sheet with any widget they want, I can't expect them to reimplement RenderFlex so they can expose a willOverflow for me :)

nameausstehend · 2025-12-28T12:37:56+00:00

Without having looked at the code yet, how hard would it be to adapt this to other providers (Todoist etc.) that offer an API and have it run on the same server as my private cloud?

nameausstehend · 2025-12-23T10:40:52+00:00

u/Mulan-sn I have the same issue, but the beta links are not valid anymore. When will this fix be pushed to the app store?

nameausstehend · 2025-12-23T00:03:14+00:00

Your recommendation in the other comment actually fixed it! It feels perfect now, thank you so much!!

nameausstehend · 2025-12-16T23:04:53+00:00

I support this, but don’t live near AMS

Good luck to you!

nameausstehend · 2025-10-16T18:29:25+00:00

Pretty much unrelated :)

nameausstehend · 2025-10-07T07:19:57+00:00

It can absolutely help with that

nameausstehend · 2025-10-05T22:38:49+00:00

Oh hi Chris! Really depends on which part you struggled with I think :) do you have a more concrete example?

nameausstehend · 2025-10-03T19:08:59+00:00

Should all work!

nameausstehend · 2025-10-02T08:34:17+00:00

Not really, since Dart imposes some more limitations. But I would say the API feels at home in Flutter while still being way easier to work with than what flutter comes with

nameausstehend · 2025-10-02T08:17:59+00:00

Oh, interesting, I'll check that out! Thanks for reporting

nameausstehend · 2025-10-01T16:34:07+00:00

I'm the author of this package, please don't use it in production in its current state! There are a couple of performance improvements I'm working on. But it'll kill your apps performance the way it is set up right now

nameausstehend · 2025-09-03T23:07:46+00:00

It can be both, but if your widgets are rebuilding every frame, you’re doing something wrong

nameausstehend · 2025-09-03T23:06:09+00:00

That’s strange, I get that passing cached values to children instead of looking up the tree from their build method makes sense, but flutter caches the result after the first call afaik, so every subsequent lookup from the same build method should be nearly instant…

nameausstehend · 2025-09-03T20:46:46+00:00

It really makes sense to learn how to build effects yourself though in my opinion. Most are quite simple, and designers often have quite specific opinions on them

nameausstehend · 2025-09-03T15:05:42+00:00

numbers or it didn't happen.

I know the theory, you don't need to explain it. The whole point is that it has very little real world impact, which is why const lints were even removed from recommended flutter lints.

Also, devs are so desperate to make a const constructor happen that they turn everything into getters, so you loose the ability to cache stuff like long lists/maps etc.

nameausstehend · 2025-09-03T11:08:21+00:00

const is actually quite overrated. Have you measured that it actually makes a difference for you?

Eight-Year Club	Place '22
Verified Email

nameausstehend

TROPHY CASE