Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt WebKit
  4. Accessing complete tree, not just elements.
Forum Updated to NodeBB v4.3 + New Features

Accessing complete tree, not just elements.

Scheduled Pinned Locked Moved Qt WebKit
1 Posts 1 Posters 1.8k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    TimS
    wrote on last edited by
    #1

    I don't know the thinking that went into the design of the QtWebKit interface, but not being able to do the following really limits its usefulness:

    • Can't access nodes, only elements
    • Can't (easily) get the QWebFrame for an iframe/frame element

    I need to traverse the DOM tree and access everything, which means I need access to underlying WebCore classes.
    A few posts exist on accessing WebCore from a Qt project, but they don't work on my 4.8.0/MSVC2010 system as I get unresolved external symbol errors on linking. Linking against JSCore.lib results in duplicate symbol errors.

    Anyone got a proven method for doing this? I'm not a C++ man so hit the limits on figuring out what to do.
    At the moment I'm adding additional methods to QWebPage and compiled up my own QtWebKit.dll to do what I need, but would prefer not to.

    Thanks for any assistance, I really like Qt otherwise (coming from a .NET man)

    1 Reply Last reply
    0

    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt Extensions
    • Unsolved