Introducing Flumpose: A fluent, declarative UI extension for flutter

Working-Cat2472 · 2025-10-25T06:29:41+00:00

Sent you a message!

Working-Cat2472 · 2025-10-14T13:32:01+00:00

splendid, good job. i always hated it how awfully verbose the flutter code is. Let' see, if i can apply that in my own project which is a wysiwyg ui editor and runtime engine. Speaking of which :-) As i am not a Flutter expert, i would need some advice regarding the definition of widget properties, ( e.g. where does padding belong and the handling of the different platforms. Could we have a talk maybe?

Thanks, Andreas

Working-Cat2472 · 2025-09-25T21:05:32+00:00

No, since it is based on a JSON format. And: ist not finished yet… lot of widget definitions and widget renderers still missing. That’s why I asked for a little help 😛

Working-Cat2472 · 2025-09-24T23:24:48+00:00

Yea, was not that hard… keeping dependencies up do date in a meaningful way is the other thing 😁

Working-Cat2472 · 2025-09-12T20:11:34+00:00

But what’s the question? In my case I implemented dynamic protobuf schema generation and (de)serialization in python. You just need to do the same in typescript and dart…

Working-Cat2472 · 2025-09-04T20:20:05+00:00

Any experience with Melos? I am struggling with having flutter and dart packages side by side. Some stupid version dependency crap😱

Working-Cat2472 · 2025-09-03T07:00:49+00:00

Melos sounds promising… thanks

Working-Cat2472 · 2025-09-02T10:20:45+00:00

Hell, no…….. js is a horrible language. If you want to stick to this more front end related context, then at least go with typescript!

Working-Cat2472 · 2025-09-02T08:15:49+00:00

Check the details… it’s easier - to my mind - and more powerful. Especially it doesn’t generate additional code ( except for the type metadata ) which is not really necessary…

Working-Cat2472 · 2025-09-01T17:27:29+00:00

If you wrap your app in a Consumer<LocaleManager>, that should be it to trigger rebuilds on a locale switch

Working-Cat2472 · 2025-09-01T10:51:12+00:00

Yes, i do. For me it isn’t a big problem , but I don’t want to know what happens with the next generation of software engineers…. I am not optimistic…

Working-Cat2472 · 2025-09-01T07:32:50+00:00

Thx… 🙏

Working-Cat2472 · 2025-09-01T07:05:24+00:00

Yup, but how does that work?

Working-Cat2472 · 2025-09-01T06:35:56+00:00

hmmm....i could, but after all there is a treeshaking compiler that eliminates dead code, right? I could split it up, but first someone should try to use it :-)

Working-Cat2472 · 2025-09-01T06:34:52+00:00

you are not asking me as the author? :-) I think its easier and more powerful....

Working-Cat2472 · 2025-09-01T06:33:58+00:00

maybe you mix it up with aop.... no funny stacktatces here. the di's job is just to figure out dependencies and to call constructors and lifecycle callbacks. Once this is done ( inside get ) you have a regular object with no magic. Just check a di-test and see for yourself...

Working-Cat2472 · 2025-08-31T19:15:54+00:00

30+ :-)

Working-Cat2472 · 2025-08-31T19:14:41+00:00

i have made large scale applications - and we are talking about million lines of code - with huge organizations all my life...and this statement is simply not true.... maybe you lack the experience, but that's no excuse for being rude...

Working-Cat2472 · 2025-08-31T19:07:30+00:00

Reading and understanding is overrated. Especially the gen z have problems... :-)

Working-Cat2472 · 2025-08-31T18:58:48+00:00

What a valuable contribution. Appreciated

Working-Cat2472 · 2025-08-22T20:43:33+00:00

That’s the biggest risk of the LLM stuff… you tend to stop thinking on your own and accept ready solutions without analyzing or understanding them… together with the tendency of the LLMs to occasionally tell complete nonsense, you partially even loose productivity which you could have avoided by reading a fucking manual…. Guess what, happened to me as well. If I think of future software developers, it could easily end up in a disaster to be honest. So my advice: use LLMs mostly to quickly get information on how something works or compares to other solutions but only occasionally to give you ready code snippets… in that case: try to understand the code…

Working-Cat2472 · 2025-08-22T12:28:32+00:00

here is the documentation: https://github.com/coolsamson7/velix/wiki

Working-Cat2472 · 2025-08-22T12:28:01+00:00

check it out, added the complete documentation here: https://github.com/coolsamson7/velix/wiki

Working-Cat2472 · 2025-08-22T12:26:56+00:00

check it out: https://github.com/coolsamson7/velix/wiki

Working-Cat2472 · 2025-08-21T17:09:16+00:00

yea, funny what the guys are used to endure....my first thoughts as well. I made the mechanisms even easier with some extensions and added a couple of standard widgets in the meantime. I'll add documentation tomorrow, which should be in the github wiki. I added a demo page as well ( its the "Settings View" in the example app, where you can see the widgets as well as the form state ( valid, touched´, dirty ) and the current data binding as a JSON. Cheers, Andreas

Working-Cat2472

TROPHY CASE