I've left things open for the server to live in the kernel if you want it to. If not, that will also very easily work under the new memory/filesystem managers I've been planning. They more or less give interfaces really freaking hard-to-use control over memory and filesystem efficiency. It's really easy for applications to use the features though, as all they have to do is send information/requests to the interface and let it handle them (ignore, modify, or pass along to kernel after determining priority).
If you decide the server should drop into the kernel, then I'd suggest putting the font rendering code there -- I assume you'd want to support anti-aliasing and all, and that could be done quickest in the kernel. It would also help to have a single basic font defined in the server as well, for use while booting.
Anyway, it looks awesome so far. Especially for ~870loc.
Comments 1
If you decide the server should drop into the kernel, then I'd suggest putting the font rendering code there -- I assume you'd want to support anti-aliasing and all, and that could be done quickest in the kernel. It would also help to have a single basic font defined in the server as well, for use while booting.
Anyway, it looks awesome so far. Especially for ~870loc.
Reply
Leave a comment