The Descent plugin for Eclipse provides an IDE for writing, launching and debugging code in D.

Explanations on how to get it from within Eclipse are here:

http://www.dsource.org/projects/descent

The new features for this release are:
 - Full autocompletion, which also writes the imports for you. No need to remember where that class or function you are looking for is located. Just start writing the name of it, press ctrl+space, select the suggestion, and the import is added at the top of the module automatically (no need to critic Tango anymore :-P). External variables does not participate in import-adding, because there are *so* many public ones...
 - Go to definition. It even works for opCall and magic array functions. :-)
 - Semantic highlighting: you can choose to color aliases, typdefs, classes, structs, interfaces, unions, templates, local variables, functions and function calls, etc., with different colors.
 - Showing of semantic errors. By default, some semantic errors are shown, like undefined identifiers or unresolved types. You can turn this off, or you can enable full semantic error reporting (but it will probably lie in some cases, that's why the default is "some"). It is recommended to turn this off for existing big projects, as it may cause more trouble than help.
 - Compile-time evaluation of functions and other properties: hovering over an element while holding ctrl+shift shows it's compile-time value. You can use this for built-in properties like init, min, max, sizeof, alignof, stringof, mangleof, length, constants, enum values and function calls (try writing a factorial function, then invoke it with a constant value somewhere in the code, and ctrl+shift+hover over the call). If the result of the evaluation is a string, and it is likely a declaration, it will have syntax highlighting and will be formatted according to your formatter preferences. This is useful for seeing the string passed to a mixin.
 - Graying out of inactive code: shows in gray code that is not reachable because of debug or version levels/identifiers and static ifs that evaluate to false.
 - Improved occurrences finder: selecting a token highlights all other tokens with the same semantic meaning. Then, pressing ctrl+2, r, allows you to rename all those occurrences. Very useful for renaming local variables, functions and types.
 - Declaration view: shows the source of the element under the cursor.

For current users: after you update the plugin, go to Windows -> Preferences, D -> Compiler, and change any setting. It will ask you to rebuild everything. You'll need to do this since I've changed the format of the indexes for searching stuff. Otherwise you'll get errors, or some things won't work.

And now, my personal comments about the current specification of D about developing an IDE for it:
 - Difficulty to suggest autocompletion for getters, and in particular setters. There's nothing in the language that says "this function is meant to be used as a setter". So currently, if you autocomplete a method that looks like a setter, you will get something like this: "var.member = |foo|", where you can start overwriting |foo|. While testing Descent, I found more setters that "procedures", and thus this decision.
 - Public imports are bad, bad, anyway you see it: they polute the global namespace, they make compilation slower (and also an IDE slower), they make finding the definition of a symbol harder (well, if you don't use an IDE). So if you use import foo.all, forget about getting good performance in Descent. Anyway, you won't need to use that, because Descent writes the imports for you.

Finally, as always with such an ambitious project, we need help! We're looking for testers, documentation writers, translators, and most of all developers. If you're interested in helping out, check out this page, which summarizes what we're looking for:

http://www.dsource.org/projects/descent/wiki/Development

Any suggestion, critic or bug report is welcome. You can use:
- the forums: http://www.dsource.org/forums/viewforum.php?f=107
- trac: http://www.dsource.org/projects/descent/report?action=new

Awesome project ... nice work you guys :)


"Ary Borenszweig" <ary@esperanto.org.ar> wrote in message news:fo63qt$8a2$1@digitalmars.com...
> The Descent plugin for Eclipse provides an IDE for writing, launching and debugging code in D.
>
> Explanations on how to get it from within Eclipse are here:
>
> http://www.dsource.org/projects/descent
>
> The new features for this release are:
>  - Full autocompletion, which also writes the imports for you. No need to
> remember where that class or function you are looking for is located. Just
> start writing the name of it, press ctrl+space, select the suggestion, and
> the import is added at the top of the module automatically (no need to
> critic Tango anymore :-P). External variables does not participate in
> import-adding, because there are *so* many public ones...
>  - Go to definition. It even works for opCall and magic array functions.
> :-)
>  - Semantic highlighting: you can choose to color aliases, typdefs,
> classes, structs, interfaces, unions, templates, local variables,
> functions and function calls, etc., with different colors.
>  - Showing of semantic errors. By default, some semantic errors are shown,
> like undefined identifiers or unresolved types. You can turn this off, or
> you can enable full semantic error reporting (but it will probably lie in
> some cases, that's why the default is "some"). It is recommended to turn
> this off for existing big projects, as it may cause more trouble than
> help.
>  - Compile-time evaluation of functions and other properties: hovering
> over an element while holding ctrl+shift shows it's compile-time value.
> You can use this for built-in properties like init, min, max, sizeof,
> alignof, stringof, mangleof, length, constants, enum values and function
> calls (try writing a factorial function, then invoke it with a constant
> value somewhere in the code, and ctrl+shift+hover over the call). If the
> result of the evaluation is a string, and it is likely a declaration, it
> will have syntax highlighting and will be formatted according to your
> formatter preferences. This is useful for seeing the string passed to a
> mixin.
>  - Graying out of inactive code: shows in gray code that is not reachable
> because of debug or version levels/identifiers and static ifs that
> evaluate to false.
>  - Improved occurrences finder: selecting a token highlights all other
> tokens with the same semantic meaning. Then, pressing ctrl+2, r, allows
> you to rename all those occurrences. Very useful for renaming local
> variables, functions and types.
>  - Declaration view: shows the source of the element under the cursor.
>
> For current users: after you update the plugin, go to Windows -> Preferences, D -> Compiler, and change any setting. It will ask you to rebuild everything. You'll need to do this since I've changed the format of the indexes for searching stuff. Otherwise you'll get errors, or some things won't work.
>
> And now, my personal comments about the current specification of D about
> developing an IDE for it:
>  - Difficulty to suggest autocompletion for getters, and in particular
> setters. There's nothing in the language that says "this function is meant
> to be used as a setter". So currently, if you autocomplete a method that
> looks like a setter, you will get something like this: "var.member =
> |foo|", where you can start overwriting |foo|. While testing Descent, I
> found more setters that "procedures", and thus this decision.
>  - Public imports are bad, bad, anyway you see it: they polute the global
> namespace, they make compilation slower (and also an IDE slower), they
> make finding the definition of a symbol harder (well, if you don't use an
> IDE). So if you use import foo.all, forget about getting good performance
> in Descent. Anyway, you won't need to use that, because Descent writes the
> imports for you.
>
> Finally, as always with such an ambitious project, we need help! We're looking for testers, documentation writers, translators, and most of all developers. If you're interested in helping out, check out this page, which summarizes what we're looking for:
>
> http://www.dsource.org/projects/descent/wiki/Development
>
> Any suggestion, critic or bug report is welcome. You can use:
> - the forums: http://www.dsource.org/forums/viewforum.php?f=107
> - trac: http://www.dsource.org/projects/descent/report?action=new

Awesomeness. Thank you for the hard work, looks like Descent is a *major* contribution to the development tools for D. Very exciting to see it evolve.

Ary Borenszweig pisze:
> The Descent plugin for Eclipse provides an IDE for writing, launching and debugging code in D.

Great work! Thanks!

BR
Marcin Kuszczak
Aarti_pl

what is the minimal eclipse download one has to choose to be able to use descent ?

Extrawurst escribió:
> what is the minimal eclipse download one has to choose to be able to use descent ?

Eclipse >= 3.2.1 and Java >= 1.5. See http://www.dsource.org/projects/descent/wiki/Installing

sure as if i did not look at this installing page.. the problem is, i never ever used eclipse and if i am representing the silly eclipse noob i am unsure what of the thousand possible download packages to choose from the eclipse download page. but after trying the standard java crap i tried the biggest package available and it worked... thanks



Ary Borenszweig schrieb:
> Extrawurst escribió:
>> what is the minimal eclipse download one has to choose to be able to use descent ?
>
> Eclipse >= 3.2.1 and Java >= 1.5. See http://www.dsource.org/projects/descent/wiki/Installing

looks like an awesome feature list! respect!
i have just one question, is the D2.x language supported aswell with all the nifty features?


Ary Borenszweig schrieb:
> The Descent plugin for Eclipse provides an IDE for writing, launching and debugging code in D.
>
> Explanations on how to get it from within Eclipse are here:
>
> http://www.dsource.org/projects/descent
>
> The new features for this release are:
>  - Full autocompletion, which also writes the imports for you. No need to remember where that class or function you are looking for is located. Just start writing the name of it, press ctrl+space, select the suggestion, and the import is added at the top of the module automatically (no need to critic Tango anymore :-P). External variables does not participate in import-adding, because there are *so* many public ones...
>  - Go to definition. It even works for opCall and magic array functions. :-)
>  - Semantic highlighting: you can choose to color aliases, typdefs, classes, structs, interfaces, unions, templates, local variables, functions and function calls, etc., with different colors.
>  - Showing of semantic errors. By default, some semantic errors are shown, like undefined identifiers or unresolved types. You can turn this off, or you can enable full semantic error reporting (but it will probably lie in some cases, that's why the default is "some"). It is recommended to turn this off for existing big projects, as it may cause more trouble than help.
>  - Compile-time evaluation of functions and other properties: hovering over an element while holding ctrl+shift shows it's compile-time value. You can use this for built-in properties like init, min, max, sizeof, alignof, stringof, mangleof, length, constants, enum values and function calls (try writing a factorial function, then invoke it with a constant value somewhere in the code, and ctrl+shift+hover over the call). If the result of the evaluation is a string, and it is likely a declaration, it will have syntax highlighting and will be formatted according to your formatter preferences. This is useful for seeing the string passed to a mixin.
>  - Graying out of inactive code: shows in gray code that is not reachable because of debug or version levels/identifiers and static ifs that evaluate to false.
>  - Improved occurrences finder: selecting a token highlights all other tokens with the same semantic meaning. Then, pressing ctrl+2, r, allows you to rename all those occurrences. Very useful for renaming local variables, functions and types.
>  - Declaration view: shows the source of the element under the cursor.
>
> For current users: after you update the plugin, go to Windows -> Preferences, D -> Compiler, and change any setting. It will ask you to rebuild everything. You'll need to do this since I've changed the format of the indexes for searching stuff. Otherwise you'll get errors, or some things won't work.
>
> And now, my personal comments about the current specification of D about developing an IDE for it:
>  - Difficulty to suggest autocompletion for getters, and in particular setters. There's nothing in the language that says "this function is meant to be used as a setter". So currently, if you autocomplete a method that looks like a setter, you will get something like this: "var.member = |foo|", where you can start overwriting |foo|. While testing Descent, I found more setters that "procedures", and thus this decision.
>  - Public imports are bad, bad, anyway you see it: they polute the global namespace, they make compilation slower (and also an IDE slower), they make finding the definition of a symbol harder (well, if you don't use an IDE). So if you use import foo.all, forget about getting good performance in Descent. Anyway, you won't need to use that, because Descent writes the imports for you.
>
> Finally, as always with such an ambitious project, we need help! We're looking for testers, documentation writers, translators, and most of all developers. If you're interested in helping out, check out this page, which summarizes what we're looking for:
>
> http://www.dsource.org/projects/descent/wiki/Development
>
> Any suggestion, critic or bug report is welcome. You can use:
> - the forums: http://www.dsource.org/forums/viewforum.php?f=107
> - trac: http://www.dsource.org/projects/descent/report?action=new

D 2.x is supported, but the semantic analysis is for 1.x. In fact, I just tried it, and if you write "invariant(int) x;" you get a lot of syntax errors, so D 2.x is not supported (tiny bug, I've just fixed it :-()

Extrawurst wrote:
> looks like an awesome feature list! respect!
> i have just one question, is the D2.x language supported aswell with all the nifty features?

1) ok well for D2.x Descents new features are pretty useless. even a HelloWorld is too much cause phobos in D2.x is full of strings which Descent doesnt seem to understand.

2) is there any documentation of the features in Descent besides the feature list where one can eventually find a shortcut how to use it. cause features like the formatter are just usable for new users when they find the shortcut for it in the preferences-options menu

Ary Borenszweig schrieb:
> D 2.x is supported, but the semantic analysis is for 1.x. In fact, I just tried it, and if you write "invariant(int) x;" you get a lot of syntax errors, so D 2.x is not supported (tiny bug, I've just fixed it :-()
>
> Extrawurst wrote:
>> looks like an awesome feature list! respect!
>> i have just one question, is the D2.x language supported aswell with all the nifty features?