On Tuesday, 29 January 2013 at 09:42:49 UTC, Timon Gehr wrote:
> On 01/29/2013 03:14 AM, alex wrote:
>> On Tuesday, 29 January 2013 at 00:48:24 UTC, F i L wrote:
>>> ...
>> http://mono-d.alexanderbothe.com/?attachment_id=817
>> My progress so far. Lots of internals to manage though. The
>> execute-button isn't implemented yet but you can toggle the
>> "Automatically take the mixin at the caret location" button.
>> Concerning things like foo(1,2) - yes, the evaluation engine
>> directly takes the symbols straight out of its parsed modules. So
>> as you create a method body you'll be able to execute stuff
>> in-line. But yeah, remember that CTFE isn't implemented yet ;) -
>> Perhaps I'll do/finish it during the next GSoC.
>> ...
>
> Probably you should do JIT using System.Reflection.Emit.

Why not write an entire D# compiler? ;)
(jk, I originally planned to do this right after I've finished
mono-d :D)

On Tuesday, 29 January 2013 at 08:02:27 UTC, Jacob Carlborg wrote:
>> ...
> Yeah, that was soooo cool. I also liked the code bubbles. Instead of having a file as the minimum abstraction unit in the IDE/editor it was a function/class/method.

Which can be done in Eclipse by just selecting e.g. a method or class in the outline - iirc it'll just show the definition of the selected node then, nothing else.

On 2013-01-29 11:52, alex wrote:

> Which can be done in Eclipse by just selecting e.g. a method or class in
> the outline - iirc it'll just show the definition of the selected node
> then, nothing else.

If I select an item in the outline view it will just scroll the editor view to where that item is defined.

I want to be able to have three code bubbles open, side by side, showing three different methods from the same file.

-- 
/Jacob Carlborg

On 29/01/2013 10:52, alex wrote:
> On Tuesday, 29 January 2013 at 08:02:27 UTC, Jacob Carlborg wrote:
>>> ...
>> Yeah, that was soooo cool. I also liked the code bubbles. Instead of
>> having a file as the minimum abstraction unit in the IDE/editor it was
>> a function/class/method.
>
> Which can be done in Eclipse by just selecting e.g. a method or class in
> the outline - iirc it'll just show the definition of the selected node
> then, nothing else.

By default, yes, but you can do what Jacob wanted with the "Show Source of Selected Element Only" functionality:
http://help.eclipse.org/juno/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm

I personally don't like that feature that much, at least the way it's implemented, because that toggle is global, it will affect all Java editors. Plus it requires the use of the outline view (which I dont typically use), or the package explorer to select the element. I would much rather have the underlying elemented defined *per editor*, (and thus independent of selection).

-- 
Bruno Medeiros - Software Engineer

On 2013-01-29 13:26, Bruno Medeiros wrote:

> By default, yes, but you can do what Jacob wanted with the "Show Source
> of Selected Element Only" functionality:
> http://help.eclipse.org/juno/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm

That's somewhat similar to what I had in mind. But that just removes all other code that is not selected from the editor. I want to have multiple editors or views of the same file side by side. These views don't need to be any larger than the code they're showing.

-- 
/Jacob Carlborg

On Tuesday, 29 January 2013 at 19:35:45 UTC, Jacob Carlborg wrote:
> On 2013-01-29 13:26, Bruno Medeiros wrote:
>
>> By default, yes, but you can do what Jacob wanted with the "Show Source
>> of Selected Element Only" functionality:
>> http://help.eclipse.org/juno/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm
>
> That's somewhat similar to what I had in mind. But that just removes all other code that is not selected from the editor. I want to have multiple editors or views of the same file side by side. These views don't need to be any larger than the code they're showing.

Okay, I've uploaded a new version that features a basically working version. There is now a separated mixin insight and expression evaluation available.
There are still many things left to do though.

On 2013-01-30 00:28, alex wrote:

> Okay, I've uploaded a new version that features a basically working
> version. There is now a separated mixin insight and expression
> evaluation available.
> There are still many things left to do though.

I'll give it a try.

-- 
/Jacob Carlborg

On Wednesday, 30 January 2013 at 10:45:26 UTC, Jacob Carlborg
wrote:
> On 2013-01-30 00:28, alex wrote:
>
>> Okay, I've uploaded a new version that features a basically working
>> version. There is now a separated mixin insight and expression
>> evaluation available.
>> There are still many things left to do though.
>
> I'll give it a try.

I'm currently too tired to start a new thread for announcing
another bug fix release:
http://mono-d.alexanderbothe.com/?p=825

On Tuesday, 29 January 2013 at 19:35:45 UTC, Jacob Carlborg wrote:
> On 2013-01-29 13:26, Bruno Medeiros wrote:
>
>> By default, yes, but you can do what Jacob wanted with the "Show Source
>> of Selected Element Only" functionality:
>> http://help.eclipse.org/juno/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm
>
> That's somewhat similar to what I had in mind. But that just removes all other code that is not selected from the editor. I want to have multiple editors or views of the same file side by side. These views don't need to be any larger than the code they're showing.

When on Eclipse I tend to use the Java browsing perspective.

http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2FgettingStarted%2Fqs-Browsing.htm

It brings back memories when I used Smalltalk at the university. :)

--
Paulo