@toiletpaper yes. But I want to prevent it from flashbanging the user with the white background and also don't want it to show unstyled elements while it's loading the rest.
That looks ugly and stupid.
My current solution is just show a full screen loading screen but that is really annoying.
This is like a middle ground between a real single page app and normal website with pages.
@toiletpaper like what. Not use style sheets and just unstyled html?
@toiletpaper if there is another solution to not have flashes of white and the elements loading in unstyled. Of course I would use that. I just didn't look at that yet. I just saw this randomly out of coincidence and I think it would work for that issue.
@toiletpaper like browsers showing a white screen when loading is default browser behaviour.
@toiletpaper also yea just quickly looking.... You can apparently just do what I did. Show a throbber and block the whole page until it is loaded.. But then you still get a white flash shortly and then the fucking spinner every time.
Or put some. Js to fade the body in and out. Which seems stupid too. That just makes it fade to white instead of flash.
Or use single page app frameworks like livewire they write.
@toiletpaper I don't think I would do use that specific thing. I think I'll just have it load in and display or hide the individual things the user interacted with. Component based loading. Not like fake built in page loading.
@toiletpaper well I was just experimenting with styles to get it looking a very specific I want.. It's mostly just a top bar with 5 buttons and then a repeating background.
I have not thought about do I break it into livewire components that I can change individually or how do it do it...
I basically just copied the whole page, changed the page title and what button was using my top-bar-button-active blade component.
Just to see.
So. Yea it does load the entire page fresh.
@toiletpaper it's just blade components with one single livewire component that just gets a random number to emulate a live count.
Using css in the app.css and also tailwind though
@toiletpaper lol. Well I dont know what solution I want to go with. I think I will just make a lot more livewire components. And make it more interactive overall. Just like hiding page loads is silly...
For actually for Design reasons. It would make sense if you saw it lol.
I want to try wire navigate though... Once I am home. And yes also watch that video. It's about the site I wanted to look at anyways.
@toiletpaper literally learning how to do this stuff
@toiletpaper js frameworks don't mean you can't do stuff on the server anymore though.
And idunno. I feel like you need to do. Both stuff in the client and on the server. I don't particularly like Ruby on rails for example. If you look at stuff like Hey. You click a button and it takes a second and then when it shows up in your browser it like loads in crap and snaps into place. I think they even take in multiple actions of you clicking a button before the server made the stuff.
@toiletpaper create infinite fucking calender entries and shit because oh no your browser didn't receive the answer of having successfully made an event yet because you are on 3G wireless
@toiletpaper I don't use Javascript though.. Like that's why I chose to learn laravel first. Php. And the livewire. Although sure there's like a livewire script running in the browser. But I don't actively do that.
I will do more testing though with it to see can i dynamically load and show menus and stuff... Without it looking like a rails project.
@toiletpaper I mean how much does it matter if you use php and blade to put together html pieces on your server... Compared to using nextjs to put together react and html pieces on your server.
I don't actually know because I haven't started looking at react yet... I want to eventually. Just because seems like you can get a job with it probably. And then next just mostly randomly. I hear many good things about it though.
@toiletpaper I was pretty much against react due to a misunderstanding of what react was and then react native and the other things for it was.
When I saw a video where someone just actually explained which thing is react itself and what makes it work for Web, native mobile, desktop, fucking 3d and vr and AR shit.
That actually made me kinda interested in it.
@toiletpaper I have seen one job listing for full stack developer as only done with laravel and livewire.... I think one.
But then also many which want laravel plus react. Which.. Like.. Idunno. Almost seems stupid to me but there's good reasons for it I assume.
@toiletpaper I need to go look for that video again in a bit.but I think I can find it.
@toiletpaper
That video. When he went "this is part of react-Dom" I loudly went ooohhh.
It's not exclusively him just explaining.. Also reading an article and the cross platform stuff comes up multiple times.
The rest seems good too. I used to not like him when I found his channel like 6 months ago. But I like him now. He does seem very smart to me.
You can skip the sponsor part though. Just skip to 2:00 immediately.
@toiletpaper and I get what the problem is and what they are trying and apparently achieving with it.
At least from my limited knowledge and use of other frameworks/toolkits... Like.. I know GTK XML.. I know GTK with Blueprint... Both super directly tied to how GTK works. And then actually yes that's it lol. Unless you count laravel with blade too. That's also just literally tied to Webbrowsers exclusively.
@toiletpaper lol. Yt dlp filters out in video sponsor reads?
Also yea that guy. I used to shit on him and call him a vercel shill on twitter often.. But like. I exchanged many tweets with him and watched more of his stuff. And yea i do like him now and think he's smart.
Lol just the fact that he's leaning into it and his new domain for linking to sponsors is soy.dev is already smarter than most people.
But yes. Interacting with him on twitter and watching him live changed my opinion of him.