public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: Kawa mailing list <kawa@sourceware.org>
Subject: Re: language server protocol for Kawa
Date: Fri, 12 Jan 2018 22:32:00 -0000	[thread overview]
Message-ID: <CABgWrqq6XHB_2sfDTvFieT=ggpK=KcXaKOYahO1xPZLZxqR8jw@mail.gmail.com> (raw)
In-Reply-To: <78c36015-ce0d-a0cf-c81e-37f0ce4d8e9a@bothner.com>

Hello Per,

i started doing this a few months ago, but I didn't get very far at all.

Perhaps it's because of how I tried to do it - I looked at
https://github.com/palantir/language-servers and
https://github.com/eclipse/lsp4j and tried to implement the
LanguageClientAware and LanguageServer interfaces.

The Groovy implementation is here -
https://github.com/palantir/language-servers/blob/develop/groovy-language-server/src/main/java/com/palantir/ls/groovy/GroovyLanguageServer.java

It was difficult to know if I'm making progress, because it seemed
like all the things needed to come together all at the same time.

If you're jumping into working on an LSP implementation, I'd love to
contribute on GitLab if you can post issues with tasks for others to
complete.



Duncan.

On Fri, Jan 12, 2018 at 5:04 PM, Per Bothner <per@bothner.com> wrote:
> Has anyone done any work for a Language Server Protocol
> (https://langserver.org/) for Kawa? Any insights or partial code?
>
> I ask because I'm getting ready to jump into this as the next major
> project for Kawa.
>
> (I do have one non-trivial bug It want to resolve first:
> GitLab issue #33 and Savannah bug #52390, which are probably both related to
> the fix for issue #11).
> --
>         --Per Bothner
> per@bothner.com   http://per.bothner.com/



-- 
Duncan.

  reply	other threads:[~2018-01-12 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 22:04 Per Bothner
2018-01-12 22:32 ` Duncan Mak [this message]
2018-01-13  0:59   ` Per Bothner
2018-01-14 20:07 ` Helmut Eller
2018-01-14 20:35   ` Per Bothner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABgWrqq6XHB_2sfDTvFieT=ggpK=KcXaKOYahO1xPZLZxqR8jw@mail.gmail.com' \
    --to=duncanmak@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).