<skirst>
Begasus, found and installed the theme manager and the flat style. got thrown into kernel debug when applying it :( rebooted and it was far from flat but indeed dark! guessing it was just the color scheme with default widget style
<Begasus>
I knew I had some issues when I checked the last time ;) (sorry)
<skirst>
no worries! thanks for the tip!
<Begasus>
ps, Terminal has it's own color themes also (that one is black here)
BrunoSpr has quit []
<skirst>
yeah, i have that :D and the config backed up for when terminal barfs on it's config
BrunoSpr has joined #haiku
<Begasus>
heh
<skirst>
haiku would look so awesome with a good dark theme. those yellow tabs will really pop! wish i had the time to tinker
BrunoSpr has quit [Quit: Vision[]: Ich wurde verwaschen!]
<Begasus>
hrev55504 doesn't work with booting, icons scrambled over the screen at the bottom, can't even seem to boot the installed system with it :/
Animortis has quit [Remote host closed the connection]
Animortis has joined #haiku
deavmi has quit [Read error: No route to host]
deavmi has joined #haiku
AlaskanEmily has quit [Remote host closed the connection]
<Not-5726>
[haikuports/haikuports] Begasus pushed 1 commit to master [+0/-0/±1] https://git.io/JKvAe
<Not-5726>
[haikuports/haikuports] Begasus b682eea - blender, revbump for rebuild (for new mesa package) (#6267)
<Begasus>
k, didn't build this one, should be good as nothing else changed inthere
deavmi_ has joined #haiku
deavmi has quit [Ping timeout: 480 seconds]
<jt15s[m]>
Begasus: we haven't enabled the link to the nightlies on the downloads page, but you can always directly access the nightlies page at https://download.haiku-os.org
<Begasus>
jt15s[m], found it through google, but thanks :)
<jt15s[m]>
* downloads page (we're waiting until Beta3 gets a bit older), but
<Begasus>
maybe you could mention there how to update the Beta3 once it's installed too?
<Begasus>
updated this morning to +62
<Begasus>
55500 same issue, maybe I should just grab the beta :)
<Begasus>
bbl
pch_ has quit [Remote host closed the connection]
pch_ has joined #haiku
augiedoggie_ has joined #haiku
AlwaysLivid has quit [Ping timeout: 480 seconds]
augiedoggie has quit [Ping timeout: 480 seconds]
<nephele[m]>
andreasdr, jessicah: Yes, i am making additional UI for dark mode, aswell as misc fixes for apps that do not work as is with a dark appearence
<nephele[m]>
andreasdr: Quaternion of course, they have me in their about box ;), but in all seriousness Quaternion is a more irc-esque ui, and nheko a more "modern" "smartphoneish" UI, personally I prefer to use Quaternion but both should work somewhat fine on Haiku, Quaternion just feels more at home to me (and it's "more" working with standard controls)
<nephele[m]>
for file uploading both will work just fine
mmu_man has joined #haiku
BrunoSpr has joined #haiku
<BrunoSpr>
Begasus... installing from nightly was not easy, did not do it for a real long time... some problems I had. finally I cloned my USB-Haiku 30GB to USB-Haiku2 60GB but only 30GB used because it was cloned... anyway now it works and I have a 30GB free partition for Data/home
bobsmith432 has quit [Remote host closed the connection]
<BrunoSpr>
hello... anyone an idea if I have to rename the haiku_loader.efi to BOOTX64.EFI ?
<nephele[m]>
Do you have a loader entry that points to haiku_loader.efi?
<nephele[m]>
if not, you might want to rename it, it then becomes part of the "fallback" path the EFI takes if it has no matching entries, if you put it in the right directory, there the name is important.
<nephele[m]>
It will overwrite the BOOTX64.EFI you already have however, for what OS is it? if it doesn't matter you can just delete it I suppose :)
<BrunoSpr>
nephele[m]... no I do not think I have a loader entry... nothing done by my side...
<nephele[m]>
Then you probably do want to name it BOOTX64.EFI, this works well if you only boot Haiku on that machine
<BrunoSpr>
There is still a Windows install on this machine
<nephele[m]>
not so well if you want to dual boot, if that is the case you either do need to make loader entries, or you need to use something like rEFInd
<nephele[m]>
Yeah, if it's windows on there don't overwrite the fallback path, you will make windows unbootable, because it tries to use the fallback path
<nephele[m]>
IIRC anyhow
<BrunoSpr>
I always manual boot
<nephele[m]>
You would then need to move the BOOTX64.efi somewhere else, maybe windows_loader.efi, and use rEFInd instead
<BrunoSpr>
no boot loader or Bootman
<BrunoSpr>
ah ok
<nephele[m]>
the EFI executable is the boot loader, if you remove it windows won't be bootable anymore
<BrunoSpr>
I leave it like it is then...
<nephele[m]>
You can also make a "entry" in your efi for haiku, and point it at haiku_loader.efi and then you have a "Haiku" entry in your boot menu
<BrunoSpr>
no risk and not into studying lots of EFI and REFInd installations... too complicated for me atm
<nephele[m]>
it's a bit more complicated to do this however, refind is probably easier, it gives you a nice graphical menu to pick from and automatically finds all efi executables to boot
<nephele[m]>
Installing is basically just moving it to the right place IIRC
<BrunoSpr>
how to edit the entry in the efi?
<nephele[m]>
You need a special tool, i think on linux it is called efivar or something?
<BrunoSpr>
ah no forget it it is too complicated for me atm...
<nephele[m]>
efibootmgr
<BrunoSpr>
sorry not into experiments today
<BrunoSpr>
I already lost my Haiku install because of the MESA files yesterday...
<BrunoSpr>
it was not working so I deinstalled and installed some MESA files from HaikuDepot...
<BrunoSpr>
after that lots of my programs vanished
tqh has joined #haiku
<julicenri>
Is it possible to batch export HVIFs to SVGs?
<Not-5726>
[haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1] https://git.io/JKf5n
<Not-5726>
[haikuports/haikuports] korli 4421e01 - extra_cmake_modules: provides also without _x86
<nephele[m]>
BrunoSpr: check previous state? I suspect mesa was bumped and it deinstalled stuff that dependet on previous mesa
<nephele[m]>
julicenri: yes, no, maybe. check the "translate" command
<nephele[m]>
Either it has hvif to SVG in that list, or it has to be patched to get that, but i think the functionality might be only in IOM (and then only as IOM->SVG instead of HVIf->SVG, but i dont know this for certain, so check :D)
HaikuUser has joined #haiku
<julicenri>
I do see both HVIF and SVG translators.
<julicenri>
Does that mean conversions between both formats are possible with it?
<nephele[m]>
The translator command lists every conversion it knows explicitly
<nephele[m]>
with inputs and outputs for each
<julicenri>
So, that's a no then?
<Not-5726>
[haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1] https://git.io/JKfbt
<nephele[m]>
if it's not possible it is probably a good idea to make a bug report about this
<nephele[m]>
iirc someone also wanted to convert wonderbrush to HVIF on the commandline directly to be able to do this in a build
<julicenri>
Tbh most of the translators seem to only convert to Be Bitmap.
<julicenri>
Either I'm not understanding something here or that means a lot of bug reports will have to be filed.
<nephele[m]>
That is what many things need, HVIF is nice, but in the end it needs to be displayed as a bitmap :P
countryboy has joined #haiku
HaikuUser has quit [Quit: Vision[0.10.3]: i've been blurred!]
<nephele[m]>
Functionality for some of these things already exists in WonderBrush or Icon-O-Matic and should be moved
HaikuUser has joined #haiku
HaikuUser has quit []
<julicenri>
If I'm not misunderstanding anything, pretty much every image format translator can't convert to other formats.
<nephele[m]>
You are free to file a couple of enhancement tickets for the translator, how many you file is up to you, but i doubt that filing every possible conversion makes much sense, Wonderbrush+IOM+HVIF+SVG could be one translator for instance
<nephele[m]>
THis code also already exists mostly, it needs to be moved
<nephele[m]>
Maybe file one for the more pressing issue of IOM/HVIF -> SVG for the time beeing? :)
<julicenri>
I'm just not sure if I understand the concept of translators enough to confidently file tickets.
spa has quit [Quit: Help.]
<nephele[m]>
It's a library that is supposed to convert from "file format" to an applications native file format mostly
<BrunoSpr>
I did use preinstall but could not update it to newest hrev 55500
<BrunoSpr>
so I deleted all
<BrunoSpr>
reinstalled it...
Maturion has quit [Remote host closed the connection]
spa has joined #haiku
<julicenri>
nephele[m]: Sounds like it would be out-of-scope to have translators convert to other formats besides Be Bitmap then?
<julicenri>
IDK
<nephele[m]>
no
<julicenri>
Um, guess I'll just do manual conversions with IOM for now then.
<nephele[m]>
exporting is fine for it aswell, but it's main "pretty" gui use is fancy stuff like opening pdfs in IMageViewer
<nephele[m]>
please file a ticket, it's not supposed to have to be done manually
julicenri has left #haiku [And now, I disappear!]
julicenri has joined #haiku
spa has quit [Quit: Help.]
spa has joined #haiku
spa has quit []
spa has joined #haiku
<nephele[m]>
In essence translators are a library for file type conversion, if i understand it correctly applications should support their native file types, and use translators for the rest, so in essence applications with a similar scope can open files the system supports easily, and export them easily
<nephele[m]>
this to avoid each image processer for example to know how to convert to bmp, gif, tig, png, pdf etc, and just have this code once in the system as a translator
<nephele[m]>
You can check Preferences/DataTranslators for some we have already also, with their info
<nephele[m]>
(They are mainly IIRC in /system/add-ons/Translators/ )
<Not-5726>
[haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1] https://git.io/JKJTW
<Not-5726>
[haikuports/haikuports] korli 6cff866 - cython_python3: provides also without _x86
<Not-5726>
[haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1] https://git.io/JKJID
<Not-5726>
[haikuports/haikuports] korli 2ed043f - cython_python38: provides also without _x86
<Not-5726>
[haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1] https://git.io/JKJLG
<Not-5726>
[haikuports/haikuports] korli eb64275 - cython_python39: provides also without _x86
<countryboy>
python = a small dragon ...
countryboy has quit [Quit: countryboy]
countryboy has joined #haiku
<countryboy>
hello ...
<countryboy>
i apologize ...
<countryboy>
python = a small dragon
<countryboy>
just add the legs ...
<nephele[m]>
a reptile
<countryboy>
bad link ...
<countryboy>
negative ...
<Not-5726>
[haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±1] https://git.io/JKJOq
<nekobot>
[haiku/haiku] 4a850ca730d8 - PoorMan: update thttpd from 2.25b to 2.29
<Begasus>
didn't watch the whole video but nice progress rennj ... although I think the last one in the list didn't realy appeal to me :)
<Begasus>
looked a bit like Doom in it's first version
<rennj>
Ultrakill Prelude - Doom Eternal On A Budget
<mrentropyvcs>
I installed some fonts last night (from HaikuDepot). LibreOffice doesn't see them, but Calligra does. Is there something in LibreOffice that needs to be done to use them?
<Begasus>
maybe they are not supported by LO?
<Begasus>
or LO doesn't look in that folder (then it should be patched)
<Begasus>
but did some font packages a while ago and they showed up in LO ok
<mrentropyvcs>
Hmm. Well, I can use Calligra. Still in the camp for a native word processor, though. Or running 32-bit Productive in 64-bit Haiku.
BrunoSpr has joined #haiku
<Begasus>
[259/3069] Building CXX object intern/...les/cycles_bvh.dir/bvh_unaligned.cpp.o
<rennj>
You will either have to build Blender 2.93, which is compatible with OCIO 2.0.0, or use the library version compatible with 2.91.2.
<rennj>
like its going to fly with vesa graphics anyway
<jezek2>
CRTs were great :D one time I even simulated a "retina" density (>200dpi) on a 19" CRT by using 1920x1440 resolution and shrinking it to 50% of visible area :DD of course the detail wasn't fully there but interesting for a test
<rennj>
waiting on the VR minus the fakebook telemetry,
<rennj>
lighter headsets also
<rennj>
builddir/build/BUILD/blender-2.91.2/intern/opencolorio/ocio_impl.cc: In member function 'virtual void
<rennj>
virtual void!
<rennj>
i know that beos tune
<rennj>
5038 and virtualvoid rocked!
<rennj>
throwing monitors off beos building did not!
<nephele[m]>
BrunoSpr: The UI is bad is not really fixable with editing some XML :P
<Begasus>
bbl, or tomorrow :) cu peeps
<nephele[m]>
(for example, in chart titles it's suddenly much harder to get subscript letters, I have no idea why, but there is an open bug about this, it's not that tragic if you want to write "Gross incomin in %" but it sure is annoying when you want to write "H₂SO₄ Usage")
Begasus has quit [Quit: Ik ga weg]
Begasus_32 has quit [Quit: Vision[]: Gone to the dogs!]
Animortis has quit [Quit: leaving]
countryboy has joined #haiku
<BrunoSpr>
how to add the print to PDF translator to the print preferences?
KapiX has joined #haiku
AlwaysLivid has joined #haiku
<rennj>
create a printer i want to say
AlwaysLivid has quit [Remote host closed the connection]
<nephele[m]>
Don't think there is a gui way to get it back :/
<nephele[m]>
this is from config/settings/printers/Save as PDF
<nephele[m]>
maybe it helps if you extract it there, i only zipped up the Save as PDF file
<rennj>
/boot/config/home/add-ons/Printers on beos
<rennj>
has pdfwriter
<BrunoSpr>
yes but I deleted it by accident
<nephele[m]>
rennj: the problem is not the addon beeing deleted, but the "config" that makes it visible in the print settings
<nephele[m]>
and the print settings has no gui way to get it back i think
<nephele[m]>
BrunoSpr: Let me know if the zip helped restore it :)
<rennj>
/boot/config/home/settings/printers on beos
<rennj>
those 2 dirs
<BrunoSpr>
ah yes that could work
WoC has quit [Remote host closed the connection]
WoC has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
<rennj>
the instructions should be in software pkg for pdfwriter for beos anyway
<rennj>
no clue about haiku
<nephele[m]>
rennj: not sure what you mean with beos, haiku already has a pdf writer included
<BrunoSpr>
yes it is there again now, thanks alot nephele[m]
<rennj>
beos did not include it
<nephele[m]>
BrunoSpr: :)
<BrunoSpr>
great
<rennj>
it was software you had to add the system
<rennj>
so if you look at the old pdfwriter software from beos...probably can get a clue what way haiku went
<nephele[m]>
Haiku already has it though, so i really don't see how BeOS specific instructions would help...
<nephele[m]>
If you want to know how haiku does it just look at the source code :)
<rennj>
rather than reinstall, you should be able to figure it out from haiku live boot
<rennj>
query of simple find pdf from live cd
<nephele[m]>
There is no reinstall involved, haikus packages are immutable
<nephele[m]>
the pdf printer was never deleted
<rennj>
immutable till you delete the printer
<rennj>
the settings
<nephele[m]>
no, just immutable, there is no way to delete the actuall driver
<nephele[m]>
You can screw up your configs sure, but that has little to do with reinstalling :)
<rennj>
yeah ok
BrunoSpr has quit [Quit: Vision[]: Ich wurde verwaschen!]
<rennj>
its only immutable if its on readonly media
<rennj>
read writable media, readonly fs still subject ot data corruption
<nephele[m]>
Nope, it's immutable in general, you cannot change files from them, they are threated as RO, readonly media is also subject to data coruption
<rennj>
yeah sure, and you doing checksum on each load?
<nephele[m]>
for example cd's can be scratched, but that hardly justifies calling CD-R a rw medium
<nephele[m]>
Dunno if it does now, but it certainly should? it's a good tool to detect data corruption, ideally you can even do this on the filesystem block level like ZFS does
<rennj>
data on the harddrive where most people install it..is subject to errors
<nephele[m]>
RAM is subject to errors, so is the CPU, where is your point? It's abstractions and simplifications all the way down
countryboy has left #haiku [#haiku]
<nephele[m]>
With "haiku system packages are immutable" I don't mean "It is absolutely impossible to ever change haiku packages" But rather "there is no way during normal operation to modify system packages", You certainly can make the kernel just overwrite sectors on the disk, or make the system re-create the package to remove a file, but that is not really what the system does normally or allows users to do really.
tuaris has joined #haiku
<rennj>
i live.iso is immutable, readonly media, no remastering/re opening of iso session. the checksums on those files should never change.
Babaj has joined #haiku
<rennj>
the same can not be said for data on harddrive, unless you got something like zfs running
<nephele[m]>
iso9960 is also "just" a filesystem, it has no additional data protection
<rennj>
harddrive bios, disk cache, to hba controller can all corrupt stuff
<nephele[m]>
it's the cd itself that has the data checksuming properties, only a written medium would have any sort of error detection (and only limited correction capabilities)
<nephele[m]>
an iso has no specifal power
<nephele[m]>
rennj: hardware does break, hardware misbehaves and hardware can't be trusted, I still don't see your point. In IT it doesn't make much sense to me to say stuff /isnt/ something just because hardware could in theory screw it up, even mathematically checksums aren't perfect either. with enough corruption you could mathematically generate an error that would result in a faulty block recognized as correct. This is just so statistically unlikely
<nephele[m]>
it will probably never happen
<rennj>
trident linux and ghostbsd are 2 iso's that use zfs and checksumming on files from liveboot.
<rennj>
real nice features
<nephele[m]>
Have you checked whether haiku packages do checksumming as a prequisite for mounting?
<AlwaysLivid>
are you using a virtual machine btw
<AlwaysLivid>
e.g. qemu
<nephele[m]>
For what purpose AlwaysLivid ?
<AlwaysLivid>
nephele[m], idk, whenever i use the haiku and install some stuff (there's not a lot of space), it persists
<nephele[m]>
AlwaysLivid: If you want the filesystem image to be RO you have to tell qemu to do that
<rennj>
whole point of ZFS is to address failures like that and bitrot
<nephele[m]>
otherwise it will just make the ISO rw for you
<AlwaysLivid>
which is why i asked
<nephele[m]>
I don't use qemu to boot haiku unless i test specific kernel drivers and don't want to reboot
<nephele[m]>
rennj: still has nothing to do with the assertion that system packages are immutable, shrug
<rennj>
whatever dude...its only immutable if its not writable
<rennj>
you put files on harddrive and i can write to them
<nephele[m]>
Which is exactly what haiku does for the filesystem representation...
<rennj>
worm drive is immutable
<rennj>
write once read many
<nephele[m]>
AlwaysLivid: Haiku persists states on the "live" install because it works exactly like a normal install, it just has one more script that runs on first boot once, it's the same behaviour as if you had copied the installer iso to a USB drive
<AlwaysLivid>
which is why i asked
<nephele[m]>
I don't know what you wanted to know there, really AlwaysLivid
<nephele[m]>
How does that relate to whether I use qemu?
<AlwaysLivid>
oh, sorry, forgot to clarify that i was referring to rennj
<AlwaysLivid>
my bad
<nephele[m]>
oh, ok
<nephele[m]>
AlwaysLivid: do you compile haiku yourself?
<AlwaysLivid>
ye
tqh has joined #haiku
<nephele[m]>
Want to play around with dark mode colors? :)
<tqh>
I think yours is too black and metallic looking. So prefer the one I linked.
<nephele[m]>
x512: this is the controllook, it has nothing to do with the colors
<x512[m]>
Isn't hilight color configurable?
<nephele[m]>
tqh: not much point to me to make a dark theme if i can't use it afterwards. In any case it's harder to argue about colors if we don't have any color calibration on displays, the same colors will just look different on each others devices
<nephele[m]>
x512: button shine and window tab shine is heuristic of the controllook afaik?
<nephele[m]>
Maybe it's supposed to be the "Shine" color but that has no effect that i can see
<tqh>
nephele[m], yes, I think we should be able to have a few different themes. I mostly worry about someone wanting to restrict to one light and one dark theme.
<nephele[m]>
ThemeManager works already?
<tqh>
yes, but it's a hassle. And if we add only one dark theme, I don't have the same taste as you...
AGMS-BeOS has joined #haiku
AGMS-BeOS is now known as AGMS
<nephele[m]>
I don't care about taste that much, I'm doing this mainly because bright themese cause me pain and headaches, I don't want this functionality to deveolve into an endless discussion about which gray is the best gray :/, especailly not if we literally can't reason about this without calibrated displays. on this laptop for example stuff is too green, always. but that is not fixable with the color scheme
B2IA has quit [Quit: Vision[0.10.3]: i've been blurred!]
countryboy has left #haiku [#haiku]
Diver has joined #haiku
B2IA has joined #haiku
<tqh>
I'm not interested in the taste discussion either. We have different, and that is ok. I am more interested in what devs say about having themes in haiku itself.
<nephele[m]>
I think the consensus is pretty much to not have themes as such in haiku
<nephele[m]>
and reduce the default appearence preference settings colors to a manageable level, maybe one highlight color, maybe a second accent color or so
<nephele[m]>
and have a "default" theme for light and dark, and leave the more advanced stuff for theme manager and such
<tqh>
I think we should, you have physical problems as do color-blind so we should try to have good options.
<nephele[m]>
Personally, I think it should as far as possible work out of the box while still looking nice normally
<nephele[m]>
if we want we could always have a "higher contrast" or "reduce white point" option like for example IOS has? (though on bad days, reduce white point set to max and display brightness on 0 on iOS, is too bright for me... not much to do then)
<tqh>
I hate installing OS'es and having to spend half a day to get everything right. So I don't really want to have to find and download theme-manager find and download themes.
<tqh>
So themes takes almost no space, and we could have a selection to choose from.
<nephele[m]>
If you want a lot of customization that it what it boils down to imo, the default install should acomatade you, to a point. choice overload is the other extreme we certainly don't want i think
<nephele[m]>
to avoid a misunderstanding: what do you mean by themes in this context?
<tqh>
color scheme.
<nephele[m]>
only colors?
<tqh>
I think that probably would be enough?
<nephele[m]>
Well, in that case, I think the appearence prefs should indeed offer the most common things you'd want, but the 39 sliders we have now should definetely be more "advanced" in the theme manager or such
<tqh>
we don't really support vector backgrounds I think? :)
<nephele[m]>
I thought you were talking about themes in the sense of theme manager, as in color scheme, sound theme etc all packed into one bundle to select...
<nephele[m]>
:)
<nephele[m]>
We kinda support theoretically setting IOM or HVIF as bg and having that be converted to a bebitmap via a translator? :)
<tqh>
no, I just want it too look goot to my taste. And it is kind of flat look in dark :)
<nephele[m]>
but we don't even support transparent background pictures :(
<tqh>
good
<nephele[m]>
one suprise for me today: The digital audio on my laptop is actually working with OSS
<tqh>
I guess someone can do a good svg translator :) I havn't checked in ages though.
<tqh>
nice
countryboy has joined #haiku
Okami has quit [Remote host closed the connection]
Okami has joined #haiku
<Not-5726>
[haikuports/haikuports] korli pushed 1 commit to master [+0/-0/±2] https://git.io/JKIs7
<Not-5726>
[haikuports/haikuports] korli 5585239 - gcc: fix -fstack-protector on x86
Okami has quit [Remote host closed the connection]
jmairboeck has joined #haiku
<nephele[m]>
tqh: i looked at the screenshot again, almost 90% of the differences are because of differing rendering in the controllook, is a bikeshed there really neccesary?
<nephele[m]>
would be nice if you could atleast point out specifics rather than saying we should just do something else...
Okami has joined #haiku
ben1_ has joined #haiku
ben1_ has left #haiku [#haiku]
AGMS has quit [Quit: Vision[0.9.6-0203]: i've been blurred!]
countryboy has quit [Quit: countryboy]
HaikuUser has joined #haiku
HaikuUser has quit []
Maturion has joined #haiku
Okami has quit [Ping timeout: 480 seconds]
Babaj has quit [Quit: Leaving]
mmu_man has quit [Ping timeout: 480 seconds]
<bestonecrazy[m]>
.S.O doog a si ukiaH
<bestonecrazy[m]>
Haiku is a good O.S.
HaikuUser has joined #haiku
mmu_man has joined #haiku
jmairboeck has quit [Quit: Konversation terminated!]
<tqh>
If we decidee to only have one additional theme, it will be the only other one we are judged by.
<nephele[m]>
How is asking to throw away my work helping in any form?
<nephele[m]>
If you want to bikeshed atleast point out specifics you think are wrong and don't ask me to just copy everything from some random screenshot where the colors aren't even available in
Huggy has joined #haiku
ynhuser|828468 has joined #haiku
macdude22 has joined #haiku
KapiX has quit [Quit: KapiX]
<tqh>
I havn't asked you to throw anything away?
<tqh>
I asked in the PR what we think about having several color schemes. I just think we need to have more than two.
tqh has quit [Quit: Leaving]
macdude22 has quit [Remote host closed the connection]
HaikuUser has quit [Quit: Vision[]: i've been blurred!]
gouchi has quit [Remote host closed the connection]
skirst has joined #haiku
Maturion has quit [Remote host closed the connection]