RE: [julia-users] Announcing JuDE: autocomplete and jump to definition support for Atom

2016-03-29 Thread David Anthoff 
+1 I’m also much more interested in a simple install story for an existing Atom 
installation than a standalone juno bundle.

 

From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
Behalf Of Tomas Lycken
Sent: Tuesday, March 29, 2016 2:39 PM
To: julia-users 
Subject: Re: [julia-users] Announcing JuDE: autocomplete and jump to definition 
support for Atom

 

It would be nice, though, if it were somewhere documented - or even better, a 
meta-package with dependencies on all the others - to allow turning an already 
existing Atom installation into a Julia IDE too. I'd be much more interested in 
improving an editor I'm already using for other thing, than in installing yet 
another atom-sublime-vscode-like (they all look the same nowadays...) editor 
just to get the Julia goodness.

 

This is, of course and as already noted, definitely not urgent, but I think it 
should be on the road map.

 

// T

On Monday, March 28, 2016 at 10:26:06 PM UTC+2, Jonathan Malmaud wrote:

Mike can step in, but I think it is indeed the plan to have a Julia IDE bundle, 
causing the exact packages required on the julia and atom side to be invisible 
implementation details from the user's POV.

On Monday, March 28, 2016 at 1:27:01 PM UTC-4, David Anthoff wrote:

I think the user experience for almost all people would be much easier if they 
install Atom, then add one package for julia support and everything works. 
Having multiple Atom packages (julia-language, ink, julia-client, 
latex-completion and Jude right now) makes things confusing for most people, 
installation a pain and most people probably won’t even discover all of these 
packages.

 

Maybe another solution to this would be to eventually have one “juno” package 
that automatically installs all the individual useful plugins for Atom that 
make it a good julia IDE. I also don’t think any of this is urgent, right now 
the whole Atom story is so experimental in any case that most likely only a 
small number of people is using it in the first place.

 

From:  <mailto:julia...@googlegroups.com> julia...@googlegroups.com [ 
<mailto:julia...@googlegroups.com> mailto:julia...@googlegroups.com] On Behalf 
Of James Dang
Sent: Sunday, March 27, 2016 4:57 AM
To: julia-users < <mailto:julia...@googlegroups.com> julia...@googlegroups.com>
Subject: Re: [julia-users] Announcing JuDE: autocomplete and jump to definition 
support for Atom

 

Hi David, I think Jude's functionality is pretty orthogonal to julia-client so 
they function pretty well as distinct, easier to manage packages. julia-client 
is focused on live code execution and results visualization while Jude is more 
about getting traditional IDE tools via static syntax analysis. Why do you 
think they should merge?

Re: [julia-users] Announcing JuDE: autocomplete and jump to definition support for Atom

2016-03-29 Thread Tomas Lycken 
It would be nice, though, if it were somewhere documented - or even better, 
a meta-package with dependencies on all the others - to allow turning an 
already existing Atom installation into a Julia IDE *too*. I'd be much more 
interested in improving an editor I'm already using for other thing, than 
in installing yet another atom-sublime-vscode-like (they all look the same 
nowadays...) editor just to get the Julia goodness.

This is, of course and as already noted, definitely not urgent, but I think 
it should be on the road map.

// T

On Monday, March 28, 2016 at 10:26:06 PM UTC+2, Jonathan Malmaud wrote:
>
> Mike can step in, but I think it is indeed the plan to have a Julia IDE 
> bundle, causing the exact packages required on the julia and atom side to 
> be invisible implementation details from the user's POV.
>
> On Monday, March 28, 2016 at 1:27:01 PM UTC-4, David Anthoff wrote:
>>
>> I think the user experience for almost all people would be much easier if 
>> they install Atom, then add one package for julia support and everything 
>> works. Having multiple Atom packages (julia-language, ink, julia-client, 
>> latex-completion and Jude right now) makes things confusing for most 
>> people, installation a pain and most people probably won’t even discover 
>> all of these packages.
>>
>>  
>>
>> Maybe another solution to this would be to eventually have one “juno” 
>> package that automatically installs all the individual useful plugins for 
>> Atom that make it a good julia IDE. I also don’t think any of this is 
>> urgent, right now the whole Atom story is so experimental in any case that 
>> most likely only a small number of people is using it in the first place.
>>
>>  
>>
>> *From:* julia...@googlegroups.com [mailto:julia...@googlegroups.com] *On 
>> Behalf Of *James Dang
>> *Sent:* Sunday, March 27, 2016 4:57 AM
>> *To:* julia-users 
>> *Subject:* Re: [julia-users] Announcing JuDE: autocomplete and jump to 
>> definition support for Atom
>>
>>  
>>
>> Hi David, I think Jude's functionality is pretty orthogonal to 
>> julia-client so they function pretty well as distinct, easier to manage 
>> packages. julia-client is focused on live code execution and results 
>> visualization while Jude is more about getting traditional IDE tools via 
>> static syntax analysis. Why do you think they should merge?
>>
>

Re: [julia-users] Announcing JuDE: autocomplete and jump to definition support for Atom

2016-03-28 Thread Jonathan Malmaud 
Mike can step in, but I think it is indeed the plan to have a Julia IDE 
bundle, causing the exact packages required on the julia and atom side to 
be invisible implementation details from the user's POV.

On Monday, March 28, 2016 at 1:27:01 PM UTC-4, David Anthoff wrote:
>
> I think the user experience for almost all people would be much easier if 
> they install Atom, then add one package for julia support and everything 
> works. Having multiple Atom packages (julia-language, ink, julia-client, 
> latex-completion and Jude right now) makes things confusing for most 
> people, installation a pain and most people probably won’t even discover 
> all of these packages.
>
>  
>
> Maybe another solution to this would be to eventually have one “juno” 
> package that automatically installs all the individual useful plugins for 
> Atom that make it a good julia IDE. I also don’t think any of this is 
> urgent, right now the whole Atom story is so experimental in any case that 
> most likely only a small number of people is using it in the first place.
>
>  
>
> *From:* julia...@googlegroups.com  [mailto:
> julia...@googlegroups.com ] *On Behalf Of *James Dang
> *Sent:* Sunday, March 27, 2016 4:57 AM
> *To:* julia-users >
> *Subject:* Re: [julia-users] Announcing JuDE: autocomplete and jump to 
> definition support for Atom
>
>  
>
> Hi David, I think Jude's functionality is pretty orthogonal to 
> julia-client so they function pretty well as distinct, easier to manage 
> packages. julia-client is focused on live code execution and results 
> visualization while Jude is more about getting traditional IDE tools via 
> static syntax analysis. Why do you think they should merge?
>

RE: [julia-users] Announcing JuDE: autocomplete and jump to definition support for Atom

2016-03-28 Thread David Anthoff 
I think the user experience for almost all people would be much easier if they 
install Atom, then add one package for julia support and everything works. 
Having multiple Atom packages (julia-language, ink, julia-client, 
latex-completion and Jude right now) makes things confusing for most people, 
installation a pain and most people probably won’t even discover all of these 
packages.

 

Maybe another solution to this would be to eventually have one “juno” package 
that automatically installs all the individual useful plugins for Atom that 
make it a good julia IDE. I also don’t think any of this is urgent, right now 
the whole Atom story is so experimental in any case that most likely only a 
small number of people is using it in the first place.

 

From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
Behalf Of James Dang
Sent: Sunday, March 27, 2016 4:57 AM
To: julia-users 
Subject: Re: [julia-users] Announcing JuDE: autocomplete and jump to definition 
support for Atom

 

Hi David, I think Jude's functionality is pretty orthogonal to julia-client so 
they function pretty well as distinct, easier to manage packages. julia-client 
is focused on live code execution and results visualization while Jude is more 
about getting traditional IDE tools via static syntax analysis. Why do you 
think they should merge?

Re: [julia-users] Announcing JuDE: autocomplete and jump to definition support for Atom

2016-03-27 Thread James Dang 
Hi David, I think Jude's functionality is pretty orthogonal to julia-client 
so they function pretty well as distinct, easier to manage packages. 
julia-client is focused on live code execution and results visualization 
while Jude is more about getting traditional IDE tools via static syntax 
analysis. Why do you think they should merge?

RE: [julia-users] Announcing JuDE: autocomplete and jump to definition support for Atom

2016-03-24 Thread David Anthoff 
Very nice!

 

Any chance that this could just become part of julia-client at some point?

 

From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
Behalf Of James Dang
Sent: Sunday, March 20, 2016 11:58 AM
To: julia-users 
Subject: [julia-users] Announcing JuDE: autocomplete and jump to definition 
support for Atom

 

Hi All, Julia has been great for me, and I wanted to give back a little. 
LightTable and Atom are great editors, but I was really starting to miss good 
intellisense-like autocomplete and basic navigation features like 
jump-to-definition, especially on larger codebases. It's really quite a slog to 
remember exactly where in which file a function was defined, or what its exact 
arguments are. And maybe with better tooling, more people will be drawn to the 
community. So I put a bit of work into a new package for Atom that gives you 
that!

https://atom.io/packages/jude

 <https://raw.githubusercontent.com/jamesdanged/Jude/master/img/JudeDemo.gif> 



This is a bit different from what you get out of julia-client and 
autocomplete-julia because it does a full syntax parsing and scope resolution 
of your codebase without executing it in a Julia process. It reparses very 
quickly on the fly without needing to save. And the matching is precise, not 
fuzzy, giving you exactly what names are available in the scope you are in 
currently. It's quite new and unpolished, but please try it out and let me know 
what you think!

Cheers,
James

[julia-users] Announcing JuDE: autocomplete and jump to definition support for Atom

2016-03-20 Thread James Dang 
Hi All, Julia has been great for me, and I wanted to give back a little. 
LightTable and Atom are great editors, but I was really starting to miss 
good intellisense-like autocomplete and basic navigation features like 
jump-to-definition, especially on larger codebases. It's really quite a 
slog to remember exactly where in which file a function was defined, or 
what its exact arguments are. And maybe with better tooling, more people 
will be drawn to the community. So I put a bit of work into a new package 
for Atom that gives you that!

https://atom.io/packages/jude




This is a bit different from what you get out of julia-client and 
autocomplete-julia because it does a full syntax parsing and scope 
resolution of your codebase without executing it in a Julia process. It 
reparses very quickly on the fly without needing to save. And the matching 
is precise, not fuzzy, giving you exactly what names are available in the 
scope you are in currently. It's quite new and unpolished, but please try 
it out and let me know what you think!

Cheers,
James