On Friday, 13 February 2015 at 14:47:08 UTC, Vadim Lopatin wrote:
> On Friday, 13 February 2015 at 10:00:33 UTC, Chris wrote:
>> On Thursday, 12 February 2015 at 14:16:49 UTC, Vadim Lopatin wrote:
>>> On Thursday, 12 February 2015 at 09:55:53 UTC, Chris wrote:
>>>> On Wednesday, 11 February 2015 at 17:49:53 UTC, Vadim Lopatin Got an error message after cloning and running "dub run"
>>>>
>>>> Compiling using dmd...
>>>> Error: cannot read file ../../.dub/packages/dlangui-master/examples/helloworld/bin/helloworld.d
>>>> FAIL .dub/build/application-debug-linux.posix-x86_64-dmd_2066-51E212BAD4DDA2DE13262C4DBFEB2E69/ dlangide executable
>>>> Error executing command run: dmd failed with exit code 1.
>>>>
>>>> I used dmd 2.066.1
>>>>
>>>> Btw, have you thought of integrating the version manager dvm somehow. I find it extremely useful, especially when upgrading my code to a new version of dmd.
>>>>
>>>> I'm really looking forward to using this IDE for my D projects one day.
>>>
>>> Following works for me:
>>>
>>> dub fetch dlangui
>>> dub run dlangui:helloworld
>>> dub run dlangui:example1
>>> dub run dlangui:tetris
>>>
>>> I see no errors.
>>> DMD is v2.066.0 and DUB is 0.9.22
>>
>> That works for me too, but the error I got was from this:
>>
>> git clone https://github.com/buggins/dlangide.git
>> cd dlangide
>> dub run
>>
>>>>> Building dlangide 0.2.1 configuration "application", build type debug.
>> Compiling using dmd...
>> Error: cannot read file ../../.dub/packages/dlangui-master/examples/helloworld/bin/helloworld.d
>> FAIL .dub/build/application-debug-linux.posix-x86_64-dmd_2066-51E212BAD4DDA2DE13262C4DBFEB2E69/ dlangide executable
>> Error executing command run: dmd failed with exit code 1.
>>
>> (dmd 2.066.0)
>
> Looks like DUB issue. It selects dlangui:helloworld instead if dlangui
>
>> git clone https://github.com/buggins/dlangide.git
>> cd dlangide
>> dub run
>
> It's working for me.
>
> $ dub run
> WARNING: A deprecated branch based version specification is used for the dependency dlangui. Please use numbered version
> s instead. Also note that you can still use the dub.selections.json file to override a certain dependency to use a branc
> h instead.
> Building dlib ~master configuration "library", build type debug.
> Running dmd...
> Target derelict-util 1.9.1 is up to date. Use --force to rebuild.
> Target derelict-ft 1.0.2 is up to date. Use --force to rebuild.
> Target derelict-sdl2 1.9.2 is up to date. Use --force to rebuild.
> Target derelict-gl3 1.0.12 is up to date. Use --force to rebuild.
> Building dlangui ~master configuration "library", build type debug.
> Running dmd...
> Building dlangide 0.2.3 configuration "application", build type debug.
> Compiling using dmd...
> Linking...
> Copying files for dlangui...
> Running .\bin\dlangide.exe
>
> Try
> dub upgrade --force-remove
>
> As well, check your DUB version.
> 0.9.22 should work ok.

dub upgrade --force-remove

This worked, thanks. I think I had this issue before, maybe you could add it as a note on your github page.

My dub version is:

DUB version 0.9.22, built on Sep 16 2014

On Monday, 16 February 2015 at 09:11:19 UTC, Vadim Lopatin wrote:
> On Thursday, 12 February 2015 at 14:24:05 UTC, ketmar wrote:
>> i don't want to give you any orders, but i think that it's better to make
>> shortcuts user-definable ASAP. you may skip GUI for that now and just
>> make a "keymap" file of some kind, and it will still be much better than
>> hard-coded shourtcuts.
>
> Keyboard shortcuts settings support is added.
>
> For linux and macos settings are placed in file
> ~/.dlangide/shortcuts.json
>
> For Windows,
> C:\Users\user\AppData\Roaming\.dlangide\shortcuts.json
>
> If no such file exists, it's being created on DlangIDE start, filling with default values to simplify configuration.

Great stuff. Just occured to me that font size, tab width and colors are very important too. I for my part prefer a dark background. It's easier on the eye, when you spend a lot of time looking at the screen. Texatadept and other editors have themes to choose from (and allow custom themes). That would be a great addition further down the road.

On Tuesday, 17 February 2015 at 10:42:18 UTC, Chris wrote:
> On Monday, 16 February 2015 at 09:11:19 UTC, Vadim Lopatin wrote:
>> On Thursday, 12 February 2015 at 14:24:05 UTC, ketmar wrote:
>>> i don't want to give you any orders, but i think that it's better to make
>>> shortcuts user-definable ASAP. you may skip GUI for that now and just
>>> make a "keymap" file of some kind, and it will still be much better than
>>> hard-coded shourtcuts.
>>
>> Keyboard shortcuts settings support is added.
>>
>> For linux and macos settings are placed in file
>> ~/.dlangide/shortcuts.json
>>
>> For Windows,
>> C:\Users\user\AppData\Roaming\.dlangide\shortcuts.json
>>
>> If no such file exists, it's being created on DlangIDE start, filling with default values to simplify configuration.
>
> Great stuff. Just occured to me that font size, tab width and colors are very important too. I for my part prefer a dark background. It's easier on the eye, when you spend a lot of time looking at the screen. Texatadept and other editors have themes to choose from (and allow custom themes). That would be a great addition further down the road.

Dark theme and settings editors are planned for nearest future.

On Friday, 6 February 2015 at 14:03:07 UTC, Vadim Lopatin wrote:
> Hello,
>
> I'm working on cross-platform D language IDE - DlangIDE.
> It's written in D using DlangUI based GUI.
>
> Project on GitHub: https://github.com/buggins/dlangide
>
> It's in alpha stage but already allows:
>
> * Open DUB based projects
> * Edit source files
> * Build and run projects using DUB
> * D source code syntax highlight
>
> Requires DUB for building projects.
>
> Features missing so far:
>
> * Debugging support
> * Code completion
> * Code folding
> * Go to definition
> * Smart indentation
>
> Best regards,
>    Vadim

Project update:

Hans-Albert Maritz (Freakazo) sent pull request with implementation of DCD integration.

Now DlangIDE supports autocompletion (Ctrl+Space or Ctrl+Shift+G) and GoToDefinition (Ctrl+G or F12).

DlangIDE becomes real IDE :)

For using of autocompletion, you need to install DCD.
DlangIDE starts its own copy of daemon on port 9167.
dcd-client and dcd-server must be in the same directory as dlangide executable or in one of PATH dirs.

Now most wanted feature is debugging support (IMHO).

On Tuesday, 17 February 2015 at 13:48:27 UTC, Vadim Lopatin wrote:
> On Friday, 6 February 2015 at 14:03:07 UTC, Vadim Lopatin wrote:
>> Hello,
>>
>> I'm working on cross-platform D language IDE - DlangIDE.
>> It's written in D using DlangUI based GUI.
>>
>> Project on GitHub: https://github.com/buggins/dlangide
>>
>> It's in alpha stage but already allows:
>>
>> * Open DUB based projects
>> * Edit source files
>> * Build and run projects using DUB
>> * D source code syntax highlight
>>
>> Requires DUB for building projects.
>>
>> Features missing so far:
>>
>> * Debugging support
>> * Code completion
>> * Code folding
>> * Go to definition
>> * Smart indentation
>>
>> Best regards,
>>   Vadim
>
> Project update:
>
> Hans-Albert Maritz (Freakazo) sent pull request with implementation of DCD integration.
>
> Now DlangIDE supports autocompletion (Ctrl+Space or Ctrl+Shift+G) and GoToDefinition (Ctrl+G or F12).
>
> DlangIDE becomes real IDE :)
>
> For using of autocompletion, you need to install DCD.
> DlangIDE starts its own copy of daemon on port 9167.
> dcd-client and dcd-server must be in the same directory as dlangide executable or in one of PATH dirs.
>
> Now most wanted feature is debugging support (IMHO).

I think soo too. Whats the way to go there for targeting all these platforms ?

On Tuesday, 17 February 2015 at 13:48:27 UTC, Vadim Lopatin wrote:
> For using of autocompletion, you need to install DCD.
> DlangIDE starts its own copy of daemon on port 9167.
> dcd-client and dcd-server must be in the same directory as dlangide executable or in one of PATH dirs.
>
> Now most wanted feature is debugging support (IMHO).

Thank you very much!

And why not use the libdparse library directly?
It will give much more possibilities.

On Tuesday, 17 February 2015 at 17:55:14 UTC, data man wrote:
> On Tuesday, 17 February 2015 at 13:48:27 UTC, Vadim Lopatin wrote:
>> For using of autocompletion, you need to install DCD.
>> DlangIDE starts its own copy of daemon on port 9167.
>> dcd-client and dcd-server must be in the same directory as dlangide executable or in one of PATH dirs.
>>
>> Now most wanted feature is debugging support (IMHO).
>
> Thank you very much!
>
> And why not use the libdparse library directly?
> It will give much more possibilities.

Good idea. Let me check it.

On Tuesday, 17 February 2015 at 17:53:56 UTC, extrawurst wrote:
> On Tuesday, 17 February 2015 at 13:48:27 UTC, Vadim Lopatin wrote:
>> Project update:
>>
>> Hans-Albert Maritz (Freakazo) sent pull request with implementation of DCD integration.
>>
>> Now DlangIDE supports autocompletion (Ctrl+Space or Ctrl+Shift+G) and GoToDefinition (Ctrl+G or F12).
>>
>> DlangIDE becomes real IDE :)
>>
>> For using of autocompletion, you need to install DCD.
>> DlangIDE starts its own copy of daemon on port 9167.
>> dcd-client and dcd-server must be in the same directory as dlangide executable or in one of PATH dirs.
>>
>> Now most wanted feature is debugging support (IMHO).
>
> I think soo too. Whats the way to go there for targeting all these platforms ?

It looks like we need to develop some universal debugger library.
For linux, it can use gdb as a backend.
For windows - I'm not sure. Is there any console debugger which can debug dmd generated executables? I've checked windbg shipped with dmd, but it looks like it is GUI, and cannot be used as backend via console.
Trying to play with my own implementation of debugger using win32 API.

Probably there is already some debugger interface written in D?

On Tuesday, 17 February 2015 at 19:41:10 UTC, Vadim Lopatin wrote:
> On Tuesday, 17 February 2015 at 17:53:56 UTC, extrawurst wrote:
>> On Tuesday, 17 February 2015 at 13:48:27 UTC, Vadim Lopatin wrote:
>>> Project update:
>>>
>>> Hans-Albert Maritz (Freakazo) sent pull request with implementation of DCD integration.
>>>
>>> Now DlangIDE supports autocompletion (Ctrl+Space or Ctrl+Shift+G) and GoToDefinition (Ctrl+G or F12).
>>>
>>> DlangIDE becomes real IDE :)
>>>
>>> For using of autocompletion, you need to install DCD.
>>> DlangIDE starts its own copy of daemon on port 9167.
>>> dcd-client and dcd-server must be in the same directory as dlangide executable or in one of PATH dirs.
>>>
>>> Now most wanted feature is debugging support (IMHO).
>>
>> I think soo too. Whats the way to go there for targeting all these platforms ?
>
> It looks like we need to develop some universal debugger library.
> For linux, it can use gdb as a backend.
> For windows - I'm not sure. Is there any console debugger which can debug dmd generated executables? I've checked windbg shipped with dmd, but it looks like it is GUI, and cannot be used as backend via console.
> Trying to play with my own implementation of debugger using win32 API.
>
> Probably there is already some debugger interface written in D?

maybe this helps:
http://wiki.dlang.org/Debuggers

On Friday, 6 February 2015 at 14:03:07 UTC, Vadim Lopatin wrote:
> Hello,
>
> I'm working on cross-platform D language IDE - DlangIDE.
> It's written in D using DlangUI based GUI.
>
> Project on GitHub: https://github.com/buggins/dlangide
>
> It's in alpha stage but already allows:
>
> * Open DUB based projects
> * Edit source files
> * Build and run projects using DUB
> * D source code syntax highlight
>
> Requires DUB for building projects.
>
> Features missing so far:
>
> * Debugging support
> * Code completion
> * Code folding
> * Go to definition
> * Smart indentation
>
> Best regards,
>    Vadim

Created thread DlangIDE in D.IDE for discussion.
http://forum.dlang.org/thread/lfcyzzjcavedxhicilko@forum.dlang.org