Additionnal libraries on the repo

[macman31]

Do we allow optional libraries that are not required to run the kernel but that can be helpfull for some tasks on the repo ?
For example, I felt free to post my graphic library, LibPixel there, but I don't know if you guys are OK with that.

[dilbertfan]

Well, OSes based on entropy might use them, so I think it's fine

[ColErr]

I think making sure they are compatible, and distributing them with the kernel is fine, as long as we aren't compiling it with all these extra libs.

[M52]

Precisely. I think OS developers are going to love us for providing extra functionality that works very well with the OS, they can just add that library without having to code anything themselves. However, if they don't want to and just want to use the core kernel, then that is possible too.

I really like the way this is heading!

[M52]

Oh and by the way, LibPixel allows for drawing of pixels?

Using a modified font? (and using inversion I presume)?

[macman31]

Yes, yes, yes (for the "set" of the bottom right pixel).
(If you are interested on how it works and what it can do, well there is that huge header in LibPixel with example code of the usage of kinda every LibPixel functs.)
btw it only allow a 64_48 display area, so in fact one "pixel" is a swuare of 2_2 LEM pixels. But except that, it totally work, allow the user to display "saved" picts, and have color support (with some limitations).
I'll need someome to help me to create a "drawing for LibPixel" Java program to allow the user to create pictures that will be able to be loaded with LibPixel to be shown on the DCPU. Someone here to help me with that Java program ? =)

[Kibble]

Why not a Java program that takes a standard image format and converts it to LibPixel format? Saves the trouble of writing a whole image editing program.

[macman31]

Because you can't do what you want : LibPixel have strict limitations (for example, you can only have two "colors" for each 2_4 pixels (4_8 screen pixels, LEM limitation :/)
And the color palette is very strict too, and there will be tools such as "line drawing" that will only take two word on the save file (start and end), instead of one word for each line pixel, and you can't detect that with an image conversion tool.

[viccuad]

I don't like putting libraries that are not going to be used by the kernel when compiling it here. many reasons:

• if someone new looks at the repo, they dont know which is the kernel and which is not.
• it can be missunderstood, and someone can take that library to be used in the kernel. (example, having 2 float lib, one stripped and another not stripped)
• it bloats the repo. harder to find or know what needs to be improved or fixed.
• if someone from an OS wants extra functionality, let them take the library from another repo, add it to their OS, and they aren't coding anything themselves. I don't see any problem with this. remember, the kernel was going to be done for the community, not with an OS in mind.

in my opinion, if you want to put additional and not used libraries by the kernel here, you would be better making a git repo storing all your libraries. you have all the beneficts, and none of the things i said right here.