Closed GoogleCodeExporter closed 9 years ago
Thanks for all this JCEF/CEF work and publishing this document about future
intentions.
> I would like CefBrowser to behave as much like a normal Java UI control as
possible. It should encapsulate the canvas implementation and expose
control-like functionality. Maybe we can identify an existing Java UI control
to use as a model for the interface? For example, it would be cool if it
extended Component (or similar) so that users could subclass it and override
functionality like preferred size, etc.
What you and Kai say are both true. Why not giving the end-user a widget class
that extends java.awt.Container? Internally, the Container will be filled with
a Canvas or GLCanvas based on the osr value. Canvas/GLCanvas is an
implementation detail of no particular interest to the end-user. Container is
more generic and allow us to decide what to use internally. Since it's a
Container, user can still treat this widget pretty much like a regular AWT
widget.
I know we're talking about AWT and Swing here. This approach is similar to how
the org.eclipse.swt.Browser widget is structured - it extends Composite (sort
of Container equivalent in AWT) which gives users a generic way to deal with it
while making us free to implement it however we need it to be. I was the
original committer/creator of the SWT Browser widget so I certainly have a bias
:-)
e.g.
public class ChromiumBrowser extends Container {
public ChromiumBrowser(Window parent, boolean osr) {
...
cefClient = new CefClient(clientDelegate, false, osr);
Canvas canvas = cefClient.getCanvas();
setLayout(new BorderLayout());
add(canvas, BorderLayout.CENTER);
...
}
.. other APIs to access CEF functionality
}
Thanks for any feedback, and great work pushing this out. The native window
rendering mode is so impressive by its performance.
Original comment by christop...@gmail.com
on 14 Mar 2014 at 2:41
Original comment by magreenb...@gmail.com
on 28 Mar 2014 at 10:05
Original comment by magreenb...@gmail.com
on 23 May 2014 at 6:31
Original comment by magreenb...@gmail.com
on 23 May 2014 at 6:31
All sub-issues are now complete.
Original comment by magreenb...@gmail.com
on 17 Jun 2014 at 5:36
Original issue reported on code.google.com by
magreenb...@gmail.com
on 12 Mar 2014 at 9:50