Hi!

I ported some code and features from Eclipse 3.4 and 3.5 to Descent, which are already present in the Java Development Toolkit for Eclipse (JDT). These features are:

- The popup is nicer when hovering a symbol, showing it's icon and allowing to open the ddoc view or the declaration.
- The popup also shows compile-time values of constant variables and enum members when available.
- The completion proposal list is nicer, showing the declaring type or module in grey (it's cleaner to the eyes). Also fields and methods are separated by ":" from their type.
- When hovering a method with ctrl hold, two options appear: "Open Declaration" and "Open Implementation". The first one just jumps to the method declaration. The second one opens a popup showing the classes or interfaces that implement that method, allowing you to quickly navigate to one of them. This is very useful when programming to interfaces.

Here's a video showing all of these things:

http://www.youtube.com/watch?v=Hy6-ppfq2pM

Enjoy!

Ary Borenszweig pisze:
> Hi!
> 
> I ported some code and features from Eclipse 3.4 and 3.5 to Descent, which are already present in the Java Development Toolkit for Eclipse (JDT). These features are:
> 
> - The popup is nicer when hovering a symbol, showing it's icon and allowing to open the ddoc view or the declaration.
> - The popup also shows compile-time values of constant variables and enum members when available.
> - The completion proposal list is nicer, showing the declaring type or module in grey (it's cleaner to the eyes). Also fields and methods are separated by ":" from their type.
> - When hovering a method with ctrl hold, two options appear: "Open Declaration" and "Open Implementation". The first one just jumps to the method declaration. The second one opens a popup showing the classes or interfaces that implement that method, allowing you to quickly navigate to one of them. This is very useful when programming to interfaces.
> 
> Here's a video showing all of these things:
> 
> http://www.youtube.com/watch?v=Hy6-ppfq2pM
> 
> Enjoy!

Thanks again!

I don't know if it's a platform specific problem but I cannot update Descent on my Ubuntu. I get this message:

An error occurred during provisioning.
  Failed to prepare partial IU: [R]descent.core 0.5.6.20090817.


Cheers
Piotrek

Piotrek wrote:
> Ary Borenszweig pisze:
>> Hi!
>>
>> I ported some code and features from Eclipse 3.4 and 3.5 to Descent, which are already present in the Java Development Toolkit for Eclipse (JDT). These features are:
>>
>> - The popup is nicer when hovering a symbol, showing it's icon and allowing to open the ddoc view or the declaration.
>> - The popup also shows compile-time values of constant variables and enum members when available.
>> - The completion proposal list is nicer, showing the declaring type or module in grey (it's cleaner to the eyes). Also fields and methods are separated by ":" from their type.
>> - When hovering a method with ctrl hold, two options appear: "Open Declaration" and "Open Implementation". The first one just jumps to the method declaration. The second one opens a popup showing the classes or interfaces that implement that method, allowing you to quickly navigate to one of them. This is very useful when programming to interfaces.
>>
>> Here's a video showing all of these things:
>>
>> http://www.youtube.com/watch?v=Hy6-ppfq2pM
>>
>> Enjoy!
> 
> Thanks again!
> 
> I don't know if it's a platform specific problem but I cannot update Descent on my Ubuntu. I get this message:
> 
> An error occurred during provisioning.
>   Failed to prepare partial IU: [R]descent.core 0.5.6.20090817.
> 
> 
> Cheers
> Piotrek

I can't enter dsource now. And yesterday I had to retry several times to upload the files. dsource is working very badly since yesterday, so that must be the problem. Please try again later. :)

What is the status of Descent's ability to build D projects? Last few times I checked I was unable to build my project so I was unable to use Descent, despite its wonderful code-completion abilities. Also is it able to run my build script (build.bat) and parse the output and create links to the errors?

Regards,
bobef

Ary Borenszweig Wrote:

> Hi!
> 
> I ported some code and features from Eclipse 3.4 and 3.5 to Descent, which are already present in the Java Development Toolkit for Eclipse (JDT). These features are:
> 
> - The popup is nicer when hovering a symbol, showing it's icon and
> allowing to open the ddoc view or the declaration.
> - The popup also shows compile-time values of constant variables and
> enum members when available.
> - The completion proposal list is nicer, showing the declaring type or
> module in grey (it's cleaner to the eyes). Also fields and methods are
> separated by ":" from their type.
> - When hovering a method with ctrl hold, two options appear: "Open
> Declaration" and "Open Implementation". The first one just jumps to the
> method declaration. The second one opens a popup showing the classes or
> interfaces that implement that method, allowing you to quickly navigate
> to one of them. This is very useful when programming to interfaces.
> 
> Here's a video showing all of these things:
> 
> http://www.youtube.com/watch?v=Hy6-ppfq2pM
> 
> Enjoy!

Ary Borenszweig wrote:

> http://www.youtube.com/watch?v=Hy6-ppfq2pM

Thanks Ary, i was waiting these features from a long time. :)

bobef wrote:
> What is the status of Descent's ability to build D projects? Last few times I checked I was unable to build my project so I was unable to use Descent, despite its wonderful code-completion abilities. Also is it able to run my build script (build.bat) and parse the output and create links to the errors?
> 
> Regards,
> bobef

You can configure an external tool like dmd, rebuild, dsss, and when run it'll show you the errors in the console and allow you to jump to them. So the answer is yes.

I'm also solve this soon:

http://www.dsource.org/forums/viewtopic.php?p=22877

Ary Borenszweig escribió:
> bobef wrote:
>> What is the status of Descent's ability to build D projects? Last few times I checked I was unable to build my project so I was unable to use Descent, despite its wonderful code-completion abilities. Also is it able to run my build script (build.bat) and parse the output and create links to the errors?
>>
>> Regards,
>> bobef
> 
> You can configure an external tool like dmd, rebuild, dsss, and when run it'll show you the errors in the console and allow you to jump to them. So the answer is yes.
> 
> I'm also solve this soon:
> 
> http://www.dsource.org/forums/viewtopic.php?p=22877

Solved! :)

Ary Borenszweig pisze:
> 
> I can't enter dsource now. And yesterday I had to retry several times to upload the files. dsource is working very badly since yesterday, so that must be the problem. Please try again later. :)

Works now! Yuppie!

Cheers
Piotrek

Hi Ary,

well done.

Here is a small bug report about the code fomatter:


=============================
import tango.io.Stdout;
import tango.core.Exception;

void main(char[][] args)
{
    try
    {
        /* Do some stuff */
    }
    catch (IOException ex)
    {
        Stdout.formatln("Caught IOException!");
    /* Consequence: Clean up and possibly try again. */
    } catch (Exception ex)
    {
        Stdout.formatln("Caught unexpected exception!");
    /* Consequence: Die as gracefully as possible. */
    }
}
=============================

You can see, the first catch-block is placed from a new line, but the second catch-block is not. Could you please fix this issue?

Thanks in advance.

Qian Xu wrote:
> Hi Ary,
> 
> well done.
> 
> Here is a small bug report about the code fomatter:
> 
> 
> =============================
> import tango.io.Stdout;
> import tango.core.Exception;
> 
> void main(char[][] args)
> {
>     try
>     {
>         /* Do some stuff */
>     }
>     catch (IOException ex)
>     {
>         Stdout.formatln("Caught IOException!");
>     /* Consequence: Clean up and possibly try again. */
>     } catch (Exception ex)
>     {
>         Stdout.formatln("Caught unexpected exception!");
>     /* Consequence: Die as gracefully as possible. */
>     }
> }
> =============================
> 
> You can see, the first catch-block is placed from a new line, but the second
> catch-block is not. Could you please fix this issue?
> 
> Thanks in advance.

The result I get, with brackets of try/catch/finally configured to the next line, is:

import tango.io.Stdout;
import tango.core.Exception;

void main(char[][] args) {
	try
	{
		/* Do some stuff */
	} catch(IOException ex)
	{
		Stdout.formatln("Caught IOException!");
	/* Consequence: Clean up and possibly try again. */
	} catch(Exception ex)
	{
		Stdout.formatln("Caught unexpected exception!");
	/* Consequence: Die as gracefully as possible. */
	}
}

What's your formatter configuration?