Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
As for applications there are many applications that you will not find in the current official KolibriOS distribution. For example an excellent image viewer ZSea, new videoplayer FPlay, Fast Fourier Transform, FLI player, Planet viewer, alternative text editor and many other.
I also work on a flash player for KolibriOS and driver for High Definition Audio, so you can ask any questions on these areas or otherwise give me advises. Any help is greatly appreciated.
iLewis
Very good! As I read on your site, you've ported MESA to your OS. Does it support hardware acceleration? How you did it?
Its not really 8fps thats just the refresh count, this is an old screenshot now. My Shell runs with MESA as the backend now which i got ported yesterday. and it renders a a little faster than Lighthouse3D which drew the above image. It gets about 15fps in VMWare on 1 core, drawing the same cube, but poly smoothing and lighting work so...
here's a current screenshot of my humble little realmode multitasker OS.
i tested it on an old (REALLY OLD) 8088 laptop i still have with dual 720 KB drives and 640 KB of RAM. a Datavue Spark. what a beast! it works fine on there too. the OS supports multiple virtual terminals. you can switch between them with ctrl-alt-f# like *NIX.
When I see all those OS with a pretty GUI, maybe with alpha channel support, or a video player I get quite nervous... You should be using VBE right? So no 2D acceleration and such. You have to draw/move/fade/whatever the pixels "by hand". How many FPS can you get? How do you get to a decent FPS rate to see a movie, while the CPU is working on decoding the file?
Once I developed a GUI using double-buffering with SSE2 to speed-up move and copy operations.
I couldn't get more than 20 FPS on most emulators, and if I used the alpha channel too, things were too bad to be said here...
Maybe your GUI uses more than one core so the working is easier?
Any other tricks?
Please, correct my English...
Motherboard: ASUS Rampage II Extreme
CPU: Core i7 950 @ 3.06 GHz OC at 3.6 GHz
RAM: 4 GB 1600 MHz DDR3
Video: nVidia GeForce 210 GTS... it sucks...
We finally got generic interfaces working in our compiler! Only thing left to do with regard to generics are generic methods. Generic interfaces, types and classes are working. Next thing on the list would be exception handling and we're ready to go for version 1.0
(PS: Ignore the CPU info...somehow virtualbox contains wrong smbios tables on osx)
rootnode wrote:(image)
We finally got generic interfaces working in our compiler! Only thing left to do with regard to generics are generic methods. Generic interfaces, types and classes are working. Next thing on the list would be exception handling and we're ready to go for version 1.0
(PS: Ignore the CPU info...somehow virtualbox contains wrong smbios tables on osx)
Synon wrote:
I really like the borders, how did you do that?
The borders are made by Mac OS X ! What you see is Mosa OS running in VirtualBox.
I'm sure Synon meant the ascii border characters on your OS screen.
Yeah, I meant that, not the window border.
Kevin wrote:
Synon wrote:I really like the borders, how did you do that?
Have a look at the Codepage 437 character set, and I'm sure you'll figure out.
I've seen some of these characters before (mostly by accident). What I wanted to know specifically (and really, I should have been more specific) is how he implemented it, i.e., is the screen divided up (like what you can do with ncurses) or did he just draw the borders?
Thanks for that page, though, I didn't know what that set of characters was called or anything about it, I'd only ever seen it by accident.
Synon wrote:What I wanted to know specifically (and really, I should have been more specific) is how he implemented it, i.e., is the screen divided up (like what you can do with ncurses) or did he just draw the borders?
Its been a while, so, here is Xero MaLux v 0.2.0 in all its half arsed glory:
I recently tried a mouse driver, however it hangs the shell. It seems to be the QEMU setup, because my dev partner has no trouble using it. Any ideas?
That was off topic, sorry. Though still relevant, and why not hit 2 birds with 1 stone? After I get the mouse driver working, I will rewrite the shell to use the message proc abilities of the kernel (it was originally wrote before this came about), and then ACPI support. Enjoy.
(I may upload some hard drive images in the future... let me know if you want...)