kate lsp client plugin

[Dominik Haumann]

Hi Christoph,

please do so. Especially QTreeWidget should not be used anymore since it
ties the data model to QWidget code. It's always better to use QTreeView +
separate model. So from my point of view: +1

Thanks
Dominik

Christoph Cullmann <christoph at cullmann.io> schrieb am Fr., 19. Juli 2019,
21:11:

> Hi,
>
> > I pushed a few more commits with minor fixes and some refinements on
> > the diagnostics (jump list).  In particular, the list (selection)
> > should now also sync to the view (position).  So switching to another
> > view/document should scroll the relevant diagnostics into view, and
> > when positioned on a line with diagnostics, then that diagnostic will
> > be selected.  The latter is also (already previously) the case when
> > clicking on the border-icon mark.
>
> Nice.
>
> I would like to work a bit on the symbols views.
>
> A colleague mentioned it would be nice to have a filter like for the
> projects
> view. To make this "easy" feasible, I would convert the QTreeWidget code
> to use
> QTreeView and some model, perhaps even directly letting the LSPServer
> part
> create a usable QStandardItemModel for the symbols information.
>
> Would that be ok for you?
>
> >
> > Albeit with this minor detour/delay, next on to the preparation for
> > handling document revisions, TextEdit, etc (or anything else that pops
> > up in between .... ).
> :=) Cool!
>
> Greetings
> Christoph
>
> --
> Ignorance is bliss...
> https://cullmann.io | https://kate-editor.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwrite-devel/attachments/20190719/6c06bbed/attachment.html>