Qt4 Hildon Legacy - Revision history

amigadave: add Qt syntax highlighting, use


amigadave — Wed, 09 Mar 2011 12:08:17 GMT
add Qt syntax highlighting, use <code>

		
		
		
		
		
		
		← Older revision
		Revision as of 12:08, 9 March 2011
		
		Line 110:
Line 110:
 Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives, for example with Qt 4.5 on Diablo and Fremantle:  Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives, for example with Qt 4.5 on Diablo and Fremantle:
  
- <source lang="cpp"> + <source lang="cpp-qt">
 #ifdef Q_WS_HILDON  #ifdef Q_WS_HILDON
     //Specific hildon/Maemo5 code here        //Specific hildon/Maemo5 code here  
Line 197:
Line 197:
  
 A developer can change it by using:  A developer can change it by using:
- <source lang="cpp"> + <source lang="cpp-qt">
 void QInputContext::setInputMode(int mode);  void QInputContext::setInputMode(int mode);
 </source>  </source>
Line 203:
Line 203:
  
 HIC Modes:  HIC Modes:
- * HILDON_GTK_INPUT_MODE_ALPHA 	alphabetical characters and whitespace + * <code>HILDON_GTK_INPUT_MODE_ALPHA</code> 	alphabetical characters and whitespace
- * HILDON_GTK_INPUT_MODE_NUMERIC 	numbers 0-9 and the '-' character + * <code>HILDON_GTK_INPUT_MODE_NUMERIC</code> 	numbers 0-9 and the '-' character
- * HILDON_GTK_INPUT_MODE_SPECIAL 	special characters + * <code>HILDON_GTK_INPUT_MODE_SPECIAL</code> 	special characters
- * HILDON_GTK_INPUT_MODE_HEXA 	hexadecimal characters; numbers 0-9, characters a-f, and A-F + * <code>HILDON_GTK_INPUT_MODE_HEXA</code> 	hexadecimal characters; numbers 0-9, characters a-f, and A-F
- * HILDON_GTK_INPUT_MODE_TELE 	telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?," + * <code>HILDON_GTK_INPUT_MODE_TELE</code> 	telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?,"
- * HILDON_GTK_INPUT_MODE_FULL 	unrestricted entry mode, combination of the alpha, numeric and special modes. + * <code>HILDON_GTK_INPUT_MODE_FULL</code> 	unrestricted entry mode, combination of the alpha, numeric and special modes.
- * HILDON_GTK_INPUT_MODE_MULTILINE 	the client contains multiple lines of text or accepts linebreaks in the input. + * <code>HILDON_GTK_INPUT_MODE_MULTILINE</code> 	the client contains multiple lines of text or accepts linebreaks in the input.
- * HILDON_GTK_INPUT_MODE_INVISIBLE 	do not echo or save the input in the IM when entering sensitive information such as passwords. + * <code>HILDON_GTK_INPUT_MODE_INVISIBLE</code> 	do not echo or save the input in the IM when entering sensitive information such as passwords.
- * HILDON_GTK_INPUT_MODE_AUTOCAP 	automatically capitalize the first letter at the start of a sentence. + * <code>HILDON_GTK_INPUT_MODE_AUTOCAP</code> 	automatically capitalize the first letter at the start of a sentence.
- * HILDON_GTK_INPUT_MODE_DICTIONARY 	enable predictive dictionaries and learning based on the input. + * <code>HILDON_GTK_INPUT_MODE_DICTIONARY</code> 	enable predictive dictionaries and learning based on the input.
  
 Example:  Example:
 For a password field we need to set a specific IM mode:  For a password field we need to set a specific IM mode:
- <source lang="cpp"> + <source lang="cpp-qt">
 int mode = HILDON_GTK_INPUT_MODE_FULL | HILDON_GTK_INPUT_MODE_INVISIBLE  int mode = HILDON_GTK_INPUT_MODE_FULL | HILDON_GTK_INPUT_MODE_INVISIBLE
 QInputContext *qic = widget->inputContext();  QInputContext *qic = widget->inputContext();
Line 227:
Line 227:
  
 Setting the ImMode is quite easy. Check the code below for more understanding.  Setting the ImMode is quite easy. Check the code below for more understanding.
- <source lang="cpp"> + <source lang="cpp-qt">
 #ifdef Q_WS_HILDON  #ifdef Q_WS_HILDON
 #include <QInputContext>  #include <QInputContext>
Line 253:
Line 253:
 Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.  Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.
 Eg:  Eg:
- <source lang="cpp"> + <source lang="cpp-qt">
 QTableWidget *table = new QTableWidget(this);  QTableWidget *table = new QTableWidget(this);
 table->setProperty("FingerScrollable", true);    table->setProperty("FingerScrollable", true);  
Line 279:
Line 279:
 http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png  http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png
 Are supported by Qt. To create them you need to create a MainWindow child of another Main window.  Are supported by Qt. To create them you need to create a MainWindow child of another Main window.
- <source lang="cpp"> + <source lang="cpp-qt">
 QMainWindow *fistStackableWindow = new QMainWindow;  QMainWindow *fistStackableWindow = new QMainWindow;
 QMainWindow *secondStackableWindow = new QMainWindow(fistStackableWindow);  QMainWindow *secondStackableWindow = new QMainWindow(fistStackableWindow);
Line 296:
Line 296:
  
 === How to minimize a Qt application? ===  === How to minimize a Qt application? ===
- <source lang="cpp"> + <source lang="cpp-qt">
 QDBusConnection c = QDBusConnection::sessionBus();  QDBusConnection c = QDBusConnection::sessionBus();
 QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");  QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
Line 304:
Line 304:
  
 If you want to run your application in portrait mode then you can add these lines to your application. The code goes in your main widget constructor.  If you want to run your application in portrait mode then you can add these lines to your application. The code goes in your main widget constructor.
- <source lang="cpp"> + <source lang="cpp-qt">
 #ifdef Q_WS_HILDON  #ifdef Q_WS_HILDON
 //Includes for portrait mode support  //Includes for portrait mode support
Line 337:
Line 337:
  
 As a workaround for the problem you can set a window property that tells HD to skip the transitions:  As a workaround for the problem you can set a window property that tells HD to skip the transitions:
- <source lang="cpp"> + <source lang="cpp-qt">
   static void set_no_transitions (Display *dpy, Window w)    static void set_no_transitions (Display *dpy, Window w)
   {    {



amigadave: tidy, use 
amigadave — Thu, 17 Jun 2010 13:08:19 GMT
tidy, use <source>
Show changes


amigadave: tidy
amigadave — Wed, 02 Jun 2010 15:03:50 GMT
tidy
Show changes


amigadave: /* Installing Qt packages in Scratchbox */ Diablo link
amigadave — Wed, 02 Jun 2010 13:37:49 GMT
Installing Qt packages in Scratchbox:  Diablo link

		
		
		
		
		
		
		← Older revision
		Revision as of 13:37, 2 June 2010
		
		Line 14:
Line 14:
  
 == Installing Qt packages in Scratchbox ==  == Installing Qt packages in Scratchbox ==
- Maemo Qt developers offers a set of Qt packages for [[Open development/Maemo roadmap/Fremantle|Fremantle]] (Maemo5 - OS2009) and Diablo (Maemo4.1 - OS2008). + Maemo Qt developers offers a set of Qt packages for [[Open development/Maemo roadmap/Fremantle|Fremantle]] (Maemo5 - OS2009) and [[Open development/Maemo roadmap/Diablo|Diablo]] (Maemo4.1 - OS2008).
  
 == Fremantle ==  == Fremantle ==




amigadave: remove icons from section titles
amigadave — Wed, 02 Jun 2010 12:46:43 GMT
remove icons from section titles

		
		
		
		
		
		
		← Older revision
		Revision as of 12:46, 2 June 2010
		
		Line 1:
Line 1:
- = [[Image:Intro.png]] Introduction = + = Introduction =
  
 To develop with [[Qt-Maemo|Qt for Maemo]], a working SDK installation is required. There are [[Documentation/Maemo_5_Final_SDK_Installation|instructions on how to install the Maemo SDK]], and you can [http://www.youtube.com/watch?v=c8myh_iBy8k watch the Maemo SDK in action]. Alternatively, you may want to try [[MADDE]], a cross-platform Maemo development tool, available as a technology preview.  To develop with [[Qt-Maemo|Qt for Maemo]], a working SDK installation is required. There are [[Documentation/Maemo_5_Final_SDK_Installation|instructions on how to install the Maemo SDK]], and you can [http://www.youtube.com/watch?v=c8myh_iBy8k watch the Maemo SDK in action]. Alternatively, you may want to try [[MADDE]], a cross-platform Maemo development tool, available as a technology preview.
Line 9:
Line 9:
 Read more about [http://maemo.org/intro/platform/ the Maemo platform] and a [http://maemo.org/intro/developer_overview/ developer overview].  Read more about [http://maemo.org/intro/platform/ the Maemo platform] and a [http://maemo.org/intro/developer_overview/ developer overview].
  
- = [[Image:Rocket.png]] Getting started = + = Getting started =
  
 To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation|install the Maemo SDK]].  To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation|install the Maemo SDK]].
Line 38:
Line 38:
  
 You can build your Maemo Qt application in 3 simple steps:  You can build your Maemo Qt application in 3 simple steps:
- # Generating project file (Required if there is no .pro file into the app source tree)<br/><pre>qmake -project</pre> + # Generating project file (Required if there is no .pro file into the app source tree)<pre>qmake -project</pre>
- # Generating Makefile from the QMake project file:<br/><pre>qmake file.pro</pre> + # Generating Makefile from the QMake project file:<pre>qmake file.pro</pre>
 # <pre>make</pre>  # <pre>make</pre>
  
Line 76:
Line 76:
   su -c ./quassel user    su -c ./quassel user
  
- = [[Image:Hammer.png]] Porting Qt applications to Maemo = + = Porting Qt applications to Maemo =
  
 Porting a Qt desktop application to Maemo requires very little effort. This is because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.  Porting a Qt desktop application to Maemo requires very little effort. This is because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.
Line 150:
Line 150:
 To get the benefits of the ongoing Maemo 5 hildon integration work in Qt, you must get the latest Qt source code and compile it yourself. See [http://wiki.maemo.org/Qt4_Hildon#Building_Qt_from_GIT_rep Building Qt from GIT repository].  To get the benefits of the ongoing Maemo 5 hildon integration work in Qt, you must get the latest Qt source code and compile it yourself. See [http://wiki.maemo.org/Qt4_Hildon#Building_Qt_from_GIT_rep Building Qt from GIT repository].
  
- = [[Image:Bug.png]] Debugging a Qt application = + = Debugging a Qt application =
  
 {{main|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}  {{main|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}
Line 158:
Line 158:
   /usr/local/bin/gdb7 ./myapp    /usr/local/bin/gdb7 ./myapp
  
- = [[Image:chart.png]] Profiling a Qt application = + = Profiling a Qt application =
  
 == OProfile ==  == OProfile ==
Line 170:
Line 170:
  
  
- = [[Image:package.png]] Packaging a Qt application for Maemo = + = Packaging a Qt application for Maemo =
  
 {{main|Packaging a Qt application}}  {{main|Packaging a Qt application}}
  
- = [[Image:Helmet.png]] Maemo Qt API Reference = + = Maemo Qt API Reference =
  
 Maemo Qt is based on Qt for X11. It shares same APIs avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run in Maemo devices as well.    Maemo Qt is based on Qt for X11. It shares same APIs avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run in Maemo devices as well.  
Line 367:
Line 367:
 Adding a QToolBar to a QMainWindow will always result in a toolbar at the  Adding a QToolBar to a QMainWindow will always result in a toolbar at the
 bottom of the screen. (Justification/Workarounds?)  bottom of the screen. (Justification/Workarounds?)
-  
- <br><br>  
-  
  
  
- = [[Image:Helmet.png]] Contributing to the Maemo Qt Project = + = Contributing to the Maemo Qt Project =
  
 Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.  Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.
Line 418:
Line 415:
  
  
- =[[Image:Help-contents.png]] F.A.Q.= + =F.A.Q.=
  
 ; ''I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong?''  ; ''I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong?''
Line 435:
Line 432:
 : libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.  : libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.
 : <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>  : <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>
-  
  
  
 [[Category:Development]]  [[Category:Development]]
 [[Category:Qt]]  [[Category:Qt]]




amigadave: /* Using Qt 4.6 in Fremantle */ link
amigadave — Wed, 02 Jun 2010 12:24:52 GMT
Using Qt 4.6 in Fremantle:  link

		
		
		
		
		
		
		← Older revision
		Revision as of 12:24, 2 June 2010
		
		Line 21:
Line 21:
  
 === Using Qt 4.6 in Fremantle ===  === Using Qt 4.6 in Fremantle ===
- Since PR 1.2 release Qt 4.6 is available in public Fremantle repository +  
- To upgrade older scratchbox targets to use the latest packages execute the following commands: + Since the [[Maemo 5/PR1.2|PR1.2]] release Qt 4.6 is available in public Fremantle repository. To upgrade older Scratchbox targets to use the latest packages execute the following commands:
   fakeroot apt-get update    fakeroot apt-get update
   fakeroot apt-get dist-upgrade    fakeroot apt-get dist-upgrade




amigadave: /* FREMANTLE (Qt 4.6) */ 4.6 for pre-PR1.2 was experimental
amigadave — Wed, 02 Jun 2010 11:48:07 GMT
FREMANTLE (Qt 4.6):  4.6 for pre-PR1.2 was experimental

		
		
		
		
		
		
		← Older revision
		Revision as of 11:48, 2 June 2010
		
		Line 370:
Line 370:
 <br><br>  <br><br>
  
- =FREMANTLE (Qt 4.6)=  
- Here an example that shows several maemo5 Qt widgets in Qt 4.6.  
  
- http://qt.nokia.com/doc/qt-maemo-4.6/examples-maemo5.html  
-  
- http://qt.gitorious.org/+qt-developers/qt/x11-maemo/trees/986340bb5e4b69ceb0a959c2a067a1ed5e504d50/examples/maemo5/widgets  
-  
- ==Finger Scrolling==  
-  
- Kinetic scrolling is present by default in most scrolling widgets, eg. <code>QTextBrowser</code>, <code>QTableView</code>. If you want to tweak the kinetic scrolling parameters like inertia and acceleration then you can instaniate a <code>QAbstractKineticScroller</code> object like this:  
-  
-  QAbstractKineticScroller ks =   
-    scrollArea->property("kineticScroller").value<QAbstractKineticScroller *>();  
-  
- where scrollArea could be <code>QScrollArea</code> with some widgets added to it, or you could use implementations like <code>QTextBrowser</code>.  
-  
- You can tweak scrolling like this:  
-  ks->setDragInertia( (double)value / 100.0)  
-  ks->setMode(QAbstractKineticScroller::PushMode)  
-   
- etc., refer to the examples here for details: http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/examples/maemo5/kineticscroller/main.cpp  
-  
- ==QSplashScreen==  
- Should be fixed in Qt 4.6. SplashWindow type is not supported by Fremantle WM. Qt 4.6 display splash screen using popup window type.  
-  
- ==Orientation==  
- [http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-rotation.html Official documentation]  
-  
- ==Maemo5 Readme file==  
- There is a [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/README.maemo5 README file in Qt 4.6 source tree].  
  
 = [[Image:Helmet.png]] Contributing to the Maemo Qt Project =  = [[Image:Helmet.png]] Contributing to the Maemo Qt Project =




dohollan: Qt4 Hildon moved to Qt4 Hildon Legacy: Move for Legacy
dohollan — Wed, 14 Apr 2010 12:01:17 GMT
Qt4 Hildon moved to Qt4 Hildon Legacy: Move for Legacy

		
		
		
		
		
		
		← Older revision
		Revision as of 12:01, 14 April 2010
		
		



amigadave: /* CMake */ remove dead link
amigadave — Mon, 12 Apr 2010 08:28:57 GMT
CMake:  remove dead link

		
		
		
		
		
		
		← Older revision
		Revision as of 08:28, 12 April 2010
		
		Line 44:
Line 44:
 === CMake ===  === CMake ===
  
- Because of some issue with [http://www.cmake.org/ CMake], [[Open development/Maemo roadmap/Diablo|Diablo]] CMake packages are currently useless since CMake segfaults (on the device at least). This issue has been solved in [[Open development/Maemo roadmap/Fremantle|Fremantle]] and CMake packages that comes from Fremantle [[SDK]] work nicely. + Because of some issue with [http://www.cmake.org/ CMake], [[Open development/Maemo roadmap/Diablo|Diablo]] CMake packages are currently useless since CMake segfaults (on the device at least). This issue has been solved in [[Open development/Maemo roadmap/Fremantle|Fremantle]] and CMake packages that comes from Fremantle SDK work nicely.
  
 CMake projects usually have a <code>CMakeLists.txt</code> file instead of:    CMake projects usually have a <code>CMakeLists.txt</code> file instead of:  




192.100.124.219: /* Fremantle */
192.100.124.219 — Tue, 23 Mar 2010 17:30:53 GMT
Fremantle

		
		
		
		
		
		
		← Older revision
		Revision as of 17:30, 23 March 2010
		
		Line 18:
Line 18:
 == Fremantle ==  == Fremantle ==
 You do not need to add any extra repository for Fremantle since Qt packages are already available in the SDK. You can install Qt with the command:  You do not need to add any extra repository for Fremantle since Qt packages are already available in the SDK. You can install Qt with the command:
-   fakeroot apt-get install libqt4-gui libqt4-dev +   fakeroot apt-get install libqt4-dev
  
 === Using Qt 4.6 in Fremantle ===  === Using Qt 4.6 in Fremantle ===

← Older revision		Revision as of 11:48, 2 June 2010
Line 370:		Line 370:
	<br><br>		<br><br>

-	~~=FREMANTLE (Qt 4.6)=~~
-	~~Here an example that shows several maemo5 Qt widgets in Qt 4.6.~~

-	~~http://qt.nokia.com/doc/qt-maemo-4.6/examples-maemo5.html~~
-
-	~~http://qt.gitorious.org/+qt-developers/qt/x11-maemo/trees/986340bb5e4b69ceb0a959c2a067a1ed5e504d50/examples/maemo5/widgets~~
-
-	~~==Finger Scrolling==~~
-
-	Kinetic scrolling is present by default in most scrolling widgets, eg. <code>QTextBrowser</code>, <code>QTableView</code>. If you want to tweak the kinetic scrolling parameters like inertia and acceleration then you can instaniate a <code>QAbstractKineticScroller</code> object like this:
-
-	~~QAbstractKineticScroller ks =~~
-	~~scrollArea->property("kineticScroller").value<QAbstractKineticScroller *>();~~
-
-	~~where scrollArea could be <code>QScrollArea</code> with some widgets added to it, or you could use implementations like <code>QTextBrowser</code>.~~
-
-	~~You can tweak scrolling like this:~~
-	~~ks->setDragInertia( (double)value / 100.0)~~
-	~~ks->setMode(QAbstractKineticScroller::PushMode)~~
-
-	~~etc., refer to the examples here for details: http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/examples/maemo5/kineticscroller/main.cpp~~
-
-	~~==QSplashScreen==~~
-	~~Should be fixed in Qt 4.6. SplashWindow type is not supported by Fremantle WM. Qt 4.6 display splash screen using popup window type.~~
-
-	~~==Orientation==~~
-	~~[http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-rotation.html Official documentation]~~
-
-	~~==Maemo5 Readme file==~~
-	~~There is a [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/README.maemo5 README file in Qt 4.6 source tree].~~

	= [[Image:Helmet.png]] Contributing to the Maemo Qt Project =		= [[Image:Helmet.png]] Contributing to the Maemo Qt Project =

← Older revision		Revision as of 12:08, 9 March 2011
Line 110:		Line 110:
	Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives, for example with Qt 4.5 on Diablo and Fremantle:		Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives, for example with Qt 4.5 on Diablo and Fremantle:

-	<source lang="cpp">	+	<source lang="cpp-qt">
	#ifdef Q_WS_HILDON		#ifdef Q_WS_HILDON
	//Specific hildon/Maemo5 code here		//Specific hildon/Maemo5 code here
Line 197:		Line 197:

	A developer can change it by using:		A developer can change it by using:
-	<source lang="cpp">	+	<source lang="cpp-qt">
	void QInputContext::setInputMode(int mode);		void QInputContext::setInputMode(int mode);
	</source>		</source>
Line 203:		Line 203:

	HIC Modes:		HIC Modes:
-	* HILDON_GTK_INPUT_MODE_ALPHA alphabetical characters and whitespace	+	* <code>HILDON_GTK_INPUT_MODE_ALPHA</code> alphabetical characters and whitespace
-	* HILDON_GTK_INPUT_MODE_NUMERIC numbers 0-9 and the '-' character	+	* <code>HILDON_GTK_INPUT_MODE_NUMERIC</code> numbers 0-9 and the '-' character
-	* HILDON_GTK_INPUT_MODE_SPECIAL special characters	+	* <code>HILDON_GTK_INPUT_MODE_SPECIAL</code> special characters
-	* HILDON_GTK_INPUT_MODE_HEXA hexadecimal characters; numbers 0-9, characters a-f, and A-F	+	* <code>HILDON_GTK_INPUT_MODE_HEXA</code> hexadecimal characters; numbers 0-9, characters a-f, and A-F
-	* HILDON_GTK_INPUT_MODE_TELE telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?,"	+	* <code>HILDON_GTK_INPUT_MODE_TELE</code> telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?,"
-	* HILDON_GTK_INPUT_MODE_FULL unrestricted entry mode, combination of the alpha, numeric and special modes.	+	* <code>HILDON_GTK_INPUT_MODE_FULL</code> unrestricted entry mode, combination of the alpha, numeric and special modes.
-	* HILDON_GTK_INPUT_MODE_MULTILINE the client contains multiple lines of text or accepts linebreaks in the input.	+	* <code>HILDON_GTK_INPUT_MODE_MULTILINE</code> the client contains multiple lines of text or accepts linebreaks in the input.
-	* HILDON_GTK_INPUT_MODE_INVISIBLE do not echo or save the input in the IM when entering sensitive information such as passwords.	+	* <code>HILDON_GTK_INPUT_MODE_INVISIBLE</code> do not echo or save the input in the IM when entering sensitive information such as passwords.
-	* HILDON_GTK_INPUT_MODE_AUTOCAP automatically capitalize the first letter at the start of a sentence.	+	* <code>HILDON_GTK_INPUT_MODE_AUTOCAP</code> automatically capitalize the first letter at the start of a sentence.
-	* HILDON_GTK_INPUT_MODE_DICTIONARY enable predictive dictionaries and learning based on the input.	+	* <code>HILDON_GTK_INPUT_MODE_DICTIONARY</code> enable predictive dictionaries and learning based on the input.

	Example:		Example:
	For a password field we need to set a specific IM mode:		For a password field we need to set a specific IM mode:
-	<source lang="cpp">	+	<source lang="cpp-qt">
	int mode = HILDON_GTK_INPUT_MODE_FULL \| HILDON_GTK_INPUT_MODE_INVISIBLE		int mode = HILDON_GTK_INPUT_MODE_FULL \| HILDON_GTK_INPUT_MODE_INVISIBLE
	QInputContext *qic = widget->inputContext();		QInputContext *qic = widget->inputContext();
Line 227:		Line 227:

	Setting the ImMode is quite easy. Check the code below for more understanding.		Setting the ImMode is quite easy. Check the code below for more understanding.
-	<source lang="cpp">	+	<source lang="cpp-qt">
	#ifdef Q_WS_HILDON		#ifdef Q_WS_HILDON
	#include <QInputContext>		#include <QInputContext>
Line 253:		Line 253:
	Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.		Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.
	Eg:		Eg:
-	<source lang="cpp">	+	<source lang="cpp-qt">
	QTableWidget *table = new QTableWidget(this);		QTableWidget *table = new QTableWidget(this);
	table->setProperty("FingerScrollable", true);		table->setProperty("FingerScrollable", true);
Line 279:		Line 279:
	http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png		http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png
	Are supported by Qt. To create them you need to create a MainWindow child of another Main window.		Are supported by Qt. To create them you need to create a MainWindow child of another Main window.
-	<source lang="cpp">	+	<source lang="cpp-qt">
	QMainWindow *fistStackableWindow = new QMainWindow;		QMainWindow *fistStackableWindow = new QMainWindow;
	QMainWindow *secondStackableWindow = new QMainWindow(fistStackableWindow);		QMainWindow *secondStackableWindow = new QMainWindow(fistStackableWindow);
Line 296:		Line 296:

	=== How to minimize a Qt application? ===		=== How to minimize a Qt application? ===
-	<source lang="cpp">	+	<source lang="cpp-qt">
	QDBusConnection c = QDBusConnection::sessionBus();		QDBusConnection c = QDBusConnection::sessionBus();
	QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");		QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
Line 304:		Line 304:

	If you want to run your application in portrait mode then you can add these lines to your application. The code goes in your main widget constructor.		If you want to run your application in portrait mode then you can add these lines to your application. The code goes in your main widget constructor.
-	<source lang="cpp">	+	<source lang="cpp-qt">
	#ifdef Q_WS_HILDON		#ifdef Q_WS_HILDON
	//Includes for portrait mode support		//Includes for portrait mode support
Line 337:		Line 337:

	As a workaround for the problem you can set a window property that tells HD to skip the transitions:		As a workaround for the problem you can set a window property that tells HD to skip the transitions:
-	<source lang="cpp">	+	<source lang="cpp-qt">
	static void set_no_transitions (Display *dpy, Window w)		static void set_no_transitions (Display *dpy, Window w)
	{		{

← Older revision		Revision as of 13:37, 2 June 2010
Line 14:		Line 14:

	== Installing Qt packages in Scratchbox ==		== Installing Qt packages in Scratchbox ==
-	Maemo Qt developers offers a set of Qt packages for [[Open development/Maemo roadmap/Fremantle\|Fremantle]] (Maemo5 - OS2009) and Diablo (Maemo4.1 - OS2008).	+	Maemo Qt developers offers a set of Qt packages for [[Open development/Maemo roadmap/Fremantle\|Fremantle]] (Maemo5 - OS2009) and [[Open development/Maemo roadmap/Diablo\|Diablo]] (Maemo4.1 - OS2008).

	== Fremantle ==		== Fremantle ==

← Older revision		Revision as of 12:46, 2 June 2010
Line 1:		Line 1:
-	= ~~[[Image:Intro.png]]~~ Introduction =	+	= Introduction =

	To develop with [[Qt-Maemo\|Qt for Maemo]], a working SDK installation is required. There are [[Documentation/Maemo_5_Final_SDK_Installation\|instructions on how to install the Maemo SDK]], and you can [http://www.youtube.com/watch?v=c8myh_iBy8k watch the Maemo SDK in action]. Alternatively, you may want to try [[MADDE]], a cross-platform Maemo development tool, available as a technology preview.		To develop with [[Qt-Maemo\|Qt for Maemo]], a working SDK installation is required. There are [[Documentation/Maemo_5_Final_SDK_Installation\|instructions on how to install the Maemo SDK]], and you can [http://www.youtube.com/watch?v=c8myh_iBy8k watch the Maemo SDK in action]. Alternatively, you may want to try [[MADDE]], a cross-platform Maemo development tool, available as a technology preview.
Line 9:		Line 9:
	Read more about [http://maemo.org/intro/platform/ the Maemo platform] and a [http://maemo.org/intro/developer_overview/ developer overview].		Read more about [http://maemo.org/intro/platform/ the Maemo platform] and a [http://maemo.org/intro/developer_overview/ developer overview].

-	= ~~[[Image:Rocket.png]]~~ Getting started =	+	= Getting started =

	To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation\|install the Maemo SDK]].		To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation\|install the Maemo SDK]].
Line 38:		Line 38:

	You can build your Maemo Qt application in 3 simple steps:		You can build your Maemo Qt application in 3 simple steps:
-	# Generating project file (Required if there is no .pro file into the app source tree)~~<br/>~~<pre>qmake -project</pre>	+	# Generating project file (Required if there is no .pro file into the app source tree)<pre>qmake -project</pre>
-	# Generating Makefile from the QMake project file:~~<br/>~~<pre>qmake file.pro</pre>	+	# Generating Makefile from the QMake project file:<pre>qmake file.pro</pre>
	# <pre>make</pre>		# <pre>make</pre>

Line 76:		Line 76:
	su -c ./quassel user		su -c ./quassel user

-	= ~~[[Image:Hammer.png]]~~ Porting Qt applications to Maemo =	+	= Porting Qt applications to Maemo =

	Porting a Qt desktop application to Maemo requires very little effort. This is because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.		Porting a Qt desktop application to Maemo requires very little effort. This is because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.
Line 150:		Line 150:
	To get the benefits of the ongoing Maemo 5 hildon integration work in Qt, you must get the latest Qt source code and compile it yourself. See [http://wiki.maemo.org/Qt4_Hildon#Building_Qt_from_GIT_rep Building Qt from GIT repository].		To get the benefits of the ongoing Maemo 5 hildon integration work in Qt, you must get the latest Qt source code and compile it yourself. See [http://wiki.maemo.org/Qt4_Hildon#Building_Qt_from_GIT_rep Building Qt from GIT repository].

-	= ~~[[Image:Bug.png]]~~ Debugging a Qt application =	+	= Debugging a Qt application =

	{{main\|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}		{{main\|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}
Line 158:		Line 158:
	/usr/local/bin/gdb7 ./myapp		/usr/local/bin/gdb7 ./myapp

-	= ~~[[Image:chart.png]]~~ Profiling a Qt application =	+	= Profiling a Qt application =

	== OProfile ==		== OProfile ==
Line 170:		Line 170:


-	= ~~[[Image:package.png]]~~ Packaging a Qt application for Maemo =	+	= Packaging a Qt application for Maemo =

	{{main\|Packaging a Qt application}}		{{main\|Packaging a Qt application}}

-	= ~~[[Image:Helmet.png]]~~ Maemo Qt API Reference =	+	= Maemo Qt API Reference =

	Maemo Qt is based on Qt for X11. It shares same APIs avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run in Maemo devices as well.		Maemo Qt is based on Qt for X11. It shares same APIs avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run in Maemo devices as well.
Line 367:		Line 367:
	Adding a QToolBar to a QMainWindow will always result in a toolbar at the		Adding a QToolBar to a QMainWindow will always result in a toolbar at the
	bottom of the screen. (Justification/Workarounds?)		bottom of the screen. (Justification/Workarounds?)
-
-	~~<br><br>~~
-


-	= ~~[[Image:Helmet.png]]~~ Contributing to the Maemo Qt Project =	+	= Contributing to the Maemo Qt Project =

	Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.		Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.
Line 418:		Line 415:


-	=~~[[Image:Help-contents.png]]~~ F.A.Q.=	+	=F.A.Q.=

	; ''I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong?''		; ''I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong?''
Line 435:		Line 432:
	: libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.		: libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.
	: <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>		: <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>
-


	[[Category:Development]]		[[Category:Development]]
	[[Category:Qt]]		[[Category:Qt]]

← Older revision		Revision as of 12:24, 2 June 2010
Line 21:		Line 21:

	=== Using Qt 4.6 in Fremantle ===		=== Using Qt 4.6 in Fremantle ===
-	Since ~~PR 1~~.2 release Qt 4.6 is available in public Fremantle repository	+
-	To upgrade older ~~scratchbox~~ targets to use the latest packages execute the following commands:	+	Since the [[Maemo 5/PR1.2\|PR1.2]] release Qt 4.6 is available in public Fremantle repository. To upgrade older Scratchbox targets to use the latest packages execute the following commands:
	fakeroot apt-get update		fakeroot apt-get update
	fakeroot apt-get dist-upgrade		fakeroot apt-get dist-upgrade

← Older revision		Revision as of 08:28, 12 April 2010
Line 44:		Line 44:
	=== CMake ===		=== CMake ===

-	Because of some issue with [http://www.cmake.org/ CMake], [[Open development/Maemo roadmap/Diablo\|Diablo]] CMake packages are currently useless since CMake segfaults (on the device at least). This issue has been solved in [[Open development/Maemo roadmap/Fremantle\|Fremantle]] and CMake packages that comes from Fremantle [[SDK]] work nicely.	+	Because of some issue with [http://www.cmake.org/ CMake], [[Open development/Maemo roadmap/Diablo\|Diablo]] CMake packages are currently useless since CMake segfaults (on the device at least). This issue has been solved in [[Open development/Maemo roadmap/Fremantle\|Fremantle]] and CMake packages that comes from Fremantle SDK work nicely.

	CMake projects usually have a <code>CMakeLists.txt</code> file instead of:		CMake projects usually have a <code>CMakeLists.txt</code> file instead of:

← Older revision		Revision as of 17:30, 23 March 2010
Line 18:		Line 18:
	== Fremantle ==		== Fremantle ==
	You do not need to add any extra repository for Fremantle since Qt packages are already available in the SDK. You can install Qt with the command:		You do not need to add any extra repository for Fremantle since Qt packages are already available in the SDK. You can install Qt with the command:
-	fakeroot apt-get install ~~libqt4-gui~~ libqt4-dev	+	fakeroot apt-get install libqt4-dev

	=== Using Qt 4.6 in Fremantle ===		=== Using Qt 4.6 in Fremantle ===