Search results
- {{note|The context marker can be added when within some of the standard XML sources too. In Qt Designer forms (<tt>.ui</tt> files), each text label to a widget ...s only C++ sources, while when you run the script locally, some of the XML sources containing translatable strings will be checked as well. <tt>i18ncheckarg</ ...23 KB (3,671 words) - 12:42, 11 October 2019
- ...n the [http://www.kstuff.org/docs/tutorial/ KNewStuff tutorial] and in the sources: [http://webcvs.kde.org/kdelibs/knewstuff/README.knewstuff?view=markup kdel ...6 KB (985 words) - 13:23, 31 May 2019
- ...o build the program is to use CMake. We add <tt>mainwindow.cpp</tt> to the sources list, include the XmlGui and TextEdit frameworks, and replace all <tt>tutor ...7 KB (847 words) - 18:00, 18 April 2020
- ...o build the program is to use CMake. We add <tt>mainwindow.cpp</tt> to the sources list, include the XmlGui and TextWidgets (for KTextEdit) frameworks, and re ...7 KB (833 words) - 16:43, 24 August 2020
- ...o build the program is to use CMake. We add <tt>mainwindow.cpp</tt> to the sources list, include the XmlGui and TextWidgets (for KTextEdit) frameworks, and re ...7 KB (781 words) - 16:43, 24 August 2020
- future, there will probably be a precompiler for your sources to write ...Then you edit your {{path|Makefile.am}}, adding 'MyInterface.skel' to your SOURCES list and {{path|MyInterface.h}} to include_HEADERS. ...23 KB (3,461 words) - 00:20, 5 March 2016
- {{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}} ...4 KB (591 words) - 10:25, 11 March 2016
- source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim ...6 KB (857 words) - 11:59, 9 February 2018
- ...s to your installation. This is normally done by editing {{Path | /etc/apt/sources.list}} as user root and adding a line starting with <tt>deb-src</tt>: kdesudo kwrite /etc/apt/sources.list ...7 KB (1,148 words) - 21:03, 29 June 2011
- ...way to get stdcxx, current qt source (4.7.1 now), and a few others to your SOURCES directory. Overnight downloads or a USB Key/USB Disk at work to transport ...9 KB (1,423 words) - 20:57, 29 June 2011
- ...ide that you will also need a working tool chain to be able to compile the sources. These will also come with your distribution. ...6 KB (966 words) - 20:44, 29 June 2011
- source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim ...6 KB (802 words) - 10:25, 11 March 2016
- SOURCES += vehicletracking.cpp ...8 KB (1,045 words) - 09:30, 21 October 2016
- source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim ...8 KB (668 words) - 13:57, 5 March 2016
- * Array(string) '''connectedSources''': all the sources of the dataengine we are connected to (and whose data will appear in the '' * Array(string) '''sources''' (read only): all the sources available from the dataengine ...33 KB (4,373 words) - 23:27, 11 September 2014
- ...nes for Marble is located at marble/data/mwdbii/PDIFFBORDER.PNT inside the sources. Inside the marble/tools/pnt2svg directory you can now execute the followin ...7 KB (1,192 words) - 21:01, 10 March 2016
- ...ged since tutorial 1 is that <tt>mainwindow.cpp</tt> has been added to the sources list and any <tt>tutorial1</tt> has become <tt>tutorial2</tt>.'' ...7 KB (640 words) - 15:47, 14 July 2012
- If you only need SVN for checking out the sources (read-only), use the protocol: "svn" at the server: "anonsvn.kde.org". ...Subversion. You will need version 1.1 at least. If you are compiling from sources and want to access the KDE repository by https (and not by svn+ssh), you wi ...16 KB (2,537 words) - 20:45, 11 October 2023
- source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim ...6 KB (930 words) - 10:25, 11 March 2016
- 1) patches must have unique names because they are copied to packages/SOURCES ...6 KB (1,098 words) - 20:57, 29 June 2011