Qt Creator and other tools

[quote author="Smar" date="1281084862"]CMake's syntax is a bit unintuitive and if you need to do anything besides declarations, it gets pretty messy unless you want to put quite a bit time to write modules...

Or that's how I think about it.
[/quote]

Ok, Smar, this is an option form in CMake for build/update translations.

@option (UPDATE_TRANSLATIONS "Update source translation *.ts files (WARNING: make clean will delete the source .ts files! Danger!)")

if (UPDATE_TRANSLATIONS)
QT4_CREATE_TRANSLATION(QM_FILES ${TRANSLATIONS})
else (UPDATE_TRANSLATIONS)
QT4_ADD_TRANSLATION(QM_FILES ${TRANSLATIONS})
endif (UPDATE_TRANSLATIONS) @

What replacement for it will be in QtScript as buldsystem or other stuff?

Can we try to have QML based CSS editor with declarative formatting ON / OFF .

The editor should be smart enough to recognize tag values for formatting as some piece of code may need time to time formatting some may not.

I've added some stuff to the plugin last few days, it's probably worth doing a checkout :)

(documentation in implementation files, generate documentation for a whole file)

MariusG, oops, this undocumented tag slightly crashed design ;)

DrGreg, yeah you should use "a" tag to make it working.

Showing external pages still doesn't work for me .. related thread here: http://developer.symbian.org/forum/showthread.php?t=6340

Antonio -

Thanks for the reply... and bloody clever on the Qt developer's part.

again, thanks - greg

Thanks.

Try running master: That has a great class browser contributed by Denis Mingulov:-) Unfortunately I do not think that this code can be backported to 2.0/2.1 since it uses the C++ engine which had quite some improvements since the 2.0/2.1 branch was made.

I think that is not the same class browser shown at the link you provided though. So maybe that one was ported to 2.0? I do not know who wrote that plugin, so I can't tell, sorry.

Thank you. I have issued a wishlist bug.

Bingo!!! That was the solution.

Thank you very much for your help :O)

Creator 2.0 should only show those version control entries that are relevant for the current project. So the perforce entry should show up once you have a project open which is managed by perforce.

Is that is not the case then you "should report a bug":http://bugreports.qt.nokia.com/.

thank you for your help, in the "bugreport" if everything written thats importen for this problem.

solved

"Bugreport added":http://bugreports.qt.nokia.com/browse/QTCREATORBUG-1896

[quote author="DrMaboule" date="1279318875"]I fact you could declare more than one variable using this code:

QObject *pParent = NULL, *pParent2 = NULL; // Two pointer

But is différent from

QObject *pParent = NULL, pParent; // One pointer and a none pointer object.

This is something I don't do anyway. I would call this a code smell on its own.
[/quote]
[quote]
QObject pParent : The variable is a pointer on a objet of type QObject. QObject is not a class but a pointer on a class. The variable is a pointer, so * should be next the variable.
[/quote]

You are right, QObject* is not a class, but a pointer to a class. But it is atype.

[quote]
Don't you agreed?
[/quote]
Obviously no, but it is a matter of taste. I'll agree to Tobias Hunger that you should be consistent
to the code at hand and for my code it's T* name

lyuts thank you for the info.

ONe of the big disadvantages of IRC is that both the questions and the answers get lost. Forums and mailing-lists however archive both and can be searched.

It depends on the issue of course but building a knowledge base over time makes a lot of sense to me...

[quote author="anselmolsm" date="1278623614"]AFAIK all you need to build Qt on Windows is listed at:
http://doc.qt.nokia.com/4.7-snapshot/requirements-win.html

If you have any specific problem, post here so we can help you =)[/quote]

Yeah, I forgot perl.

Thanks for the link.

I added a comment asking whether they considered having their translation merger back into creator. At least I hope I did... since I could not really read anything on that page:-)

Yeah, I'm voting for leaving two different modes, it makes development and debugging more flexible. I'm thinking that automatic switching should be done to mode that was last. For example, if you were in design view and started debugging than after end of debugging it should switch back to design view. But if you were in edit view, started debugging, manually switched to design view, after it switched back to debug view and finished session than it should switch to design view. Not sure that it is reasonable to switch to such views as project or documentation.