50
edits
Canvas news: Difference between revisions
Jump to navigation
Jump to search
m
→Skia talks: fix small typo
m (→PUI Emulation) |
m (→Skia talks: fix small typo) |
||
| Line 858: | Line 858: | ||
}}</ref> | }}</ref> | ||
After reviewing Skia (including reading the sources) and it seems like a very promising fit, albeit with the caveat that it is kind of huge. Blend2D looks pretty good but less mature than Skia, and most importantly, lacks a hardware renderer which James thinks is critical to support devices such as the Raspberry Pi and cheap Android tablets, which James expects to be a very good target for the remote canvas (an RPi driving a wide-screen panel via HDMI could do both the PFD and ND of a Boeing/Airbus setup, but that’s 1920 x 1080 pixels which is too much to fill in software at | After reviewing Skia (including reading the sources) and it seems like a very promising fit, albeit with the caveat that it is kind of huge. Blend2D looks pretty good but less mature than Skia, and most importantly, lacks a hardware renderer which James thinks is critical to support devices such as the Raspberry Pi and cheap Android tablets, which James expects to be a very good target for the remote canvas (an RPi driving a wide-screen panel via HDMI could do both the PFD and ND of a Boeing/Airbus setup, but that’s 1920 x 1080 pixels which is too much to fill in software at 60Hz) Anyway, at this point the code is small enough that experimenting with one renderer or another (Cairo also) is probably a weekend’s hacking, if anyone cared to try. James is currently working on hardware acceleration using QtQuick, since we already have Qt as a dependency.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/35631079/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35631079/ | ||
|title = <nowiki> Re: [Flightgear-devel] Canvas-svg </nowiki> | |title = <nowiki> Re: [Flightgear-devel] Canvas-svg </nowiki> | ||