lyse
lyse.isobeef.org
No description provided.
No description provided.
@stigatle@yarn.stigatle.no Cool! Was it still using coal?
@adiabetic@www.frogorbits.com I hope you finally managed to fall asleep by now. If not (or for next time), you need to drink one glass of water in one big sip without stopping in between. Works every time.
Like @prologic@twtxt.net, I can’t give you any hints, @eaplmx@twtxt.net. Sorry. For me, a hobby project just has to be fun in some way. But I know this too well myself, over time interest is lost and thus the project never finished. But I reckon that’s fine, too. Because there was a time where I had fun and/or learned something. However, I fully agree that it doesn’t feel good to not have completed the project.
@movq@www.uninformativ.de Aha, you tricked me! ;-) So basically I’ve seen the first half of the video already? Hm.
@eaplmx@twtxt.net You’re spot on. Making everything configurable opens a whole sea container of worms. You convinced me to make it as simple as possible. Haha, no, I do not have paying users, in fact it’s just me. Maybe up to three other mates in the future. It’s just a hobby project, so there won’t be anybody paying anything. And that’s perfectly fine for me as nobody can force me to do something. :-)
I’ll go with two predefined exercise types, that’s all that I need at the moment. Yeah, keeping extensability in mind is very important. Thank you very much for all your valuable input!
Our approaches differ in measurements, I don’t care about calories, although, that is most likely by far the best meaningful number. It’s just not something I’m interested in and I also don’t have any way to measure it. In that regard I’m like a child and want to play with counting exercises. ;-)
Thanks, @xuu@txt.sour.is, I’ll try to check it out at the weekend.
@stigatle@yarn.stigatle.no Awww, how nice! I’d love to be there and cool off right now.
@eaplmx@twtxt.net The big question is: How to deal with different sorts of exercises. Like situps and pushups require a counter, but a bike ride or hike do not. They require a distance, a route and what not. Should I go full overboard and make the exercise types completely user-configurable? Or should I just offer two different things built in with the option to expand later on in the code if necessary? Two fundamentally different solutions.
@prologic@twtxt.net Everything will be done with good old plain form requests. The only thing where JS was involved was the map of course. I think for the weight graph a mate used the <canvas>
or something like that, so JS was required, too. Unfortunately. For the “Enter Exercise” form JS helped to disable the free text input field when another exercise was selected. But it also worked flawlessly with JS disabled. Or was there some CSS trickery going on? Can’t remember. Can’t remember. Would need to look into the code.
The key is to have everything working without JS. JS might only be used to add little UX benefits. But it must remain working without JS, too. That’s my fundamental rule for over a decade now.
Yes, UI and REST API are two very different things. I started with the REST API to have something very simple and functional. It’s much easier to test and I can simply have a shell script to interact with.
@mckinley@twtxt.net Gotta watch it over again tomorrow, I totally missed the paint job! And probably heaps more.
@eaplmx@twtxt.net Writing some explanations took forever. Also had to start it three times on my old machine where I had a working development setup. And still I missed a couple of things to truely showcase everything, but my bed is calling. There you go: https://lyse.isobeef.org/kraftwerk1/
@movq@www.uninformativ.de Oh, I see. I just somehow assumed you went the extra mile to also use the equipment from back in the good old days. :-) Right, totally forgot about crypto. But also all the JS crap probably breaks down.
@abucci@anthony.buc.ci @movq@www.uninformativ.de Oh, interesting. Then I take back my critique this time. I wasn’t aware of that 1024 byte limit either. Working now. I just send it always in the Content-Type
header and sometimes even omit it from the HTML altogether. But when I do, I also use the shorter and more reasonable looking HTML5 style <meta charset="UTF-8">
, just like @eaplmx@twtxt.net showed. The advantage with the HTTP response header is that I just tell nginx to do it for me, so I cannot forget it in the HTML by accident. Well, in case I forgot, it’s not an issue.
But specifying it also in the HTML helps everybody who happens to download the page. Opening it locally then obviously cannot make use of the nonexisting HTTP response header. Not that I think there are a lot of people out there downloading it, but just in case. :-)
Do you happen to have all your browsers set to fall back to UTF-8 if they can’t detect the encoding, @abucci@anthony.buc.ci?
@movq@www.uninformativ.de Wait, what?! A year has already passed again? No way! Even better, it caught me by surprise, no more waiting. :-) This is an extremely lovely project, mate! Again, just like last time, suddenly: autum. Bam. Out of nowhere. Basically the same with spring, leaves are everywhere after the blink with an eye. But autum with the drop of the leaves is much more extreme. I kind of miss the orangy season, though. I had the impression it lasted longer last time. Not by much, just a little bit longer.
As predicted, I did not saw the accident where you had to re-setup the camera. I tried to spot it, no chance. Very well done!
I’m also loving your new ideas. Go for it!
We barly survived the trip outside. It was and still is just awful hot out there without any wind. Standing air. Luckily we were walking quite fast, so we had a wee bit of airflow. The sun has set for over three quarters of an hour and the thermometer still reads 27°C.
Besides this slow worm and a second, much shorter one later on, a larger frog jumped across the path in the dark. Later a mouse or something along those lines rapidly switched sides and ran over the path. Both just half a meter in front of us, quite cool. Also seen two deer.