arraybolt3 | so I think something must be wrong with the Calamares bootloader config, since it seems to have failed to install a UEFI bootloader at all. | 00:13 |
---|---|---|
arraybolt3 | Not sure what's up there, will have to debug shortly. | 00:13 |
arraybolt3 | actually it may all have just been a problem with my system's clock being out of date | 00:14 |
arraybolt3 | anyway, after much trials, I finally got Kubuntu 24.04 installed :P | 00:14 |
* arraybolt3 afk for a while | 00:14 | |
arraybolt3 | back for a bit | 00:23 |
arraybolt3 | ok so it's the WiFi code's fault :( | 00:26 |
arraybolt3 | found the bug | 01:27 |
arraybolt3 | I'm pretending like there's always an active connection when there might not be | 01:27 |
arraybolt3 | and dereferencing a null pointer in so doing | 01:28 |
arraybolt3 | Got *most* bugs sorted out in the installer prompt network stuff. There's one that's going to be a bit harder to squish than the others, which is why I haven't uploaded yet, but stay tuned. | 04:30 |
BluesKaj | Hi all | 13:42 |
sgmoore | hiyas | 14:01 |
mmikowski | Hi everyone! | 17:34 |
* sgmoore waves | 17:35 | |
arraybolt3 | Looks like the big bad last bug is just about squished in kubuntu-installer-prompt | 17:37 |
arraybolt3 | I'll almost certainly be doing an upload later today, which will get the networking stuff working much better. | 17:37 |
arraybolt3 | also, 22.04.4 release day is tomorrow, so I'm going to be testing like crazy. | 17:38 |
sgmoore | Did the general test cases myself. Still have the default webbrowser could be dash problem, release-notes opens kate, don't think I can fix it with one days notice haha | 17:41 |
arraybolt3 | Uploaded and pushed to git. | 19:12 |
arraybolt3 | (kubuntu-installer-prompt I mean) | 19:12 |
mmikowski | hey aaron, does the installer look like the mockup? | 21:35 |
arraybolt3 | Pretty dang close, yes. | 21:38 |
arraybolt3 | mmikowski: https://i.imgur.com/ic8oCKO.png | 21:39 |
arraybolt3 | Only known issue I still haven't sorted out is that if you select a right-to-left language, the entire UI flips to match with a right-to-left layout, and that messes with the CSS I'm using to position the drop-down arrows on the combo boxes. | 21:41 |
arraybolt3 | because Qt can't figure out that it needs to turn my "shift left" into a "shift right" if it's going to flip the whole entire app horizontally | 21:41 |
arraybolt3 | so anyways I'll have to figure out how to do that part myself. | 21:42 |
arraybolt3 | or figure out what I did wrong with CSS | 21:42 |
mmikowski | hey, yeah, pretty dang close | 21:42 |
mmikowski | $0.02 (unsolicited) 😁 | 21:43 |
arraybolt3 | (I don't blame the Qt devs for not making the CSS positioning work right, I'm probably just misusing the feature somehow. But I am a bit frustrated :P | 21:43 |
mmikowski | I can help with CSS | 21:43 |
mmikowski | I know it quite well | 21:43 |
arraybolt3 | but can you figure out the undocumented setting that lets you tell Qt to *not* put the arrow in the completely wrong spot without using a margin setting? | 21:44 |
mmikowski | my $0.02 comment was more space between the two selectors would be good. | 21:44 |
mmikowski | They seem a little cramped. | 21:44 |
arraybolt3 | hmm, that's a thought | 21:44 |
mmikowski | But otherwise, pretty super | 21:44 |
arraybolt3 | I kind of liked how close they were to each other, and am not sure if moving them closer will be easy. | 21:44 |
arraybolt3 | er, moving them further apart | 21:44 |
arraybolt3 | but it might be worth a shot, and we can do it in the same upload as when we fix the arrows, if we fix them :P | 21:45 |
mmikowski | Yeah, I think 1.5x the current space | 21:45 |
mmikowski | so if it's currently 16px, 24px probably would look better | 21:45 |
mmikowski | maybe 32px | 21:46 |
arraybolt3 | the problem is right now the way it's implemented isn't "16px" or "24px", right now it's implemented as "no spacer" | 21:46 |
mmikowski | Yeah, I know :) | 21:46 |
arraybolt3 | and adding a spacer will increase the width by about three or four times and shift all the other elements XD | 21:46 |
arraybolt3 | which can be worked around, or perhaps some CSS margin magic can fix it more easily | 21:46 |
mmikowski | well, I mean, I figured it was a spacer element in QT. | 21:46 |
mmikowski | margin magic is good | 21:46 |
arraybolt3 | actually I guess you can make a height limited spacer, and it should scale right | 21:47 |
arraybolt3 | so it might be easier than I think | 21:47 |
mmikowski | The other bit missing I think is the drop shadows. | 21:47 |
mmikowski | The edges on the buttons IMO should pop somehow; | 21:48 |
mmikowski | if not a spread shadow, maybe a line. | 21:48 |
arraybolt3 | yeah, sadly drop shadows are ERR:FEATURE_MISSING_IN_QT | 21:48 |
mmikowski | haha | 21:48 |
arraybolt3 | unless we port to Qt Quick | 21:48 |
mmikowski | yeah, thought maybe | 21:48 |
arraybolt3 | which I'm not all that excited about doing | 21:48 |
mmikowski | Contain your enthusiasm 😜 | 21:49 |
mmikowski | so then option B: | 21:49 |
mmikowski | edge treatment, which can be trivial. | 21:49 |
arraybolt3 | how would that be done? | 21:49 |
mmikowski | here, I'll snag sand mock | 21:49 |
arraybolt3 | (The trouble is I say CSS, but it's not really CSS, it's Qt Style Sheets, which are to CSS like what QML is to JavaScript, though not quite that bad.) | 21:50 |
mmikowski | hahah | 21:50 |
mmikowski | well generally it's a subset | 21:50 |
arraybolt3 | essentially trying to do anything "fancy" will fail with an "unrecognized property" error. | 21:50 |
mmikowski | So when it's there, it's the same | 21:50 |
arraybolt3 | right | 21:51 |
mmikowski | and when it's not, you're out of luck | 21:51 |
mmikowski | that's not too bad | 21:51 |
arraybolt3 | well, at any rate, if you want to pull-lp-source kubuntu-installer-prompt and fiddle with the style sheet values on the buttons themselves, you'll be able to see what is possible and maybe get it working. | 21:52 |
arraybolt3 | or I can share the stylesheet with you and you can tell me what to change | 21:52 |
arraybolt3 | that's probably easier | 21:52 |
mmikowski | So some aspects of your design actually look better than the mock. | 21:53 |
mmikowski | In particular, I like the larger font. | 21:53 |
mmikowski | https://kfocus.org/NobleDev.f9150309/noble-installer-mockup-01.png | 21:56 |
mmikowski | That has drop shadows | 21:56 |
mmikowski | notice how the text areas and buttons are the same color | 21:56 |
mmikowski | *drop shadows =~ spread shadows | 21:57 |
mmikowski | Instead of spread shadows, the top combo boxes have a white border | 21:57 |
mmikowski | so a similar thing might be done for the buttons. | 21:57 |
mmikowski | Lemme upload a mock, and then we can take it off line at your convenience | 21:58 |
mmikowski | ok | 21:59 |
mmikowski | https://i.imgur.com/e0nmU9H.png | 22:07 |
arraybolt3 | hmm, that's a thpught | 22:08 |
arraybolt3 | dog needs outside, but we'll come back and see if this is feasible in a bit. Will that work for you? | 22:09 |
mmikowski | sure aaron. I'm again completely fine doing this dm. | 22:11 |
mmikowski | The right color for the buttons / inputs are probably somewhere inbetween. | 22:12 |
mmikowski | https://i.imgur.com/pqXoJkV.png | 22:29 |
arraybolt3 | there it is | 23:41 |
arraybolt3 | not yet | 23:42 |
arraybolt3 | need to add that | 23:42 |
arraybolt3 | yeah | 23:44 |
arraybolt3 | ok, you're going to hate this, but... | 23:44 |
arraybolt3 | problem | 23:44 |
arraybolt3 | so we need to style those, but this part doesn't support radius. | 23:45 |
arraybolt3 | the actual drop-down itself | 23:45 |
arraybolt3 | almost | 23:45 |
arraybolt3 | did you see it? | 23:45 |
arraybolt3 | yeah | 23:45 |
arraybolt3 | can you not see me? | 23:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!