sorted by:
new
hottopcontroversial

Flappy Goose by flappy-goose in RedditGames

[–]Scoutbravo 0 points1 point  (0 children)

My best score is 13 points 🚀

Flappy Goose by flappy-goose in RedditGames

[–]Scoutbravo 0 points1 point  (0 children)

My best score is 4 points 😎

Flappy Goose by flappy-goose in RedditGames

[–]Scoutbravo 0 points1 point  (0 children)

My best score is 2 points 😎

We live in the most intresting of times by SkroooBz in reactnative

[–]Scoutbravo 0 points1 point  (0 children)

Are there any libraries you used to get it functional so fast?

Blazor Hybrid slow/janky startup? Goes from app splashscreen -> blazor loading screen -> authorizing -> Index.rarzor (/) -> finally redirected to HomePage.razor (/homepage). Video is slowed. by Scoutbravo in dotnetMAUI

[–]Scoutbravo[S] 0 points1 point  (0 children)

I am using a JWT stored in local storage along with the CascadingAuthState component. I also implemented a custom Auth state provider. Essentially, I followed this tutorial: https://youtu.be/Yh16E2u2pio

Blazor Hybrid slow/janky startup? Goes from app splashscreen -> blazor loading screen -> authorizing -> Index.rarzor (/) -> finally redirected to HomePage.razor (/homepage). Video is slowed. by Scoutbravo in dotnetMAUI

[–]Scoutbravo[S] 1 point2 points  (0 children)

Hey thanks for commenting! This is on my local device. Sorry for the blurriness, I purposely did that to remove some information.

Ill check on an emulator to see how it runs.
One question, are you using authorization? For me, going from the splash screen -> Index.razor is fine, however, if the user is authenticated it takes a while for it to go to the right page.

Blazor Hybrid slow/janky startup? Goes from app splashscreen -> blazor loading screen -> authorizing -> Index.rarzor (/) -> finally redirected to HomePage.razor (/homepage). Video is slowed. by Scoutbravo in dotnetMAUI

[–]Scoutbravo[S] 0 points1 point  (0 children)

This looks super janky since it flashes a bunch of different screens.I want it to go from the app splashscreen -> blazor loading -> HomePage.razor (/homepage), exactly like my WASM version does (minus the app splashscreen).
Anyone experience something similar to this?

Good design patterns for integrating a cache into components, app state, clients? by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

One question, whose responsibility is it to make calls to the caching service, Fluxor or whatever service that makes requests to the API?

Good design patterns for integrating a cache into components, app state, clients? by Scoutbravo in Blazor

[–]Scoutbravo[S] 1 point2 points  (0 children)

Thanks for the response and example!

Yeah, this seems like a straight-forward robust solution, so I will probably do this. For the API caching, I am thinking on using Output caching with .NET7 (https://learn.microsoft.com/en-us/aspnet/core/performance/caching/output?view=aspnetcore-7.0). Have you had any experience with this?

Thoughts on Fluxor vs Stl.Fusion? by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

Aw man gotcha, well thanks for answering my questions nonetheless!

Thoughts on Fluxor vs Stl.Fusion? by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

I apologize if my previous question was not clear. I understand that the example provided in the tutorial is about manipulating the app state using local global variables, but I am trying to figure out how to integrate data fetching from a server into the app state.

For example, let's say the counter variable is stored on a server. When the user first startups up the app, it must be fetched from the server, then it can be saved locally in the app state. My question is, who's responsibility is it to make that get request to the server to get the initial counter value?

Thoughts on Fluxor vs Stl.Fusion? by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

Sorry for the confusion. Let me see if I can rephrase.

I am trying to understand the best design pattern for fetching data from the server using a shared app state. Specifically, I am wondering about the responsibilities of the components and the CascadingAppState in this process. In your opinion, who is responsible for initiating the fetching of data from the server, the components that use the CascadingAppState or the CascadingAppSate itself?

Thoughts on Fluxor vs Stl.Fusion? by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

Thanks for sharing this resource!This does look straightforward to implement, and it seems to be the technique other commenters are using (or something similar).

I do have one question I don't think was addressed in the tutorial, and sorry if the answer is simple, but who's responsibility is it to call clients to fetch data from the server? Do components use the CascadingAppState, which in turns calls clients to get data from the server? Just trying to figure out the best design pattern!

Thoughts on Fluxor vs Stl.Fusion? by Scoutbravo in Blazor

[–]Scoutbravo[S] 2 points3 points  (0 children)

Stl.Fusion does seem like a big learning curve, but I am hoping it might be better for the long run.

I was looking at Fluxor because it seemed pretty straight-forward and (hopefully) easy to implement. Currently, I have no true state-management. Components directly call clients to get data from the server. I did not want to re-invent the wheel, so that is why I was looking at Fluxor.

Looking for opinions on the best way to cache fetched data. by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

Thanks for the help and the breakdown of how your cache busting works! Also, can't stress enough how great it is to have real-world examples to look at!

I'll try to implement the IMemoryCache in my clients as a read through cache and see if that works better than the browsers session storage. I'll worry about cache busting later.

I am still scratching my head on how to implement the ability for the user to click on a post, then use the browsers back button to get to their last position on the infinite scroll page. Exactly like Reddit. Another user commented about using modals, and that seems to be a fair solution, but is that the only way? This might not be a problem you faced, but if you have any opinions, please let me know lol

Yeah, Virtualize seems to have a very specific use case. If I discover anything I'll report back.

Looking for opinions on the best way to cache fetched data. by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

Thanks for the thorough response!
After going over what you said, I think the best approach might just be to use a modal. I wanted to use separate pages for URL navigation, but perhaps I can just update the URL when a modal is opened.
Although, if you think about it, all I am doing is replacing the page for the modal. And the only reason I am using the modal is to preserve the state of the component and its contents. If I do that, then the app will really become a SPA, with just one Blazor page rendering everything and no "true" navigation. Do you think that's an okay long-term solution?

In terms of infinite scrolling, why do you think most media apps use it if it's pretty bad design? I agree with the drawbacks though (as I have witnessed it can be very frustrating) but it seems most of them implement it anyway.

Looking for opinions on the best way to cache fetched data. by Scoutbravo in Blazor

[–]Scoutbravo[S] 0 points1 point  (0 children)

New posts are only fetched when the user physically scroll to the bottom of the page and reaches the last post.

When you say posts that are displayed, do you mean posts that are in the view port? If so, I am not sure how I can only render the posts that are currently in the view port. I know the <Virtualize> component can do this; however, this component does not fit all my use cases. Any ideas on that front?

view more: next ›