On Wednesday, 9 August 2017 at 20:29:07 UTC, 12345swordy wrote:
> You edit the json file of course. That how DUB generates solution files for visual D and other IDE's.

This breaks changes that was done in the VS project.

On Thursday, 10 August 2017 at 05:55:59 UTC, Dmitry wrote:
> On Wednesday, 9 August 2017 at 20:29:07 UTC, 12345swordy wrote:
>> You edit the json file of course. That how DUB generates solution files for visual D and other IDE's.
>
> This breaks changes that was done in the VS project.

What changes are talking about? You typically make changes in the json file.

Alex

On Thursday, 10 August 2017 at 19:44:35 UTC, 12345swordy wrote:
> On Thursday, 10 August 2017 at 05:55:59 UTC, Dmitry wrote:
>> On Wednesday, 9 August 2017 at 20:29:07 UTC, 12345swordy wrote:
>>> You edit the json file of course. That how DUB generates solution files for visual D and other IDE's.
>>
>> This breaks changes that was done in the VS project.
>
> What changes are talking about? You typically make changes in the json file.

https://forum.dlang.org/thread/olfrkycsfukvipeohmut@forum.dlang.org

On Wednesday, 9 August 2017 at 22:17:42 UTC, Jonathan M Davis wrote:
> On Wednesday, August 09, 2017 17:13:37 Timon Gehr via Digitalmars-d wrote:
>> It is also a common pattern for the complainers to point out how not fixing their pet peeve will result in negative PR or reduced popularity. As if everyone here was somehow more deeply invested in D's popularity than in its quality. I find that to be a bit irritating.
>
> If anything, most of us are more invested in its quality than its popularity. Those of us who spend our time contributing to the code base or writing our personal projects in D care a great deal about its quality, and while we may care about how popular it is, that obviously wasn't what brought us here. Having D popular would be nice, but it's not necessary for us to be doing what we've been doing. And the reality of the matter is that most of us don't have the proper skillset for improving D's popularity. We're engineers, not marketing people.
>
> If someone has an issue that prevents them from using D, then that matters, but it needs to be taken in the context of everything else, and honestly, if doing something to make the language more popular means reducing its quality, I'd rather that it have higher quality. Ideally, having higher quality would help improve its popularity, but unfortunately, things don't always work that way.
>
> Regardless, we're here because we want a quality language, not because we want a popular one. We just hope that those two things aren't mutually exclusive.
>
> - Jonathan M Davis

i agree about quality part, but you mix two things, popularity and the need of tooling

the point of my post was to gather community in hope for better tooling, not popularity

having great tooling might increase popularity, but for me it'll improve my productivity, and that's all i care about, popularity is next, quality is already nice for me

On Wednesday, 9 August 2017 at 07:59:46 UTC, Ryion wrote:
> this here because its obvious pattern. I agree that this seems to be a very small community and it is hard to get things done in a small community. But it is counter productive to constantly tell people that there is no solution, they need to do it or pay for it. Its like hearing a broken record that keeps skipping to the same beat.

It's a sign of a lack of strategy.

Other languages such as Dart had an IDE strategy from the start. Dart even provided a full Eclipse based IDE until JetBrains included support (then the Dart team dropped their own IDE).

Without a central organized IDE project it will be hard to reach maturity for any such effort (unless the language is popular to sustain the development of a commercial IDE).

On Friday, 11 August 2017 at 08:13:07 UTC, SC wrote:
> [...]
> having great tooling might increase popularity, but for me it'll improve my productivity, and that's all i care about, popularity is next, quality is already nice for me

The language itself should improve your productivity: meta programming, embedded unittests, static assertions.

On 11/08/2017 12:46 PM, HyperParrow wrote:
> On Friday, 11 August 2017 at 08:13:07 UTC, SC wrote:
>> [...]
>> having great tooling might increase popularity, but for me it'll improve my productivity, and that's all i care about, popularity is next, quality is already nice for me
> 
> The language itself should improve your productivity: meta programming, embedded unittests, static assertions.

Good tooling won't subtract from a good language, it will only improve upon it. Its the icing on the already delicious cake.

On Friday, 11 August 2017 at 11:34:44 UTC, Ola Fosheim Grøstad wrote:
> On Wednesday, 9 August 2017 at 07:59:46 UTC, Ryion wrote:
>> this here because its obvious pattern. I agree that this seems to be a very small community and it is hard to get things done in a small community. But it is counter productive to constantly tell people that there is no solution, they need to do it or pay for it. Its like hearing a broken record that keeps skipping to the same beat.
>
> It's a sign of a lack of strategy.
>
> Other languages such as Dart had an IDE strategy from the start. Dart even provided a full Eclipse based IDE until JetBrains included support (then the Dart team dropped their own IDE).
>
> Without a central organized IDE project it will be hard to reach maturity for any such effort (unless the language is popular to sustain the development of a commercial IDE).

I think having IDE for some language written in the same language may show power and usability of this language.

E.g. DlangIDE is written in D, uses cross-platform GUI library DlangUI which is written in D, and is cross-platform. May work even as console app.

For D programmers, it's easy to contribute something to IDE written in D than to some Java or C++/C# project.

Active contributing to DlangIDE can make it really useful tool. So far, it's less usable than Visual-D or Mono-D. So far, I myself use Visual-D to develop D projects (including DlangIDE), but I hope there will be a point when it would be possible to switch to DlangIDE.

I'm thinking about killer feature - adding Delphi like UI designer for writing DlangUI/DML apps. Having IDE similar to Delphi or Lazarus would be great advantage of D.

On Friday, 11 August 2017 at 12:11:13 UTC, Vadim Lopatin wrote:
> E.g. DlangIDE is written in D, uses cross-platform GUI library DlangUI which is written in D, and is cross-platform. May work even as console app.
>


First, you are to be saluted (luimarco style*) for your effor on DlangIDE and DlangUI

And I wish you continued growth and success

But if you may accept some advice from me, I think, re branding the  DlangIDE
to something more generic and adding C support specifically and allowing to add support for other languages is the right thing to do


IDEs take years to mature, you need to be more inclusive, only supporting D isnt very inclusive
Most people program in more than one language, and like to use one toolset/ide
C specifically, because there is a large C community out there that is under served, most C programmer use advanced text editors Vim/Emacs/SlickEdit

In other word, you need to be more inclusive and inviting, IDEs are big and the D community is small

A re-branding (Call it Dice IDE, for example)
Pluggin support
And a solid C plugin are my recommendations


------
* luimarco is a fitness and body building youtuber

On Friday, 11 August 2017 at 03:16:17 UTC, Dmitry wrote:
> On Thursday, 10 August 2017 at 19:44:35 UTC, 12345swordy wrote:
>> On Thursday, 10 August 2017 at 05:55:59 UTC, Dmitry wrote:
>>> On Wednesday, 9 August 2017 at 20:29:07 UTC, 12345swordy wrote:
>>>> You edit the json file of course. That how DUB generates solution files for visual D and other IDE's.
>>>
>>> This breaks changes that was done in the VS project.
>>
>> What changes are talking about? You typically make changes in the json file.
>
> https://forum.dlang.org/thread/olfrkycsfukvipeohmut@forum.dlang.org

The person that you reply appears to be uncertain as he/she admits that he/she never use dub themselves.

BTW if you want to add a dependency to the project you have to modify the json file.