Difference between revisions of "User:Vladbogolin/GSoC2014/Logs"
From BRL-CAD
Vladbogolin (talk | contribs) (→Week 2) |
Vladbogolin (talk | contribs) (→Week 2) |
||
Line 52: | Line 52: | ||
*31 May: | *31 May: | ||
**Mostly a break day. | **Mostly a break day. | ||
+ | *1 June: | ||
+ | **Break day. | ||
+ | |||
+ | ==Week 3== | ||
+ | *Weekly milestone: | ||
+ | **Finish implementing open/close and start working at the write function. | ||
+ | *2 June: | ||
+ | **Continued working at the open function: created an empty window - the function should be done tomorrow. |
Revision as of 15:05, 2 June 2014
Contents
Daily Progress
Project Info
Project Name | Embedding a framebuffer window |
Student Name | Bogolin Simion Vlad |
IRC nick | vladbogo |
Link to proposal | http://brlcad.org/wiki/User:Vladbogolin/Proposal/EmbeddingFrameBuffer |
Milestones
- Implementing a new Qt framebuffer
- Raytracing
- Embedding a framebuffer window
Logs
Community Bonding
- Studied the existing framebuffer implementation
- Researched to see exactly what framebuffer functions are called when using the rt command
Week 1
- Weekly milestone:
- Start working at the "open" function.
- 19 May:
- Started creating a new Qt framebuffer: I started by creating a txt framebuffer that just logs function calls.
- 20 May:
- Mostly a break day
- 21 May - 25 May:
- In this interval I had my final exams
Week 2
- Weekly milestone:
- Make up for the lost time due to exams
- Implement the open/close functions
- 26 May:
- I had my last exam so from now on I will focus on the project.
- Worked a little bit more on the txt framebuffer
- 27 May:
- Worked at attaching the txt framebuffer to the display manager - the txt framebuffer is almost done.
- Studied the existing "open" functions.
- 28 May:
- Attached the qt framebuffer to the display manager.
- Started working at the "open" function.
- 29 May:
- Continued working at the "open" function - it should be done shortly
- 30 May:
- Researched how the raytracer uses the framebuffer and attached the new framebuffer to it.
- 31 May:
- Mostly a break day.
- 1 June:
- Break day.
Week 3
- Weekly milestone:
- Finish implementing open/close and start working at the write function.
- 2 June:
- Continued working at the open function: created an empty window - the function should be done tomorrow.