On 23/02/12 20:29, Fredrik Holmqvist wrote:
Den 23 februari 2012 20:41 skrev Simon Taylor<simontaylor1@xxxxxxxxxxxx>:There is some BeOS backend code in the current cairo, but it only implements conversion from BBitmap to cairo's image surfaces. None of the drawing functions are implemented with BeAPI (but as is hopefully clear, I don't think we want to implement them anyway).How do you plan to show the cairo_surface on screen?
Some conversion to BBitmap to prove the concept, potentially some optimised path to app_server later on.
Are you going to rewrite the haiku widget code in Firefox, or are you going to blit over the image on each gfx op?
I'm not quite sure on some of it yet. I believe FF implements the widget behaviour itself, and the appearance is all the platform needs to provide (necessary so the browser can layer them correctly with other web content). Back in the day I was briefly listed on the Bezilla BeBits build as part of the team (tb100), although I never really contributed anything. The few lines to show the BeOS icons in the download window came from me though; so I did at least have some idea of my way around the code as it was 10 years ago.
It's going to be horrible. Even when scrolling and resizing in Firefox now as little as possible is invalidated and as much as possible is blitted. It's already slow enugh, Doing a lot more lifting in the redrawing isn't much of an option. You might as well just get X working on Haiku.
There's no hardware blitting used on Haiku anyway, but I'd certainly aim to memcpy the surface bitmap rather than re-rendering the whole thing.
/Fredrik Holmqvist,TQH
