[Qt-creator] my cheers, and two cents

[Thorbjørn Lindeijer]

ext Nathan Carter wrote:
> 1. What's a task list?  I can get to it with the button next to
> QuickOpen, but I can't add a task, and can't find documentation on
> this.  Is it searching my source files for some secret incantation
> like "TO DO"?

I guess this is a concept that came from Visual Studio (not sure 
though). You're not the only one confused by the terminology here. I'm 
not sure if we should extend its functionality, or just rename it. I do 
think automatically searching for all TODO entries in source code would 
be a nice feature, though it's easy enough to just press Ctrl+Shift+F 
and do it yourself. :-)

> 2. Is it intentional that the syntax highlighting treats the Q_OBJECT
> macro as if it were a C++ type?

We decided to go with it until we have proper highlighting for macros. 
We plan to highlight macros specifically in the future, in which case 
these will also be highlighted as such instead of as keywords.

> 4. Can we get continued video tutorials as features are added?  I
> found the intro tutorials a perfect high-level intro, from which I
> began experimenting on my own and reading help on an as-needed basis.
> It would be great if as new chunks of features are added (code
> refactoring tools, etc.) that we see an overview of them in new video
> tutorials.  This really gives the learning curve a smackdown, IMO.

For sure we'll have some more videos later. :-)

> 5. When I press Ctrl+R to run the app, can't Qt Creator jump to Output
> mode, rather than opening up a baby output mode at the bottom of edit
> mode?  This should especially be true if it's a console app, such as
> those I interact with regularly when doing unit testing via QtTest.

Yep, this would be a nice option.

> 6. Bug: I checked the preference box for showing a word wrap marker at
> column 80, but it doesn't seem to show up, instead just slightly
> graying everything from column 0 to the right.

Hmm, can't reproduce. Maybe a problem with your font? Can you try 
selecting another one? Sounds like it might be having problems 
determining how wide 80 characters are.

> 9. Support for Doxygen comments would be excellent, or at the very
> least the trivial feature of preserving the initial * on a line when I
> press enter.  That is, if I'm at the point
>         /** foo bar baz bash
>          *  hubbly bubbly [and I press enter here]
> then give me a line like
>           *  [cursor here]
> as the next line.  Eventually, it would be great if Doxygen-generated
> documentation took on the same status in QtCreator's help as the built-
> in Qt help does.  I.e., I can push a button to call Doxygen on my
> Doxyfile, and rebuild the help which then gets re-indexed, and F1-ing
> a class I've defined opens that generated page in the help window.

I'm very much with you here. The Doxygen integration might make for a 
nice plugin. :-)

Regards,
Bjørn

-- 
Thorbjørn Lindeijer
Software Engineer
Nokia, Qt Software