Development Tricks: Difference between revisions
Jump to navigation
Jump to search
(Started. "This page shows a list of time-saving workflow tips for Devs who are developing for Scribus. Feel free to add your shortcuts") |
(→make) |
||
Line 8: | Line 8: | ||
# perhaps there can be a script here | # perhaps there can be a script here | ||
# That automagically does this? | # That automagically does this? | ||
== traces in the terminal== | |||
Whenever you need to understand what happens un the code, it's possible to issue some traces on the terminal using qDebug function : | |||
<pre>qDebug() << blah << "some text";</pre> | |||
Clean your code before issuing a patch, unless its absolutely necessary to mess the user's terminal. | |||
== Related == | == Related == | ||
* [[Low_Hanging_Fruit]] | * [[Low_Hanging_Fruit]] | ||
* [[How_Can_I_Help]] | * [[How_Can_I_Help]] |
Revision as of 20:58, 20 January 2014
Background
This page shows a list of time-saving workflow tips for Devs who are developing for Scribus. Feel free to add your shortcuts
make
There is no need to make each time, certain files like language files can just be copied.
# perhaps there can be a script here # That automagically does this?
traces in the terminal
Whenever you need to understand what happens un the code, it's possible to issue some traces on the terminal using qDebug function :
qDebug() << blah << "some text";
Clean your code before issuing a patch, unless its absolutely necessary to mess the user's terminal.