Hi Adam,
On Jul 16, 2007, at 9:52 AM, Adam Roben wrote:
[snip]
I think there are probably two approaches to implement it:
1.) Have one GdkWindow for the main Frame of the Page
+ Resource friendly
+ z-order would always be right
- Scrolling would need to be manually handled by
On Jul 16, 2007, at 10:28 AM, Holger Freyther wrote:
Am 16.07.2007 um 18:52 schrieb Adam Roben:
Answers and pointers to manual Frame tests would be appreciated.
I'm tempted to go with the 2nd option.
I think you'll have a much easier time getting things right in
the end if you go wit
Am 16.07.2007 um 18:52 schrieb Adam Roben:
Answers and pointers to manual Frame tests would be appreciated.
I'm tempted to go with the 2nd option.
I think you'll have a much easier time getting things right in
the end if you go with the first option (one native widget
(GdkWindow) p
On Jul 16, 2007, at 1:59 AM, Holger Freyther wrote:
-Each Page has one main Frame?
Yes.
-Each Frame has a FrameView? Is that mandantory or should the
FrameView only be created when FrameLoaderClient::makeDocumentView
is getting called?
Yes. In the Windows implementation,
Hi,
the most grave issues in the Gdk/Gtk port are resolved and I would
like to implement FrameLoaderClientGdk::createFrame and have a couple
of questions.
To get the cardinalities right could you confirm that:
-Each Page has one main Frame?
-Each Frame has a FrameView? Is that man
5 matches
Mail list logo
