capybara-webkit/src/webkit_server.pro

TEMPLATE = app
TARGET = webkit_server
DESTDIR = .
HEADERS = WebPage.h Server.h Connection.h Command.h Visit.h Find.h Reset.h Node.h JavascriptInvocation.h Url.h Source.h Evaluate.h Execute.h FrameFocus.h
SOURCES = main.cpp WebPage.cpp Server.cpp Connection.cpp Command.cpp Visit.cpp Find.cpp Reset.cpp Node.cpp JavascriptInvocation.cpp Url.cpp Source.cpp Evaluate.cpp Execute.cpp FrameFocus.cpp
RESOURCES = webkit_server.qrc
QT += network webkit
CONFIG += console
Initial commit 2011-02-19 03:53:06 +00:00			`TEMPLATE = app`
			`TARGET = webkit_server`
			`DESTDIR = .`
Working on frame handling. In terms of the QT code, the non-frame-related specs pass with these changes (e.g. mainFrame() => currentFrame() and the new injectJavascriptHelpers() code in WebPage.cpp). It seems like the current JS+xpath implementation dives in to iframes already. Is this desired behavior? I wonder if that works with x-domain iframes? I doubt it... Also, this design assumes that we only step one frame down at a time... Lastly, I'm really not sure how QWebKit decides which frame is currentFrame(). For now, I'm hoping to be able to use the QWebFrame setFocus() method. This may be a dead end though. We may have to have WebPage manually keep track of the "current" frame. 2011-04-19 07:16:25 +00:00			`HEADERS = WebPage.h Server.h Connection.h Command.h Visit.h Find.h Reset.h Node.h JavascriptInvocation.h Url.h Source.h Evaluate.h Execute.h FrameFocus.h`
			`SOURCES = main.cpp WebPage.cpp Server.cpp Connection.cpp Command.cpp Visit.cpp Find.cpp Reset.cpp Node.cpp JavascriptInvocation.cpp Url.cpp Source.cpp Evaluate.cpp Execute.cpp FrameFocus.cpp`
Moved Javascript code into a .js file that gets loaded into each page 2011-02-26 03:32:22 +00:00			`RESOURCES = webkit_server.qrc`
Initial commit 2011-02-19 03:53:06 +00:00			`QT += network webkit`
Moved Javascript code into a .js file that gets loaded into each page 2011-02-26 03:32:22 +00:00			`CONFIG += console`
Initial commit 2011-02-19 03:53:06 +00:00