Re: KDevelop problems suitable for a Ph.D. thesis

Πέτρος Σιλιγκούνας <[email protected]> Wed, 4 Sep 2024 00:35:37 +0300
Newsgroups gmane.comp.kde.devel.kdevelop
Message-ID <CAKQ0YYz8o+FgPvrODcywzahrY+Oi8mhg9+ECJ3nf9hFHdjo5Dg@mail.gmail.com>
--0000000000005489f706213dd774
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, I hope you find your thesis theme soon. I would propose kdevelop
zealdoc plugin which needs some modifications to compile.

Another nice addition would be finishing the plugin for showing code meta
information with inline notes.[1] [2]

I hope all the best

[1] https://kate-editor.org/2018/08/17/kate-gains-support-for-inline-notes/

[2] https://github.com/michalsrb/kdev-sourceinfo

=CE=A3=CF=84=CE=B9=CF=82 =CE=A4=CF=81=CE=AF 3 =CE=A3=CE=B5=CF=80 2024, 3:24=
 =CE=BC.=CE=BC. =CE=BF =CF=87=CF=81=CE=AE=CF=83=CF=84=CE=B7=CF=82 Igor Kush=
nir <[email protected]>
=CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:

> Hi everyone!
>
> I am urgently looking for a computer science Ph.D. thesis theme. I'd like
> to
> solve some important and challenging KDevelop problem(s), write scientifi=
c
> papers and a thesis about them. Any ideas?
>
> I have considered integrating Language Server Protocol (LSP). But based o=
n
>
> https://commits.kde.org/kdevelop?path=3Dkdevplatform/language/duchain/Mai=
npage.dox
> ,
> https://microsoft.github.io/language-server-protocol/overviews/lsp/overvi=
ew/
> and
>
> https://microsoft.github.io/language-server-protocol/specifications/lsp/3=
.17/specification/
> , I conclude that proper integration into existing KDevelop
> language/duchain
> framework is impossible. For one thing, a LSP server reply does not
> group/structure declarations in nested scopes, which is necessary to fill
> duchain context hierarchy. LSP can be integrated separately from duchain,
> similarly to but more thoroughly than Kate's LSP plugin, which could be a
> very
> good starting point. However, I expect such an undertaking to consist
> almost
> exclusively of plugin/library/protocol integration work rather than
> interesting
> new algorithms or algorithm improvements/adaptations worthy of scientific
> papers.
>
> The following two merge requests represent my KDevelop work that comes
> closest
> to what I am looking for:
> https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/224 and
> https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/118 . But both
> are
> fairly small and mostly complete. Not much need or room for improvement i=
s
> left
> there.
>
> Thank you,
> Igor
>

--0000000000005489f706213dd774
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><p dir=3D"ltr">Hi, I hope you find your thesis theme soon=
. I would propose kdevelop zealdoc plugin which needs some modifications to=
 compile.</p>
<p dir=3D"ltr">Another nice addition would be finishing the plugin for show=
ing code meta information with inline notes.[1] [2]</p>
<p dir=3D"ltr">I hope all the best </p>
<p dir=3D"ltr">[1] <a href=3D"https://kate-editor.org/2018/08/17/kate-gains=
-support-for-inline-notes/">https://kate-editor.org/2018/08/17/kate-gains-s=
upport-for-inline-notes/</a> </p><p dir=3D"ltr">[2]=C2=A0<a href=3D"https:/=
/github.com/michalsrb/kdev-sourceinfo">https://github.com/michalsrb/kdev-so=
urceinfo</a></p></div>
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=CE=A3=
=CF=84=CE=B9=CF=82 =CE=A4=CF=81=CE=AF 3 =CE=A3=CE=B5=CF=80 2024, 3:24 =CE=
=BC.=CE=BC. =CE=BF =CF=87=CF=81=CE=AE=CF=83=CF=84=CE=B7=CF=82 Igor Kushnir =
&lt;<a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"noreferre=
r">[email protected]</a>&gt; =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Hi everyone!<br>
<br>
I am urgently looking for a computer science Ph.D. thesis theme. I&#39;d li=
ke to <br>
solve some important and challenging KDevelop problem(s), write scientific =
<br>
papers and a thesis about them. Any ideas?<br>
<br>
I have considered integrating Language Server Protocol (LSP). But based on =
<br>
<a href=3D"https://commits.kde.org/kdevelop?path=3Dkdevplatform/language/du=
chain/Mainpage.dox" rel=3D"noreferrer noreferrer noreferrer" target=3D"_bla=
nk">https://commits.kde.org/kdevelop?path=3Dkdevplatform/language/duchain/M=
ainpage.dox</a> <br>
, <a href=3D"https://microsoft.github.io/language-server-protocol/overviews=
/lsp/overview/" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">=
https://microsoft.github.io/language-server-protocol/overviews/lsp/overview=
/</a> <br>
and <br>
<a href=3D"https://microsoft.github.io/language-server-protocol/specificati=
ons/lsp/3.17/specification/" rel=3D"noreferrer noreferrer noreferrer" targe=
t=3D"_blank">https://microsoft.github.io/language-server-protocol/specifica=
tions/lsp/3.17/specification/</a> <br>
, I conclude that proper integration into existing KDevelop language/duchai=
n <br>
framework is impossible. For one thing, a LSP server reply does not <br>
group/structure declarations in nested scopes, which is necessary to fill <=
br>
duchain context hierarchy. LSP can be integrated separately from duchain, <=
br>
similarly to but more thoroughly than Kate&#39;s LSP plugin, which could be=
 a very <br>
good starting point. However, I expect such an undertaking to consist almos=
t <br>
exclusively of plugin/library/protocol integration work rather than interes=
ting <br>
new algorithms or algorithm improvements/adaptations worthy of scientific p=
apers.<br>
<br>
The following two merge requests represent my KDevelop work that comes clos=
est <br>
to what I am looking for: <br>
<a href=3D"https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/224" r=
el=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://invent.kd=
e.org/kdevelop/kdevelop/-/merge_requests/224</a> and <br>
<a href=3D"https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/118" r=
el=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://invent.kd=
e.org/kdevelop/kdevelop/-/merge_requests/118</a> . But both are <br>
fairly small and mostly complete. Not much need or room for improvement is =
left <br>
there.<br>
<br>
Thank you,<br>
Igor<br>
</blockquote></div>

--0000000000005489f706213dd774--