U++ framework: U++ Developers corner » Rainbow Framebuffer

Home » Developing U++ » U++ Developers corner » Rainbow Framebuffer - theide running

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Rainbow Framebuffer - theide running [message #33285]

Fri, 22 July 2011 15:44

mirek
Messages: 14290
Registered: November 2005

Ultimate Member

TheIDE running on framebuffer backend:

index.php?t=getfile&id=3390&private=0

Attachment: Clipboard01.png
(Size: 219.23KB, Downloaded 714 times)

Report message to a moderator

Re: Rainbow Framebuffer - theide running [message #33286 is a reply to message #33285]

Fri, 22 July 2011 15:54

cbpporter
Messages: 1428
Registered: September 2007

Ultimate Contributor

Wow!

Great!

I brought up the subject of window borders (simulating windows on a flat drawing canvas) and the support Rainbow has for this. I didn't quite understand the details of this, so now is a good time to ask again. I see that the windows have titlebars and buttons. These are managed by the specific Rainbow backend, in this case WinFB? There is code in the backend to draw window borders and handle mouse events on these borders? Simulating what normally is done by Windows or X11?

Report message to a moderator

Re: Rainbow Framebuffer - theide running [message #33292 is a reply to message #33286]

Fri, 22 July 2011 19:46

mirek
Messages: 14290
Registered: November 2005

Ultimate Member

cbpporter wrote on Fri, 22 July 2011 09:54

Yes.

Quote:

There is code in the backend to draw window borders and handle mouse events on these borders? Simulating what normally is done by Windows or X11?

Exactly. Now, it is possible that if ever FB is used for embedded devices, all of this effort is a little bit overkill, as I think that on embedded, there will be no windows.

But FB is also "proof of concept" for rainbow. So I wanted to have it complete...

NOTE: Implementation-wise, those window borders are somewhat hacked solution - FB Ctrl code basically implements borderless windows with owners and TopWindow is implemented as "sort of" owned (only for internal implementation) by TopWindowFrame (but it is not visible outside of Framebuffer Ctrl implementation).

Report message to a moderator

Previous Topic:	Porting Upp to SDL first ? (cause of MacOSX & framebuffer)
Next Topic:	Docking

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Apr 27 13:57:09 GMT+2 2026

Total time taken to generate the page: 0.00906 seconds