Re: [flux-dev] meeting minutes

[Jayaprakash Arthanareeswaran <jarthana@xxxxxxxxxx>]

> But that also
means to use JDT for multiple users at the same time, right? Isn’t that
be a 
> prerequisite or do you imagine a different way
of using headless JDT?

Absolutely. I don't think there can be two ways about
that. I was merely thinking aloud that this should be among
our top priority items.

Regards,
Jay



From:      
 Martin Lippert <mlippert@xxxxxxxxx>
To:      
 Jayaprakash Arthanareeswaran/India/IBM@IBMIN
Cc:      
 Flux developer discussions
<flux-dev@xxxxxxxxxxx>
Date:      
 07/14/2014 07:11 PM
Subject:    
   Re: [flux-dev]
meeting minutes

---

Hey Jay,

> As Alex rightly assessed, the problem is we have quite a lot of code
in the jdt.ui. Code completion is one example. As I pointed out in the
other example, we have some for Java doc hover too. 
> 
> Going forward, I see two main challenges for the Flux JDTservice:
> 
> 1. Extracting the code from JDT/UI and reusing or duplicating that
code in Flux's JDT service. 

+1

> 2. This in my opinion is even a bigger problem - making some of the
JDT features store and reuse data across workspaces. One of the biggest
feature affected will be search, as at this point, as, for example, we
will end up storing multiple indexes for the same JRE libraries for each
workspace/user. I don't know if this has been discussed already among the
Flux team. I think making the JDT features reuse such data will be key
if we want it to scale. 

+1

But that also means to use JDT for multiple users at the same time, right?
Isn’t that be a prerequisite or do you imagine a different way of using
headless JDT?

Cheers,
-Martin



> 
> Jay 
> 
> 
> 
> From:        Alex Boyko <aboyko@xxxxxxxxxxxxx>
> To:        Martin Lippert <mlippert@xxxxxxxxx>
> Cc:        Flux developer discussions <flux-dev@xxxxxxxxxxx>
> Date:        07/12/2014 04:56 AM 
> Subject:        Re: [flux-dev] meeting minutes
> Sent by:        flux-dev-bounces@xxxxxxxxxxx 
> 
> 
> 
> Hi Jay, 
> 
> I did some work around JDT Content Assist for Flux. I found as well
that a lot of the completion proposal code logic is implemented in subclasses
of IJavaCompletionProposal (ICompletionProposal which depends on Eclipse
UI) which are located in JDT UI plugin and are UI dependent. Also a lot
of the related code is located in packages under org.eclipse.jdt.internal.corext
which in JDT UI plugin as well. 
> I ended up extracting UI independent pieces of code from JDT UI and
implementing them in Flux JDT service. In fact one class i just copied
into Flux because it only had JDT Core dependent utilities. In other cases
i copied methods and adopted them for Flux (removed UI dependencies from
them). Would have been nice if majority of completion proposal logic from
JDT UI were in JDT Core. 
> Content assist in Flux seems to be close to the JDT content assist
now exceptions are keywords and templates i think. There is more work to
be done on Content Assist in Flux. It’s still in the prototype state.
All my content assist support work is delivered to master branch in org.eclipse.flux.jdt.service
plugin. 
> 
> Cheers, 
> Alex 
> 
> On Jul 9, 2014, at 4:11, Martin Lippert <mlippert@xxxxxxxxx>
wrote: 
> 
> Hey Jay,
> 
> Alex is also looking into options in the area of JDT and more advanced
content-assist, code-completion, quick-fixes, and refactorings.
> Maybe you both can work on this together? That would be wonderful.
> 
> Cheers,
> -Martin
> 
> 
> 
> 
> 
> 
> Thanks Martin! 
> 
> And the JDT hover support sounds nice. What about submitting a pull
request for this? Would be great! 
> 
> Well, I thought it's not in a good enough state to be in. It works
perfectly for binary elements, not so well for source elements. The reason
is (not just limited to this feature) there are quite a few nice features
that are programmed in JDT/UI, which we can't make use of at this point
-  "Javadoc from source files" is one example, code completion
being another. 
> 
> As I said earlier, looking forward to join the call from next week
on and be able to discuss more on these with the team. 
> 
> Regards, 
> Jay 
> 
> 
> 
> From:        Martin Lippert <mlippert@xxxxxxxxx>
> To:        Flux developer discussions <flux-dev@xxxxxxxxxxx>
> Date:        07/07/2014 09:07 PM 
> Subject:        Re: [flux-dev] meeting minutes
> Sent by:        flux-dev-bounces@xxxxxxxxxxx 
> 
> 
> 
> Hey Jay,
> 
> great to hear that you are looking into Flux, that is awesome. Especially
the headless JDT core services are in interesting area to explore further.
> Would be great to have you joining the calls, you are very welcome.
> 
> And the JDT hover support sounds nice. What about submitting a pull
request for this? Would be great!
> 
> Cheers,
> -Martin
> 
> 
> 
> 
> 
> I was meaning to join today's call but was bit confused about the
timing and joined late. But wasn't sure if I was on the right call, so
hung up.   
> Anyway, just wanted to say that, I have managed to get it up and running,
played around a bit. I find Flux to be very impressive. I also like the
idea of being able to leverage the headless JDT core services to provide
Java tooling capabilities. 
> 
> I am looking forward to join the call from next week on and contribute
to the effort. Meanwhile, I will think about some low hanging fruits from
JDT Core, like the Javadoc hover I have added here: 
> 
> https://github.com/jarthana/flux.git
> 
> This is just a first-cut by no means complete, just a result of my
experiments. To view Javadoc for an element, place the cursor on the element
and press F2. 
> 
> Regards, 
> Jay 
> 
> 
> 
> From:        Martin Lippert <mlippert@xxxxxxxxx>
> To:        Flux developer discussions <flux-dev@xxxxxxxxxxx>
> Date:        07/03/2014 10:07 PM 
> Subject:        [flux-dev] meeting minutes 
> Sent by:        flux-dev-bounces@xxxxxxxxxxx 
> 
> 
> 
> from todays call:
> https://wiki.eclipse.org/Flux/Meeting_minutes/20140703
> 
> Cheers,
> -Martin
> 
> 
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev
> 
> 
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev
> 
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev
> 
> 
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev
> 
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev