Open comments for this post
i got bombed by my own regex
anyways, so i started making a lexical parser and uhh its not going all sunshine and rainbows. the blockquote regex doesn’t really work right and also i checked the gfm spec since i want to adhere to it and uhh fuck i might be cooked. i thought ts was going to be a 20h project help meeeeeee
also yes it took me 6 hours for 74 lines of code sob this is just great
Open comments for this post
HEADINGS NOW RENDER!
headings now render! as you can see in the screenshot, it now renders the headings as big boys also, me very happy.
this took a while because i lowk didn’t know what to really do. i didn’t think about how i would do it, i was only thinking about doing it anyways gn gng
Open comments for this post
took only this long to make a bunch of letters
you see, i had to make a bunch of custom glyphs to render headings in the terminal. making that for pretty much all the characters on your keyboard isn’t quite easy but hey its done now. the thing is, this is only for level one headings. once i finish the actual parser, i’ll add glyphs for the rest of the headings. in the meantime, i’ll have to do the rest. i did not expect to have spent this long on the project already yk
Open comments for this post
whoops, forgot to do the devlog yesterday!
well im too lazy to write stuff so here’s the gist of it:
- i made a (terrible) wallpaper in krita (and inkscape, i wasn’t able to do it properly )
- i added swaybg to the package list
- swaybg autostarts with labwc
- branding gets copied to
/usr/share/ every time i run the script to generate an iso
that’s about it, i spent a while on that wallpaper for some reason
(i just remembered i added the autostart thing in the vm and didn’t add it in the actual repo)
Open comments for this post
optimized themes.js! i also did a bunch of other stuff but i don’t remember what i did
anyways i switched from using cookies to using session storage for the theme because fast
Open comments for this post
a terminal markdown reader that has actual headings? never could have thought of it huh
well this is what i’m doing. literally a markdown reader that prints text the way you might have written it.
anyways so this is gonna use bun since bun is ultra fast. also this might be a 10-20h proj, shouldn’t be too hard.
well i like more hours, so i might also add stuff like:
- browsing all the markdown files in a directory (and subdirectories)
- editing (very unlikely!)
well i don’t really know what else to put so ig that’s it? anyways i have actually done some work, that is, my file currently ouputs some text. literally the raw original text. what’d you expect from 24m of coding
Open comments for this post
woah woah woah! check this out!
i customized waybar and got submenus working! well that doesn’t sound all that impressive, until you realize i had to plan it out. the thing is, much of this time didn’t get logged because i was testing configs in the virtual machine, which is a live usb without persistence. i just typed one line at a time and looked at how it changed and what could be improved.
for the waybar, you might be wondering what happened to the colorful stuff. well, once i started my own styles, it stopped using the default config. it does look pretty cool tho!
as for the right click menu in the background, you can see that it is showing a submenu too. the main menu has six things: firefox, a libreoffice submenu, a separator, a teminal, shutdown and reboot. the submenu has options to open the main libreoffice window, a libreoffice writer window, a libreoffice impress window and a libreoffice calc window.
also, i took that icon out the full logo to make a colorful and white icon! now just the wallpapers, which i installed krita for.
that’s about it for today, and see you guys tomorrow!
Open comments for this post
hey hey hey!
today was mostly creating a logo
you can find it on github, but you wouldn’t open it, so here it is!:
anyways, besides that, today i was able to get waybar to autostart
so tomorrow, i’ve gotta do these:
- separate the icon out of the logo
- start with wallpapers
- get a proper config, this is nothing
anyways, bye!
Open comments for this post
poof! there is now a gui!!!
as you might have guessed, there’s still no artwork
however,
- there is now some gui! in the screenshot, i am running waybar manually from a terminal.
- the terminal in question is called
foot ( - also, there is 0 config of anything at all
- the login works perfectly! i don’t have a screenshot and i don’t want to boot up the vm again for this
- speaking of vms, i finally figured out why everything was so slow and sluggish—it was because qemu was using TCG (tiny code generator) (software emulation) instead of KVM acceleration (kernel-based virtual machine). i turned on kvm and it started up in SECONDS.
that’s about it, and see you all tomorrow!
Open comments for this post
aaaa i found out lxdm can’t launch wayland sessions so i have to use something else. i settled on greetd for the backend login manager and greetd-regreet for the frontend.
i chose regreet because apparently it’s written in rust, uses gtk4 and can easily be styled with css! will be great!
anyways, as for the actual stuff, i put labwc in the package list even though its not configured. also, i still haven’t started with the artwork.
so far, this is what i have that works (:sk:)
Open comments for this post
i updated some info on the site! macOS sequoia and tahoe have had updates since i last checked, and i updated the releases.json files for both versions! don’t know why it took so long tho
i got a LOT of stuff to do, and i honestly don’t feel like starting another article, but i have to
Open comments for this post
amethystOS: you can’t tell its arch without the terminal!
today, i tried to get a lightweight login manager working.
- first, i thought of
sddm, but when i saw it, i felt it was too ugly.
- then i thought of
wlgreeter, but it wasn’t in the repos.
- eventually, i settled on
lxdm. it looks good and seems to work well.
now you see, the problem is i need to auto-login into labwc, the compositor. remember that you don’t need a full desktop environment to ship a distro. the compositor can work well standalone. you just have to install a few things to be able to actually use it, and that’s what i plan on doing.
also, i need make some artwork for this. i’ve already come up with a few designs for logos and wallpapers, i just have to actually make them in inkscape! i feel like my 4 wallpapers and final logo are pretty good!
hoping to get stuff actually working tomorrow ✌️ i need to:
- configure autologin for live cd
- configure lxdm
- auto-start the calamares installer when the user boots the disk
- make a custom boot animation
- of course, make the boot animation
Open comments for this post
its arch but it has a gui installer but its not manjaro or endeavor!!!
amethystOS is arch but you can actually use it without being a wizard in the terminal. why install a gui yourself and spend hours (trying to) configure your setup when you can have the distro decide for you?
and not only that, it comes with a bunch of pre-installed applications! libreoffice, the fox on fire, and more!
at least, that’s the goal. i can’t even make an arch iso rn because whatever happened to the repo.
anyways, you might see that the initial commit is from january, but that’s because i started this and never really started it.
so as for what i actually did, i tried to get calamares working, but no, it kaboomed. well i’ll have to fix that, obviously, but i will work on the logo and artwork in the meanwhile!
hoping for a great result by the end of this!✌️
Open comments for this post
hey guys! hi guys! it’s time for ospedia: season 3!!!
not much has actually changed since the end of flavortown, except for information and style updates. besides those, literally nothing has happened.
however, the information updates include these:
- completion of the articles for ubuntu 6.06 lts and 6.10
- update of the releases list for macos sequoia and tahoe
- added blockquote styling
- contributors’ list in readme!
protip: if you don’t see changes on the main site, that’s because development happens on the unstable branch, which deploys to https://unstable--ospedia.netlify.app!
get ready to see ubuntu articles by the end of stardance!