I just pushed a new release of workspace-d (bridge between DCD, DScanner, dfmt and dub with some utility stuff) and code-d (my vscode D extension using workspace-d).

The latest update features several smaller additions such as better auto completion for DlangUI Markup Language and more configurability.

As an addition I am starting to bundle .deb files and precompiled windows binaries with workspace-d releases, to make it easier for the users to install the latest version.

You can get the latest workspace-d version from here:
https://github.com/Pure-D/workspace-d/releases/tag/v2.7.2

And to get the visual studio code extension, simply search for `code-d` in the extensions manager. It will pop up as `D Programming Language (code-d)` by webfreak.

Also I recently started collecting some ideas for even more features & commands to integrate into workspace-d & code-d, if you want to take a look and submit more ideas:

https://github.com/Pure-D/workspace-d/issues (commands & features for all IDEs/Text Editors which will support workspace-d)

https://github.com/Pure-D/code-d/issues (features specific to the visual studio code plugin such as UI changes)


A mostly complete list of all code-d/workspace-d features can be found here: https://github.com/Pure-D/code-d/wiki

Awesome work, thanks again!
Suggest getting the deb hosted in d-apt along with the other tools
already there, and set them as dependencies?

On 7 September 2016 at 07:05, WebFreak001 via Digitalmars-d-announce <digitalmars-d-announce@puremagic.com> wrote:
> I just pushed a new release of workspace-d (bridge between DCD, DScanner,
> dfmt and dub with some utility stuff) and code-d (my vscode D extension
> using workspace-d).
>
> The latest update features several smaller additions such as better auto completion for DlangUI Markup Language and more configurability.
>
> As an addition I am starting to bundle .deb files and precompiled windows binaries with workspace-d releases, to make it easier for the users to install the latest version.
>
> You can get the latest workspace-d version from here: https://github.com/Pure-D/workspace-d/releases/tag/v2.7.2
>
> And to get the visual studio code extension, simply search for `code-d` in the extensions manager. It will pop up as `D Programming Language (code-d)` by webfreak.
>
> Also I recently started collecting some ideas for even more features & commands to integrate into workspace-d & code-d, if you want to take a look and submit more ideas:
>
> https://github.com/Pure-D/workspace-d/issues (commands & features for all IDEs/Text Editors which will support workspace-d)
>
> https://github.com/Pure-D/code-d/issues (features specific to the visual studio code plugin such as UI changes)
>
>
> A mostly complete list of all code-d/workspace-d features can be found here: https://github.com/Pure-D/code-d/wiki

On Wednesday, 7 September 2016 at 02:04:21 UTC, Manu wrote:
> Awesome work, thanks again!
> Suggest getting the deb hosted in d-apt along with the other tools
> already there, and set them as dependencies?

would probably be nice, but I have no idea how package maintaining for apt really works. I am not quite sure how to make an i386 package, I only made an amd64 one. The script for generating the apt file is in makedeb.d if you want to check it. I'm surprised it even works because I haven't tested it once.

But I guess I can manage adding dependencies. Just not really sure if I also need to make an i386 package or other architectures

On 7 September 2016 at 13:29, WebFreak001 via Digitalmars-d-announce <digitalmars-d-announce@puremagic.com> wrote:
> On Wednesday, 7 September 2016 at 02:04:21 UTC, Manu wrote:
>>
>> Awesome work, thanks again!
>> Suggest getting the deb hosted in d-apt along with the other tools
>> already there, and set them as dependencies?
>
>
> would probably be nice, but I have no idea how package maintaining for apt really works. I am not quite sure how to make an i386 package, I only made an amd64 one. The script for generating the apt file is in makedeb.d if you want to check it. I'm surprised it even works because I haven't tested it once.
>
> But I guess I can manage adding dependencies. Just not really sure if I also need to make an i386 package or other architectures

So, the 'normal' way is to create a debian source package, which
effectively contains code and build instructions, and then generate a
matrix of binary deb's from that. *buntu users would just put that on
LaunchPad, which will populate the build matrix for your PPA
automatically.
d-apt is not a PPA though, so maybe it would be simplest for you to
contact the maintainer of d-apt and ask his advice. It might just
slide into his scripts without requiring any additional effort on your
part...?

>And to get the visual studio code extension, simply search for `code-d` in >the extensions manager. It will pop up as `D Programming Language (code-d)`

So to get it work I should place dcd-client.exe dcd-server.exe dscanner.exe and workspace-d.exe in dir that set in PATH (for me it's C:\D\dmd2\windows\bin ) right?

But after it it's do not seems to be working:

http://img.ctrlv.in/img/16/09/07/57cfc3120b3c5.png

What I am doing wrong?

On Wednesday, 7 September 2016 at 07:37:11 UTC, Suliman wrote:
>>And to get the visual studio code extension, simply search for `code-d` in >the extensions manager. It will pop up as `D Programming Language (code-d)`
>
> So to get it work I should place dcd-client.exe dcd-server.exe dscanner.exe and workspace-d.exe in dir that set in PATH (for me it's C:\D\dmd2\windows\bin ) right?
>
> But after it it's do not seems to be working:
>
> http://img.ctrlv.in/img/16/09/07/57cfc3120b3c5.png
>
> What I am doing wrong?

Oh right on windows you also need to change the path of phobos/druntime in your vscode config. For example if you installed D on C:\D\ you would add this to your vscode user settings (ctrl-shift-p -> user settings):

"d.stdlibPath": [
	"C:\\D\\druntime\\import",
	"C:\\D\\include\\dmd\\phobos"
]

(you should also check these paths before copy-pasting because I am not sure if they are correct)

"d.stdlibPath": [
 "C:\\D\\dmd2\\src\\phobos",
 "C:\\D\\dmd2\\src\\druntime\\import"
]

I check path, look like this is correct (al lst they are exists).

But I still do not getting surrestion for import like std. and for any Phobos functions like writeln etc

On Wednesday, 7 September 2016 at 17:08:36 UTC, Suliman wrote:
> "d.stdlibPath": [
>  "C:\\D\\dmd2\\src\\phobos",
>  "C:\\D\\dmd2\\src\\druntime\\import"
> ]
>
> I check path, look like this is correct (al lst they are exists).
>
> But I still do not getting surrestion for import like std. and for any Phobos functions like writeln etc

Can you check the output in the developer tools and also post an issue on workspace-d with the log from the dev tools when you try to auto complete?

On Wednesday, 7 September 2016 at 17:08:36 UTC, Suliman wrote:
> "d.stdlibPath": [
>  "C:\\D\\dmd2\\src\\phobos",
>  "C:\\D\\dmd2\\src\\druntime\\import"
> ]
>
> I check path, look like this is correct (al lst they are exists).
>
> But I still do not getting surrestion for import like std. and for any Phobos functions like writeln etc

Hm... Does it's need time for cashing symbols? It's seems that work, but I still not understand if it's ok or not.

On Wednesday, 7 September 2016 at 17:21:17 UTC, Suliman wrote:
> On Wednesday, 7 September 2016 at 17:08:36 UTC, Suliman wrote:
>> "d.stdlibPath": [
>>  "C:\\D\\dmd2\\src\\phobos",
>>  "C:\\D\\dmd2\\src\\druntime\\import"
>> ]
>>
>> I check path, look like this is correct (al lst they are exists).
>>
>> But I still do not getting surrestion for import like std. and for any Phobos functions like writeln etc
>
> Hm... Does it's need time for cashing symbols? It's seems that work, but I still not understand if it's ok or not.

Depends on how many dependencies it has. More dependencies = longer cache time at the start where its unresponsive. Also I assume you just downloaded the workspace-d.exe from the project page or compiled it yourself with **LDC** <-- important, otherwise that might be the issue.

When it says "DCD is ready" in the console it will load the dub dependencies. After that you should be able to autocomplete phobos paths