Hi folks,
Recently I forced to do some web interfaces for one of my projects so I
decided to learn Python because -as I read- it's easy language to learn
which supports web applications (in addition to GUI/Qt application) so I
need to know the following:
1. Does Qt Creator supports Python
On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz
andre.poen...@mathematik.tu-chemnitz.de wrote:
On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote:
I'm having problems getting Qt Debugger libraries to build.
Environment
-
Creator 2.0 built from source
Qt 4.7
Bashir:
Among the free alternatives out there you can take a look at Eric4
Python IDE if you plan on using Python and the PyQt wrappers at the URL
below:
http://eric-ide.python-projects.org
For wxWidgets development (although I doubt you plan on using the
wxWidgets toolkit) I only know of
Hi,
Because of a change in qt.git/4.7 in the QtDeclarative module we had to patch
creator/2.0 branch. Commit 74a615fbeec95786dfc3d85a667e994f731b73dd will hit
the public repo with the usual 12 hour delay. Once you pull this commit, you've
to update also your qt ...
Regards
Kai
--
Kai Köhne
On Tuesday 11 May 2010 11:39:15 ext M. Bashir Al-Noimi wrote:
Hi folks,
Recently I forced to do some web interfaces for one of my projects so I
decided to learn Python because -as I read- it's easy language to learn which
supports web applications (in addition to GUI/Qt application) so I
On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote:
On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz
andre.poen...@mathematik.tu-chemnitz.de wrote:
On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote:
I'm having problems getting Qt Debugger libraries to build.
Environment
On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote:
On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote:
On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz
andre.poen...@mathematik.tu-chemnitz.de wrote:
On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote:
On May 11, 2010, at 2:37 PM, ext Jack Wootton wrote:
On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote:
On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote:
On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz
andre.poen...@mathematik.tu-chemnitz.de wrote:
On Mon,
On May 11, 2010, at 2:59 PM, ext Eike Ziller wrote:
On May 11, 2010, at 2:37 PM, ext Jack Wootton wrote:
On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote:
On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote:
On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz
Thanks for that tip!
By the way I filed a bug with a sample project already.
On Sat, May 8, 2010 at 3:12 AM, Bradley Smith brad...@baysmith.com wrote:
I noticed the same problem and found that a workaround may be to use $
$files.
For example, try
HEADERS += $$files(./inc/*.h)
I didn't realise Creator require Carbide to run the emualtor. At least now
I have a Symbian Emulator target. thank you for the help on that. Now I
get an error when building the project, related to the Meta Object creation
files I think. myFile.cpp contains the Q_OBJECT macro since it contains
Sorry, the error message was inaccurate; it should have read
:: error: [moc_myFile.cpp] Error -1073741515
On Tue, May 11, 2010 at 2:33 PM, Jack Wootton jackwoot...@gmail.com wrote:
I didn't realise Creator require Carbide to run the emualtor. At least now
I have a Symbian Emulator target.
Hi there,
In our department we have a quite large Project, that uses the subdir feature
of .pro files a lot.
The project itself is stored on a NFS share (which makes IO a little slow).
Every time I open this project in qtcreator the UI of qtcreator stops updating
itself. There is no progress
Hi,
I think this was fixed in 4648a5b3a41ae177fbcc3c2fea2c617dd3357d80
ciao robe
On May 11, 2010, at 4:00 PM, ext Liebe Markus (RtP2/TEF72) wrote:
Hi there,
In our department we have a quite large Project, that uses the subdir feature
of .pro files a lot.
The project itself is stored
My goal is to make a Qt project runnable from any user's Linux home
directory (no hard coded paths).
I tried setting the working directory setting found under Project-Run
Settings-Running Executable-Working Directory?
That your app depends on the working directory is the problem. Depending
On Tue, May 11, 2010 at 1:45 PM, Ed Sutton esut...@fescorp.com wrote:
I am not sure I understand. I am trying to make the Qt Creator project run
settings paths relative (no hard-coded absolute paths ). I want any Red Hat
Enterprise Linux developer to be able to extract a project tarball to
Or are you saying it cannot be done and the best I can do is to use these
static methods at run-time?
We're saying that the run-time solution is superior in general.
Working directory is a notoriously fickle beast and it can change
just depending on how you happen to invoke the program. The
Thanks Victor,
On 11/05/2010 12:21 م, Victor Sardina wrote:
Bashir:
Among the free alternatives out there you can take a look at Eric4
Python IDE if you plan on using Python and the PyQt wrappers at the URL
below:
http://eric-ide.python-projects.org
I'll test it now, any way I've read
On Tue, May 11, 2010 at 4:15 PM, André Pönitz andre.poen...@nokia.com wrote:
On Tuesday 11 May 2010 11:39:15 ext M. Bashir Al-Noimi wrote:
There is no real Python support in Creator.
However, there is some generic syntax highlighter in the works that also
covers Python, and Creator's
On May 11, 2010, at 12:38 PM, André Fillipe wrote:
On Tue, May 11, 2010 at 1:45 PM, Ed Sutton
esut...@fescorp.commailto:esut...@fescorp.com wrote:
I am not sure I understand. I am trying to make the Qt Creator project run
settings paths relative (no hard-coded absolute paths ). I want any
On 05/11/2010 10:39 PM, Ed Sutton wrote:
Obviously if I delete the .pro.user file I lose all Qt Project settings;
custom build steps, build environment, run settings, and run environment
settings. I had added an environment variable required by a 3rd-party
library to the run settings
Any tweaks you need should be coded inside the *.pro file.
True.
The qmake reference docs contain everything you need.
Quite the opposite: qmake is probably the worst documented part of Qt.
Try and search for any info on $$qtLibraryTarget, the fakelib
template, $$files and the such. I spent
On May 11, 2010, at 4:08 PM, André Fillipe wrote:
Any tweaks you need should be coded inside the *.pro file.
True.
The qmake reference docs contain everything you need.
Quite the opposite: qmake is probably the worst documented part of Qt.
Try and search for any info on $$qtLibraryTarget, the
I am totally unable to tell which part of your text is a quote and which
is something you wrote as a reply :-/
On 05/12/2010 01:54 AM, Ed Sutton wrote:
On May 11, 2010, at 4:08 PM, André Fillipe wrote:
Any tweaks you need should be coded inside the *.pro file.
True.
The qmake reference
24 matches
Mail list logo
