Some feedback from a new user

[Volker Wysk]

Am Sonntag, 10. Juli 2016, 21:00:54 CEST schrieben Sie:
> Hey Volker,
> 
> thanks for the feedback, it's always appreciated to get information on
> how a new user sees the application.
> 
> On 10/07/16 20:32, Volker Wysk wrote:
> > When I open a new file, I always have to enlarge the font, because the
> > standard font is very small.
> 
> For some reason the default fixed font size is quite small (across all
> applications though), just go change it in settings -> configure editor
> -> appearance -> font.

Okay, got it.


> > I hover the mouse over KConfigDialog, or use the Code Browser. There, the
> > documentation is shown. But it is just plain text, no formatting, although
> > the text contains tags.
> 
> That makes sense, I think. You probably don't want to render stuff the
> user types into his comments as HTML -- it could be invalid, it could be
> a code sample, or it could not be meant to be interpreted as HTML at
> all. We should leave the formatting to tools like doxygen.

I think it would be cool, if the rendered API documentation would be shown as 
long as the cursor isn't in the comment. When he enters the comment, it would 
go back to plain text. Here, you would be able to enter the Doxygen tags. It 
isn't needed to support HTML in comments. Just support the Doxygen tags. 


> > I jump to the declaration of KConfigDialog, and there is "class
> > KCONFIGWIDGETS_EXPORT KConfigDialog : public KPageDialog". I want to
> > browse
> > KPageDialog, but the following message appears: "Problem in Semantic
> > Analysis: Declaration not Found: KPageDialog".
> 
> Does it find the related include? Are your include paths set up correctly?

Gwenview compiled fine, with "make" from the command line (except for a few 
warnings). The compiler knows of all the include paths that it needs. Why 
doesn't know Kdevelop of those paths...?

Aside, I have once supplied an additional include path. But I can't find it 
right now.


> > "KPageDialog" also isn't accessible through the class browser.
> 
> That again makes sense because it's not a class which is part of the
> project; it's from the KConfigWidgets framework or something.

Isn't it obvious that users would want to browse the libraries in use? Just 
the API documentation, though.


> > But what I'm really missing, is support for properly browsing the
> > documentation. There ist the "documentation" tool, but I couldn't find out
> > how to use ist. I also couldn't find it in the KDevelop manual.
> 
> What documentation? 

In my case, the API docs of KF5, and of Qt.

> There is the documentation toolview, but that is for
> e.g. Qt's documentation. For the user-supplied code and its comments,
> the only way to browse it is through the navigation widget (the popup
> you can get by moving the mouse over an object or holding Alt).

Where is the documentation of the documentation tool?


So far. There are more cool features which come to my mind. Such as UML 
compliant class diagrams... ;-)

Thanks to the developers, for such an impressing piece of software.


V.W.