Hello,

DlangIDE is getting close to usable.
DlangIDE is and IDE for D programming language written in D using DlangUI library.

Project page: https://github.com/buggins/dlangide

To try, use `dub fetch dlangide && dub run dlangide` try to create and run DlangUI Helloworld project, or open Tetris project from workspaces/tetris.

Supported platforms: win32, linux, osx.

DlangIDE uses DUB to build and run projects, DUB .json as project format, DCD for code completion.
For code completion / go to references functionality, you need to build dcd-server and dcd-client executables from https://github.com/Hackerpilot/DCD.git and put them to some of PATH dirs.

Recent changes:
- New Project wizard
- New source file wizard
- Add / remove project files, refresh workspace
- A lot of bugfixes

Current activities:
- GDB MI debugger support
- integration of DML GUI builder (Delphi like)

DlangUI: https://github.com/buggins/dlangui

Recent DlangUI changes:
- MonoD and VisualD projects for development under Windows, Linux, OSX.
- pure X11 backend implemented to avoid SDL dependency
- dmledit app for editing DML
- spreadsheet example (excel like app, just started)
- a lot of bugfixes

Try dlangui:tetris, dlangui:example1, dlangui:dmledit examples.


Best regards,
    Vadim

On Tuesday, 8 December 2015 at 15:58:43 UTC, Vadim Lopatin wrote:
> Hello,
>
> DlangIDE is getting close to usable.
> DlangIDE is and IDE for D programming language written in D using DlangUI library.
>
> [...]

Congrats! Glad to see that project is not abandoned.

On Tuesday, 8 December 2015 at 15:58:43 UTC, Vadim Lopatin wrote:
> Hello,
>
> DlangIDE is getting close to usable.
> DlangIDE is and IDE for D programming language written in D using DlangUI library.

Sweet! Glad you're back and working on this!
Was wanting to give it a shot, but typing } on my keyboard (german layout, right-alt + 0) did not actually insert the character into the opened document, so I gave up.
Most of the UI stuff looks really neat (especially like the directory structure preview when creating a new project/workspace), but obviously still needs a lot of work (you cannot drag dialogs around, fe).
One of the things I did manage to try was putting a readln() into the standard hello-world-console-app preset. Turns out that it causes dlangide to hang up because it's not actually possible to have user input (or to configure dlangide to start the project separately so a regular console window appears). Killing the started process also was not possible since the respective option to stop debugging is still grayed out.

From the looks of it, this is very promising though. I like the Workspace layout and the general feel of the IDE (very responsive, very clean) and it all kind of makes me wish it wouldn already have enough features (especially debugging!) to be a viable option.

I still haven't written much D code and my time is somewhat limited, but if there are simple tasks you need to get done, I would be glad to offer help!

Here's to hoping this IDE will keep going and turn out well :-)

Awesome!

Is there any chance of bundling DCD? It would be a lot more convenient if I didn't even have to think about getting another completion program and running it on my project.

On Tuesday, 8 December 2015 at 18:18:29 UTC, default0 wrote:
> Sweet! Glad you're back and working on this!
> Was wanting to give it a shot, but typing } on my keyboard (german layout, right-alt + 0) did not actually insert the character into the opened document, so I gave up.
What is a platform? Linux with SDL? How do I reproduce it? Could you please submit a bug on github?

> Most of the UI stuff looks really neat (especially like the directory structure preview when creating a new project/workspace), but obviously still needs a lot of work (you cannot drag dialogs around, fe).
Dialogs are currently displayed as popup widgets instead of separate windows due to issue with OpenGL contexts under Win32 when multiple windows are being used.

> One of the things I did manage to try was putting a readln() into the standard hello-world-console-app preset. Turns out that it causes dlangide to hang up because it's not actually possible to have user input (or to configure dlangide to start the project separately so a regular console window appears). Killing the started process also was not possible since the respective option to stop debugging is still grayed out.
Input hangs because running currently is just invoking of `dub run` - with input and output redirected. Output is shown in IDE message log, but for input just nothing is sent.
I'm working on debugging, and as well will implement running apps w/o debugger with separate console.

> From the looks of it, this is very promising though. I like the Workspace layout and the general feel of the IDE (very responsive, very clean) and it all kind of makes me wish it wouldn already have enough features (especially debugging!) to be a viable option.
Debugging is high priority task now.

> I still haven't written much D code and my time is somewhat limited, but if there are simple tasks you need to get done, I would be glad to offer help!
It would be great.

> Here's to hoping this IDE will keep going and turn out well :-)
I think for programming language, it's big + to have native GUI library and IDE written in the same language. Adding Delphi style GUI builder could attract newbies.

On Tuesday, 8 December 2015 at 23:45:47 UTC, Chris Wright wrote:
> Awesome!
>
> Is there any chance of bundling DCD? It would be a lot more convenient if I didn't even have to think about getting another completion program and running it on my project.

For win32, it's bundled with dcd-client and dcd-server binaries (although of quite old version).
For mac, I suppose there should not be a problem too to add dcd binaries.
But for Linux I'm unsure how to build DCD which is able to work on all distributions.

On Wednesday, 9 December 2015 at 05:47:07 UTC, Vadim Lopatin wrote:
> On Tuesday, 8 December 2015 at 18:18:29 UTC, default0 wrote:
>> Sweet! Glad you're back and working on this!
>> Was wanting to give it a shot, but typing } on my keyboard (german layout, right-alt + 0) did not actually insert the character into the opened document, so I gave up.
> What is a platform? Linux with SDL? How do I reproduce it? Could you please submit a bug on github?

Done!
>> One of the things I did manage to try was putting a readln() into the standard hello-world-console-app preset. Turns out that it causes dlangide to hang up because it's not actually possible to have user input (or to configure dlangide to start the project separately so a regular console window appears). Killing the started process also was not possible since the respective option to stop debugging is still grayed out.
> Input hangs because running currently is just invoking of `dub run` - with input and output redirected. Output is shown in IDE message log, but for input just nothing is sent.
> I'm working on debugging, and as well will implement running apps w/o debugger with separate console.

Sounds good! When the typical edit-compile-debug cycle works this will probably already be enough to start using it for smaller projects :-)

>> I still haven't written much D code and my time is somewhat limited, but if there are simple tasks you need to get done, I would be glad to offer help!
> It would be great.
>
Will be looking through GitHub and try to set DlangUI etc. up locally, too and see what I can do :-)

>> Here's to hoping this IDE will keep going and turn out well :-)
> I think for programming language, it's big + to have native GUI library and IDE written in the same language. Adding Delphi style GUI builder could attract newbies.

Yeah, also has the advantage of being able to work on DlangIDE while using DlangIDE, once it's come along some ways.

On Wednesday, 9 December 2015 at 09:18:37 UTC, default0 wrote:
>>> One of the things I did manage to try was putting a readln() into the standard hello-world-console-app preset. Turns out that it causes dlangide to hang up because it's not actually possible to have user input (or to configure dlangide to start the project separately so a regular console window appears). Killing the started process also was not possible since the respective option to stop debugging is still grayed out.
>> Input hangs because running currently is just invoking of `dub run` - with input and output redirected. Output is shown in IDE message log, but for input just nothing is sent.
>> I'm working on debugging, and as well will implement running apps w/o debugger with separate console.
>
> Sounds good! When the typical edit-compile-debug cycle works this will probably already be enough to start using it for smaller projects :-)

Running in external console is implemented.
Run button now starts dub build, and if build is successful executes program in external console.
Stop button added.
Xterm is used as external console on posix.

Tested under windows and linux.

On Wednesday, 9 December 2015 at 09:18:37 UTC, default0 wrote:
>>> I still haven't written much D code and my time is somewhat limited, but if there are simple tasks you need to get done, I would be glad to offer help!
>> It would be great.
>>
> Will be looking through GitHub and try to set DlangUI etc. up locally, too and see what I can do :-)

Added development environment setup instructions (VisualD, Mono-D) to README.

On Wednesday, 9 December 2015 at 12:10:33 UTC, Vadim Lopatin wrote:
> On Wednesday, 9 December 2015 at 09:18:37 UTC, default0 wrote:
>>>> I still haven't written much D code and my time is somewhat limited, but if there are simple tasks you need to get done, I would be glad to offer help!
>>> It would be great.
>>>
>> Will be looking through GitHub and try to set DlangUI etc. up locally, too and see what I can do :-)
>
> Added development environment setup instructions (VisualD, Mono-D) to README.

Thanks for the instructions! I followed them, but when I tried to build in Visual Studio, I got the following error:

Building Debug\dlangide.exe...
C:\Users\Administrator\Documents\DCode\DlangUI\src\dlangui\graphics\images.d(34): Error: module io is in file 'dlib\image\io\io.d' which cannot be read
import path[0] = C:\Users\Administrator\Documents\DCode\DlangUI\src
import path[1] = C:\Users\Administrator\Documents\DCode\DlangUI\3rdparty
import path[2] = C:\Users\Administrator\Documents\DCode\DlangUI\3rdparty\libpng\source
import path[3] = C:\Users\Administrator\Documents\DCode\DlangUI\..\DerelictGL3\source
import path[4] = C:\Users\Administrator\Documents\DCode\DlangUI\..\DerelictUtil\source
import path[5] = C:\Users\Administrator\Documents\DCode\DlangUI\..\DerelictFT\source
import path[6] = C:\Users\Administrator\Documents\DCode\DlangUI\..\DerelictSDL2\source
import path[7] = C:\Users\Administrator\Documents\DCode\DlangUI\..\de_image\source\interfaces
import path[8] = C:\Users\Administrator\Documents\DCode\DlangUI\..\de_image\source\png
import path[9] = C:\Users\Administrator\Documents\DCode\DlangUI\..\dlib
import path[10] = C:\Users\Administrator\Documents\DCode\DlangUI\..\libdparse\src
import path[11] = C:\D\dmd2\windows\bin\..\..\src\phobos
import path[12] = C:\D\dmd2\windows\bin\..\..\src\druntime\import
Building Debug\dlangide.exe failed!

I checked the import path[9] it listed, and relative to that path, there is the dlib/image/io/io.d file (ie in "C:\Users\Administrator\Documents\DCode\DlangUI\..\dlib\dlib\image\io\io.d"). I'm not sure why it doesn't find that file, despite listing a path that contains this file in the imports (and has the necessary permissions for reading it, and the file obviously not being used by anything). I'm using Visual D.

Pretty stumped on that right now, building with dub obviously works, and I suppose I could then attach the debugger from within Visual Studio, but that's not a workflow I'm looking forward to (nor do I know if it works the way I hope)...