summaryrefslogtreecommitdiff
path: root/shared
Commit message (Collapse)AuthorAgeFilesLines
* Get rid of the intermediate "shared" static library.Jocelyn Turcotte2013-11-214-380/+0
| | | | | | | | It is not necessary anymore since QtWebEngineProcess dynamically links to the core library which will now contain those symbols. Change-Id: I3475347bab41a00b943f934a5e341326c66dc726 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Use our own implementation of GetDefaultXDisplay.Jocelyn Turcotte2013-11-112-0/+25
| | | | | | | | This allows the Chromium GL code to initialize on the display created by Qt. Change-Id: I3d21f56c3792d6e99cb94690f56d7dd5c542045a Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* QtWebEngine Dev Tools (Web Inspector)Chris Hutten-Czapski2013-10-291-6/+13
| | | | | | | | | | | | | | | | | | To implement the Web Inspector we need a delegate to handle the http server and devtools connections, a landing page, a ContentClient to tell the devtools server where to find its frontend resources, those frontend resources, and an API for embedders to turn on inspectability in WebEngineViews. The frontend resources are build by the chromium build and are copied over as part of lib's build. The landing page was taken directly from content_shell. This should be replaced by either a new one for all QtWebEngine embedders or by a mechanism for embedders to supply their own (or both). Change-Id: Id4076d5ede34a91abf8dba443aed4dca4be1b3e5 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Return the physical screen's geometryPierre Rossi2013-10-241-2/+2
| | | | | | | | | This is exposed through JS, and sometimes used to center popups and so on. Exposing the virtual geometry in the case of multi-screen setups can lead to quirky behavior. Change-Id: I4fe395dd2a19e5c96d79a33ed6ca08bed9e3d086 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Mac: INCLUDEPATH fixPierre Rossi2013-10-111-0/+3
| | | | | | | | Something seems to be busted with 5.2 lately. Specifically on Mac. Work around the problem for now. Change-Id: I4180257f31e67d02d46e26808e8b044f3b0c0cd2 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Do not forward declare OBJC types.Zeno Albisser2013-10-111-1/+2
| | | | | | | | | | We have to disable forward declaration of objective-c types in Qt when building chromium code. Chromium does have different, incompatible forward declarations. Change-Id: Ib7f7e9839e5c85d758d1e5bb921e67c57a55c4ef Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Add Qt namespace macros QtWebEngine classes.Michael Brüning2013-09-171-0/+3
| | | | | | This should enable namespaced builds of Qt and QtWebEngine. Change-Id: I4c9d506d864b42a346026b980dcf3777b9680957 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Centralize type conversion functions.Jocelyn Turcotte2013-08-202-20/+5
| | | | | | | | | | | | | This adds the common GURL->QUrl and string16->QString conversions into a common header and use those functions throughout the code. Move the qStringToStringType into the same header and rename it to a name consistent with the others. This also cleans up shared_globals.h by moving content:: forward declarations in the cpp, where they are used. Change-Id: I19527ea7de1f6047aae8b44c97eb4d7c3e5a0e54 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Fix the debug build.Jocelyn Turcotte2013-07-292-0/+164
| | | | | | | | | Move resource_bundle_qt.cpp to the shared lib since the process also needs its symbols. The qrc file should normally follow, but Windows doesn't support them in static files, so keep them separated until it's a problem. Change-Id: I4963e4609592df90126f8b8a18a4d368907f205f Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Fix BrowserContextQt::GetPath() to return path to user data directoryAndras Becsi2013-07-261-0/+21
| | | | | | | | | Besides returning a proper application specific user data directory, this patch removes the duplicate definition of GetPath() which was added by accident with the recent chromium update. Change-Id: Ia30d598e3ef99eb88000498ef3a00ccae0593ff8 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Fix linking of QtWebEngineProcessAndras Becsi2013-07-042-0/+13
| | | | | | | | | | | | | | Since the global factory function content::CreateWebContentsView is also needed by the web process and we exclude all implementations we have to place the definition of it in the shared static lib. However, to prevent the need for moving platform layer classes back to the shared static lib we have to revert back to use ContentBrowserClient::OverrideCreateWebContentsView in the API layer to create our platform WebContentsViewQt and make the global factory function definition empty. Change-Id: I9d46524b22458b26a043c80df02b4a5fa7d91a55 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Fix the build without c++11Andras Becsi2013-06-281-2/+2
| | | | | | | Use NULL instead of nullptr. Change-Id: I3294cecdc13054011f036a7645d5f97d23f71e0b Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* CreateViewForWidget must return a value.Zeno Albisser2013-06-271-0/+1
| | | | | Change-Id: I4057758500b01ba3b55f7521c9b6384f94ed4255 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Fix build with ToTAndras Becsi2013-06-241-1/+1
|
* Fix the build.Jocelyn Turcotte2013-06-192-6/+2
|
* Move API layer-only classes back from the shared static lib.Jocelyn Turcotte2013-06-199-1520/+4
| | | | | | | Since ContentBrowserClientQt::OverrideCreateWebContentsView now takes care of using our Qt layer at runtime without relying on the static RenderWidgetHostView::CreateViewForWidget, we can now avoid linking this layer into the render process.
* Move symbols that we left out from the Chromium build in a separate file.Jocelyn Turcotte2013-06-194-31/+138
|
* Simplify the BackingStore handling.Jocelyn Turcotte2013-06-195-65/+16
| | | | | | | | | | | | | This patch removes the black borders around the widget when resizing. - No need to resize the BackingStore direcly, RenderWidgetHostImpl::WasResized takes care of allocating a new one with the correct size. - Get the backing store just before painting instead of pushing it when scheduling an update. Getting the backing store has side effects that assumes it is done that way. - Remove the about_to_validate_and_paint_ check as all our painting updates are scheduled back to the event loop and that we are now only fetching the BackingStore at this point.
* Allow the API class to provide the page widget rendering implementation.Jocelyn Turcotte2013-06-197-462/+51
| | | | | | | - Rename NativeViewQt to RenderWidgetHostViewQtDelegate to keep the context obvious. - Use an interface to handle the parenting instead of the NativeViewContainerQt mechanism that was needed with the Shell.
* Make logging of unimplemented functions optionalPierre Rossi2013-06-191-0/+5
| | | | | Can be enabled easily by adding this line to one's ~/.gyp/include.gypi file: 'defines': [ 'QT_WEBENGINE_LOGGING', ],
* Notify the NativeViewContainer when the QQuickNativeView is being destroyed.Zeno Albisser2013-06-181-1/+6
|
* cleaner content margins for the nested layoutsPierre Rossi2013-06-181-3/+7
| | | | also remove QQUICKWEBENGINE env var
* Quick cleanup.Jocelyn Turcotte2013-06-122-12/+0
|
* Start simplifying WebContentsDelegateQtPierre Rossi2013-06-121-1/+1
| | | | Mostly removing duplicated code so far.
* Remove obsolete RasterWindow.Zeno Albisser2013-06-122-194/+0
|
* Rename remaining references of blinq to QtWebEngine.Jocelyn Turcotte2013-06-111-3/+3
|
* Fix an assert in RenderWidgetHostImpl::GetBackingStore.Jocelyn Turcotte2013-06-104-14/+37
| | | | Also carry the damaged rect to QWidget|QPaintedItem::update.
* Fix undefined symbols in debug builds.Jocelyn Turcotte2013-06-1012-0/+2199
process uses the same code as lib and decides at runtime which code to run. Fix the debug build by making sure that all infrastructure code is available in both process and lib by building common code not shared directly through chromium sources in a separate static lib.
View Lorry Controller Status