1. 17 Jun, 2013 - 1 commit
  2. 12 Jun, 2013 - 1 commit
  3. 11 Jun, 2013 - 1 commit
  4. 06 Jun, 2013 - 1 commit
    • Jocelyn Turcotte's avatar
      Properly implement a QWidget and QtQuick API · 5bf14ccc
      Jocelyn Turcotte authored
      This layers things properly to be able to implement the UI in the
      example application instead of directly in shell_qt.cpp.
      
      This is still using global variables to allow the Shell platform
      code to do callbacks to the API classes. This should go away once
      we properly implemented a WebContentsDelegate.
      5bf14ccc
  5. 05 Jun, 2013 - 1 commit
    • Zeno Albisser's avatar
      Implement support for QtQuick2. · db4b7526
      Zeno Albisser authored
      The current preliminary implementation uses the QQuickPaintedItem.
      
      The RasterWindow is being replaced by an abstract NativeViewQt
      class, which can be instantiated as QWidgetNativeView or QQuickNativeView.
      The NativeViewContainerQt builds a wrapper around an instance of these classes
      and serves as a common api towards chromium.
      
      Due to the current design where the view is being created by the shell,
      we introduce a browser_window.qml which provides a very basic browser UI.
      The content is then being injected into an item within that browser window.
      
      Just executing the example the "regular" way will launch the Widgets example.
      To launch the QtQuick2 example, the environment variable QQUICKWEBENGINE must
      be defined.
      db4b7526