Editing New Cross-Platform 2D Framebuffer
From BRL-CAD
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| + | ==Cross Platform Framebuffer== | ||
| + | |||
BRL-CAD displays its raytracing output as it is generated by using a framebuffer. Currently BRL-CAD has specific framebuffers for X11 Opengl (ogl), Windows OpenGL (wgl), and raw X11 (X), in addition to a variety of more special purpose and experimental framebuffers. A single, high performance, cross platform framebuffer is of interest to BRL-CAD. | BRL-CAD displays its raytracing output as it is generated by using a framebuffer. Currently BRL-CAD has specific framebuffers for X11 Opengl (ogl), Windows OpenGL (wgl), and raw X11 (X), in addition to a variety of more special purpose and experimental framebuffers. A single, high performance, cross platform framebuffer is of interest to BRL-CAD. | ||
| − | This task, | + | This task, rather than being specific to Qt or OGRE, would invite suggestions for a cross platform framebuffer implementation - either utilizing existing, license compatible open source code or writing from scratch. A possible candidate would be the pxCore library: http://code.google.com/p/pxcore/ |
| − | + | Distinct from the Qt framebuffer, a custom solution would ideally be implemented in such a way that it can be embedded into a Tk window and be a "drop in replacement" for existing graphical framebuffers on multiple platforms. | |
# Review current framebuffer code and related code (in particular, isst) to identify features needed for a framebuffer | # Review current framebuffer code and related code (in particular, isst) to identify features needed for a framebuffer | ||
| − | # Identify approach ( | + | # Identify approach (pxCore, all custom code, etc) |
# Implement working code, including: | # Implement working code, including: | ||
#*per-scan-line drawing - display update should not have to wait for a completed raytrace | #*per-scan-line drawing - display update should not have to wait for a completed raytrace | ||
| Line 16: | Line 18: | ||
A good proposal for this task will need to spell out a fair number of specifics and should do some homework - "research and implement framebuffer code" would be a weak submission. The X11 framebuffer (if_X24.c) would be good code to review when developing a proposal for this task. | A good proposal for this task will need to spell out a fair number of specifics and should do some homework - "research and implement framebuffer code" would be a weak submission. The X11 framebuffer (if_X24.c) would be good code to review when developing a proposal for this task. | ||
| − | + | Requirements: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
*Familiarity with C and C++ | *Familiarity with C and C++ | ||
*(optional) Familiarity with cross platform graphical drawing APIs and issues | *(optional) Familiarity with cross platform graphical drawing APIs and issues | ||
| + | |||
| + | Difficulty: low/medium | ||
