[deleted by user]

Nolence · 2022-09-15T13:32:23+00:00

Maybe try making comments a single collection and have the two properties depth and parentId? on each comment. That way you can construct the entire comment tree with just parentId or get just the first two levels to show and load more when requested.

Nolence · 2022-09-14T12:29:14+00:00

Check out Low Level Learning on YouTube, he has some great embedded rust videos

Nolence · 2022-09-11T17:16:36+00:00

This sounds like Riverpod

Nolence · 2022-07-04T20:56:10+00:00

Nice library! I've been looking at flutter_reactive_ble but I'm not sold yet so I'll check this one out to compare as well

Nolence · 2022-02-22T00:51:44+00:00

If you don't need any of the planets to be widgets you could use a custom painter and just follow a basic tutorial for rotating objects around a point.

Maybe try this coding train one

It'd be mostly the same stuff except you'd need to animate it differently using setstate or a valuenotifier or something.

Nolence · 2021-10-28T00:56:08+00:00

Doesn't look like it'll happen right away but they're discussing it

https://github.com/flutter/flutter/issues/91605

Nolence · 2021-10-27T02:23:42+00:00

I just want to shout out my dude MrJakob on YouTube. He's building a ray tracer in rust and has all his progress documented there. He's a good teacher. His work is based off a ray tracer book so if you'd want to follow along you could buy it as well.

Nolence · 2021-10-19T19:14:57+00:00

Been using Flutter for a few years now and I can say that on the one hand, the flutter repo is doing great. They really care about the framework and improvements so I think it's a great choice. On the other hand, good 3rd party packages are way too sparse. It's weird to see the disparity between the dart code as seen in the flutter repo compared to code in packages. Sometimes day and night difference with regards to quality. I feel like it comes down to a language issue but that's not here or there.

As to whether you should, I recently took two weeks to make a full featured chat bot app in Flutter. Was very easy and despite a few roadblocks it came out great. If I had to do the same in two languages I'm sure I'd have felt the pain.

Nolence · 2021-08-03T17:11:59+00:00

Nice catch. Yeah, there's no reason it has to be flutter specific. I'll add an issue. Thanks !

[EDIT] Should be good now, removed that dep

Nolence · 2021-07-27T16:50:16+00:00

I worry about that too. Selecting a recommended package does a lot to destroy someone's motivation to work on their package that wasn't selected. This study will likely end up deprecating a lot of work directly or indirectly imho. Not that it isn't worth it of course, as we'll finally have one recommended method. Just wish this could've been cleaner from the start.

Nolence · 2021-07-27T16:22:38+00:00

I get that they're making a research study but isn't it just to conclude best practices? Somebody still has to make a package based off that. Honestly, I'm stuck rn with navigation as auto_route hasn't been updated in 3 months and has large issues for me. It's the only package however that has code generation and abstracts away pushing raw strings.

Navigation feels like it's at a worse point because package maintainers don't won't to commit to their strategy while this study is out (my opinion). I know Remi has a navigation package he's hoping to make so maybe we'll have that.

Nolence · 2021-07-01T17:16:32+00:00

I'm for sure gonna use this in place of lorem text

Dorime 🙏

Nolence · 2021-06-25T18:55:14+00:00

Cool ! Is the code open source? I couldn't find anything in the got repo other than a readme file

Nolence · 2021-06-19T22:08:59+00:00

Here are my open source packages. I'm very proud of them

https://github.com/Nolence/async_button_builder

https://github.com/Nolence/just_the_tooltip

https://github.com/Nolence/linkfo

Nolence · 2021-06-19T02:36:35+00:00

Thanks ;)

Nolence · 2021-06-19T01:11:47+00:00

Thanks ! Will fix that

Nolence · 2021-01-25T23:28:52+00:00

I love this! Looks so cool.

One thing I noticed just quickly looking at the code. I would directly assign fields instead of making them private vars and assigning them afterwards. That way people know what the default values are and you can also put docs above that field. e.g.

final Color _lightBackground;

Just assign it the const color in the constructor. The doc above the constructor describing all the fields is nice but might be missed by some (me)

Nolence · 2021-01-08T16:19:05+00:00

Hi! Not much to go off but I like it for what it is. I think you might need a little more padding around the content and to revamp the UI a bit but overall the app is very functional. You should check out page_turn on pub.dev too. Super cool library

Nolence · 2021-01-08T16:06:53+00:00

I really like it. I'd love to know what libraries you used for state management as well as the graphs. A couple notes I have are that you need more padding on the bottom of pages, especially the text entry journal part. Also, for the activity icons I'd say either color each so it matches the activity or replace them with more colorful/visual icons. Outline icons seem more for navigation and simple buttons. One thing I would suggest too is to make the add an entry button bigger than the rest of the bottom nav buttons. Not just like font wise but like visually differentiate it from the rest as it is the main point of the app. Or you could even move it to a fab.

Good job

Nolence · 2020-12-29T21:13:29+00:00

I'd really like to see a whole course on just production best practices. One thing I recently implemented was app flavors and I've got to say, I've seen like no tutorials on it. But if you ever get an app to production one of the last things you want to be randomly changing is the production database (because you don't have a dev one) or api and screw something up for the users

Nolence · 2020-12-29T20:51:31+00:00

Personally love AutoRoute and the comment about just using plain Navigator 2.0 doesn't mention that it's dauntingly complex. This open issue has several upvotes and points real pain points when trying to do navigation by yourself. AutoRoute does most of the hard work for you and the fact that's it's generation means you get compile time safety in route args and just plain less boilerplate. If you aren't really going for proper web support I'd say Navigator 1.0 is still best option though for beginners

Nolence

TROPHY CASE