561
edits
Difference between revisions of "Talk:OpenTasks"
Some thoughts about the "Improve overlay API" task
(→Recorded Play: -- my response) |
(Some thoughts about the "Improve overlay API" task) |
||
| Line 56: | Line 56: | ||
That should not be possible with our current overlay code, where you either have the overlay visible and usable OR the game graphics visible and usable. So until this is changed, I would abstain from adding it as a task goal. Of course it would be really nice to have that, but I guess letting the guy worrying about our overlay code too, seems a bit too much :-). --[[User:LordHoto|LordHoto]] 18:11, 4 February 2009 (CEST) | That should not be possible with our current overlay code, where you either have the overlay visible and usable OR the game graphics visible and usable. So until this is changed, I would abstain from adding it as a task goal. Of course it would be really nice to have that, but I guess letting the guy worrying about our overlay code too, seems a bit too much :-). --[[User:LordHoto|LordHoto]] 18:11, 4 February 2009 (CEST) | ||
:Yeah, I completely agree. I altered wording a bit --[[User:Sev|Sev]] 22:18, 9 February 2009 (UTC) | :Yeah, I completely agree. I altered wording a bit --[[User:Sev|Sev]] 22:18, 9 February 2009 (UTC) | ||
== Improve the overlay API == | |||
Seeing that some of the ideas there are implemented in our current trunk, it might come into consideration to remove this task. At least we have Graphics::PixelFormat, the OSystem addition and partly changed our code to use that now. Another alternative would be to change the task to allow for example use of overlay and game graphics at the same time, which might for example be useful for our vkbd, except we now decide to change the vkbd API, so all backends have to invoke vkbd handling directly. Apart I think that what is left of the task is too small for an fulltime GSoC project. | |||
--[[User:LordHoto|LordHoto]] 17:21, 15 Feburary 2008 (CEST) | |||