LLQtWebKit - Revision history

Oz Linden: Text replacement - "hg.secondlife.com" to "bitbucket.org/lindenlab"

2015-05-01T17:12:59Z

Text replacement - "hg.secondlife.com" to "bitbucket.org/lindenlab"

← Older revision		Revision as of 10:12, 1 May 2015
Line 9:		Line 9:

	== Browse the code ==		== Browse the code ==
	The code for LLQtWebKit is stored in a Mercurial code repository. You can browse the code [http://hg.~~secondlife.com~~/llqtwebkit/src/ here] using a Web browser.		The code for LLQtWebKit is stored in a Mercurial code repository. You can browse the code [http://bitbucket.org/lindenlab/llqtwebkit/src/ here] using a Web browser.

	Versions built with earlier editions of Qt can be found via appropriate Mercurial tags.		Versions built with earlier editions of Qt can be found via appropriate Mercurial tags.
Line 21:		Line 21:

	==== Linux ====		==== Linux ====
	The Linux version of the build instructions (in the form of a README file) can be found [http://hg.~~secondlife.com~~/llqtwebkit/src/tip/README-linux.txt here].		The Linux version of the build instructions (in the form of a README file) can be found [http://bitbucket.org/lindenlab/llqtwebkit/src/tip/README-linux.txt here].

	However, that README-linux.txt is incorrect. Since Qt 4, qmake has the Qt location hardcoded and ignores QTDIR. It is necessary to run the correct qmake (and uic) and therefore to make sure that the correct ones are found <em>first</em> in the PATH. Also, some webpages instruct one that you must set QMAKESPEC to $QTDIR/mkspecs/default.		However, that README-linux.txt is incorrect. Since Qt 4, qmake has the Qt location hardcoded and ignores QTDIR. It is necessary to run the correct qmake (and uic) and therefore to make sure that the correct ones are found <em>first</em> in the PATH. Also, some webpages instruct one that you must set QMAKESPEC to $QTDIR/mkspecs/default.
Line 36:		Line 36:

	== Test applications ==		== Test applications ==
	As well as the source code and other files required to build LLQtWebKit, there are a number of applications included in the package that are useful for testing. You can browse the code [http://hg.~~secondlife.com~~/llqtwebkit/src/tip/tests/ here]. Details of how to build them are included in the platform specific build instructions above.		As well as the source code and other files required to build LLQtWebKit, there are a number of applications included in the package that are useful for testing. You can browse the code [http://bitbucket.org/lindenlab/llqtwebkit/src/tip/tests/ here]. Details of how to build them are included in the platform specific build instructions above.

	* '''qttestapp''' - A simple Qt based, cross platform application that implements a simple Web browser		* '''qttestapp''' - A simple Qt based, cross platform application that implements a simple Web browser

Callum Linden at 00:45, 24 December 2010

2010-12-24T00:45:32Z

← Older revision		Revision as of 17:45, 23 December 2010
Line 3:		Line 3:
	LLQtWebKit is a static library that renders Web content into a memory buffer using an off-the-shelf version of the [http://qt.nokia.com/ Qt application and UI framework]. It is currently used by the most recent version of the [[Media Rendering Plugin Framework\|Media Plugin API]] to render Web content in the Second Life viewer.		LLQtWebKit is a static library that renders Web content into a memory buffer using an off-the-shelf version of the [http://qt.nokia.com/ Qt application and UI framework]. It is currently used by the most recent version of the [[Media Rendering Plugin Framework\|Media Plugin API]] to render Web content in the Second Life viewer.

	The biggest change in this version of ~~the~~ LLQtWebKit is that is can be built against an un-patched version of Qt. The patches that were present before have either been rolled into the main Qt codebase or we have found way to work around them.		The biggest change in this version of LLQtWebKit is that is can be built against an un-patched version of Qt. The patches that were present before have either been rolled into the main Qt codebase or we have found way to work around them.

	== License ==		== License ==

Callum Linden at 00:45, 24 December 2010

2010-12-24T00:45:23Z

← Older revision		Revision as of 17:45, 23 December 2010
Line 2:		Line 2:
	== Introduction ==		== Introduction ==
	LLQtWebKit is a static library that renders Web content into a memory buffer using an off-the-shelf version of the [http://qt.nokia.com/ Qt application and UI framework]. It is currently used by the most recent version of the [[Media Rendering Plugin Framework\|Media Plugin API]] to render Web content in the Second Life viewer.		LLQtWebKit is a static library that renders Web content into a memory buffer using an off-the-shelf version of the [http://qt.nokia.com/ Qt application and UI framework]. It is currently used by the most recent version of the [[Media Rendering Plugin Framework\|Media Plugin API]] to render Web content in the Second Life viewer.

			The biggest change in this version of the LLQtWebKit is that is can be built against an un-patched version of Qt. The patches that were present before have either been rolled into the main Qt codebase or we have found way to work around them.

	== License ==		== License ==

Callum Linden at 22:58, 23 December 2010

2010-12-23T22:58:43Z

← Older revision		Revision as of 15:58, 23 December 2010
Line 1:		Line 1:
			__NOTOC__
	== Introduction ==		== Introduction ==
	LLQtWebKit is a static library that renders Web content into a memory buffer using ~~code from a modified~~ version of the [http://qt.nokia.com/ Qt application and UI framework]. It is currently used by the most recent version of the [[Media Rendering Plugin Framework\|Media Plugin API]] to render Web content in the Second Life viewer.		LLQtWebKit is a static library that renders Web content into a memory buffer using an off-the-shelf version of the [http://qt.nokia.com/ Qt application and UI framework]. It is currently used by the most recent version of the [[Media Rendering Plugin Framework\|Media Plugin API]] to render Web content in the Second Life viewer.

	== License ==		== License ==
Line 7:		Line 8:
	== Browse the code ==		== Browse the code ==
	The code for LLQtWebKit is stored in a Mercurial code repository. You can browse the code [http://hg.secondlife.com/llqtwebkit/src/ here] using a Web browser.		The code for LLQtWebKit is stored in a Mercurial code repository. You can browse the code [http://hg.secondlife.com/llqtwebkit/src/ here] using a Web browser.

			Versions built with earlier editions of Qt can be found via appropriate Mercurial tags.

	== Build instructions ==		== Build instructions ==
Line 39:		Line 42:

	== Version numbers ==		== Version numbers ==
	* The version of Qt/WebKit used is: <code>4.6.0</code>		* The version of Qt/WebKit used is: <code>4.7.1</code>
	* The version of LLQtWebKit is <code>2.2</code>		* The version of LLQtWebKit is <code>2.2</code>
	* The user agent string reported by LLQtWebKit can be modified using the API but is of the form: "<code>Mozilla/5.0 (Windows;U; Windows NT 5.1; en-US) AppleWebKit/~~532~~.4+ (KHTML, like Gecko, Safari/~~532~~.4)</code>"		* The user agent string reported by LLQtWebKit can be modified using the API but is of the form: "<code>Mozilla/5.0 (Windows;U; Windows NT 6.1; en-US) AppleWebKit/533.3 (KHTML, like Gecko, Safari/533.3)</code>"

	== Previous Incarnations ==		== Previous Incarnations ==

Aleric Inglewood: /* Linux */

2010-10-05T15:01:38Z

Linux

← Older revision		Revision as of 08:01, 5 October 2010
Line 18:		Line 18:
	The Linux version of the build instructions (in the form of a README file) can be found [http://hg.secondlife.com/llqtwebkit/src/tip/README-linux.txt here].		The Linux version of the build instructions (in the form of a README file) can be found [http://hg.secondlife.com/llqtwebkit/src/tip/README-linux.txt here].

	However, that README-linux.txt is incorrect. Since Qt 4, qmake has the Qt location hardcoded and ignores QTDIR. It is necessary to run the correct qmake (and uic) and therefore to make sure that the correct ones are found first in the PATH. Also, some webpages instruct one that you must set QMAKESPEC to $QTDIR/mkspecs/default.		However, that README-linux.txt is incorrect. Since Qt 4, qmake has the Qt location hardcoded and ignores QTDIR. It is necessary to run the correct qmake (and uic) and therefore to make sure that the correct ones are found <em>first</em> in the PATH. Also, some webpages instruct one that you must set QMAKESPEC to $QTDIR/mkspecs/default.

	Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):		Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):

Aleric Inglewood: Tone down

2010-10-05T15:00:24Z

Tone down

← Older revision		Revision as of 08:00, 5 October 2010
Line 18:		Line 18:
	The Linux version of the build instructions (in the form of a README file) can be found [http://hg.secondlife.com/llqtwebkit/src/tip/README-linux.txt here].		The Linux version of the build instructions (in the form of a README file) can be found [http://hg.secondlife.com/llqtwebkit/src/tip/README-linux.txt here].

	However, that README-linux.txt is ~~horribly wrong~~.		However, that README-linux.txt is incorrect. Since Qt 4, qmake has the Qt location hardcoded and ignores QTDIR. It is necessary to run the correct qmake (and uic) and therefore to make sure that the correct ones are found first in the PATH. Also, some webpages instruct one that you must set QMAKESPEC to $QTDIR/mkspecs/default.
	~~For a start,~~ Qt 4 ~~doesn't care about QTDIR.~~ qmake has the Qt location hardcoded. ~~So, telling people~~ to ~~do add $QTDIR/bin at~~ the ~~end~~ of the PATH ~~isn't going to work~~. ~~They also forget to mention~~ that you must set QMAKESPEC to $QTDIR/mkspecs/default~~. Moreover, on some operating systems (debian, ubuntu) 'uic' is a symbolic link to the Qt 3 version~~.

	Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):		Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):
Line 29:		Line 28:
	</pre>		</pre>

	And then continue as instructed (<code>which qmake</code> and <code>which uic</code> now show a binary in your QTDIR).		And then continue as instructed (<code>which qmake</code> and <code>which uic</code> now should show a binary in your QTDIR).

	== Test applications ==		== Test applications ==

Aleric Inglewood: /* Linux */

2010-10-05T14:55:23Z

Linux

← Older revision		Revision as of 07:55, 5 October 2010
Line 23:		Line 23:
	Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):		Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):

	<~~code~~>		<pre>
	export QTDIR=/usr/local/Trolltech/Qt-4.6.0		export QTDIR=/usr/local/Trolltech/Qt-4.6.0
	export PATH=$QTDIR/bin:$PATH		export PATH=$QTDIR/bin:$PATH
	export QMAKESPEC=$QTDIR/mkspecs/default		export QMAKESPEC=$QTDIR/mkspecs/default
	</~~code~~>		</pre>

	And then continue as instructed (<code>which qmake</code> and <code>which uic</code> now show a binary in your QTDIR).		And then continue as instructed (<code>which qmake</code> and <code>which uic</code> now show a binary in your QTDIR).

Aleric Inglewood: /* Linux */

2010-10-05T14:54:54Z

Linux

← Older revision		Revision as of 07:54, 5 October 2010
Line 23:		Line 23:
	Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):		Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):

	[code]		<code>
	export QTDIR=/usr/local/Trolltech/Qt-4.6.0		export QTDIR=/usr/local/Trolltech/Qt-4.6.0
	export PATH=$QTDIR/bin:$PATH		export PATH=$QTDIR/bin:$PATH
	export QMAKESPEC=$QTDIR/mkspecs/default		export QMAKESPEC=$QTDIR/mkspecs/default
	[code]		</code>

	And then continue as instructed ([code]which qmake[code] and [code]which uic[code] now show a binary in your QTDIR).		And then continue as instructed (<code>which qmake</code> and <code>which uic</code> now show a binary in your QTDIR).

	== Test applications ==		== Test applications ==

Aleric Inglewood: /* Linux */

2010-10-05T14:53:51Z

Linux

← Older revision		Revision as of 07:53, 5 October 2010
Line 23:		Line 23:
	Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):		Hence, correct instructions are (change '4.6.0' as appropriate for your Qt version):

			[code]
	export QTDIR=/usr/local/Trolltech/Qt-4.6.0		export QTDIR=/usr/local/Trolltech/Qt-4.6.0
	export PATH=$QTDIR/bin:$PATH		export PATH=$QTDIR/bin:$PATH
	export QMAKESPEC=$QTDIR/mkspecs/default		export QMAKESPEC=$QTDIR/mkspecs/default
			[code]

	And then continue as instructed ([code]which qmake[code] and [code]which uic[code] now show a binary in your QTDIR).		And then continue as instructed ([code]which qmake[code] and [code]which uic[code] now show a binary in your QTDIR).

Aleric Inglewood: Add fix for environment variables.

2010-10-05T14:52:39Z

Add fix for environment variables.

@@ Line 17: / Line 17: @@
 ==== Linux ====
 The Linux version of the build instructions (in the form of a README file) can be found [http://hg.secondlife.com/llqtwebkit/src/tip/README-linux.txt here].
 == Test applications ==