User:Declan.mcgrath: Difference between revisions

From KDE TechBase
mNo edit summary
(Added draft article on Qt widgets vs KDE widgets)
 
(57 intermediate revisions by the same user not shown)
Line 1: Line 1:
Developing Ruby QT Applications using QT Designer and Ruby on Ubuntu
= Published Articles  =


<br>
;[[Development/Tutorials/Developing Qt4 Applications using Qt Designer and Ruby on Kubuntu|Developing Qt4 Applications using Qt Designer and Ruby on Kubuntu]]
:''Tutorial that shows how to design a simple User Interface in Qt Designer and then use the resulting widget in a Qt Ruby application we build from scratch.''


== Install the appropriate packages ==
= <br> Draft Articles =


These instructions are tested with Ubuntu Jaunty Jackalope 9.04


*sudo aptitude install libkorundum4-ruby1.8<br>  
 
*sudo aptitude qt4-designer<br>
;[[Development/Tutorials/Quickstart Guide to the Wikitext syntax used in KDE Techbase|Quickstart Guide to the Wikitext syntax used in KDE Techbase]]
*sudo aptitude libqt4-ruby1.8-dev<br>
;<br>
*sudo aptitude install libqt4-ruby1.8-examples<br>
 
*sudo aptitude install qt4-doc qt4-doc-html&nbsp; qt4-demos<br>
;[[Development/Tutorials/Deploying Qt Ruby Applications as a Debian packages for Kubuntu|Deploying Qt Ruby Applications as a Debian packages for Kubuntu]]
*sudo aptitude install qt-creator (you may not need this)<br>
 
Q. What is the difference between writing a Qt application and KDE application?
A. Qt targets multiple platforms and it's widgets provide only functionality that is available on all target platforms. KDE widgets are specialised for the KDE desktop, thus KDE takes a Qt widget and enhances it for the KDE environment. For example, a QDropdownBox might not provide auto-completion because only some target Qt platforms support it - whereas the KDE version will include this functionality in a KDialog (TODO: Get a specific correct example). Additionally KDE contains components for networking, displaying and file system abstraction which would not be available in Qt. If your program needs to run on on platforms other than KDE then you will need to use Qt widgets - if it's KDE you're focused on then go with a KDE application and KDE widgets.

Latest revision as of 14:51, 7 February 2010

Published Articles

Developing Qt4 Applications using Qt Designer and Ruby on Kubuntu
Tutorial that shows how to design a simple User Interface in Qt Designer and then use the resulting widget in a Qt Ruby application we build from scratch.


Draft Articles

Quickstart Guide to the Wikitext syntax used in KDE Techbase

Deploying Qt Ruby Applications as a Debian packages for Kubuntu

Q. What is the difference between writing a Qt application and KDE application? A. Qt targets multiple platforms and it's widgets provide only functionality that is available on all target platforms. KDE widgets are specialised for the KDE desktop, thus KDE takes a Qt widget and enhances it for the KDE environment. For example, a QDropdownBox might not provide auto-completion because only some target Qt platforms support it - whereas the KDE version will include this functionality in a KDialog (TODO: Get a specific correct example). Additionally KDE contains components for networking, displaying and file system abstraction which would not be available in Qt. If your program needs to run on on platforms other than KDE then you will need to use Qt widgets - if it's KDE you're focused on then go with a KDE application and KDE widgets.