On 2012-03-27 20:05, Adam Wilson wrote:

> To be a fully useable *D* IDE this is true, but that's not really an
> Integrated Development Environment, its just Yet Another Specialized
> Development Environment. I'd argue that the whole point of the
> "Integrated" part of IDE is that everything you might possibly need to
> do your job is one place specifically so you don't have to go hunt down
> that other software package you only need every couple of months. And
> I'm not saying that we shouldn't have an IDE written in D, just that
> it's not the best path at the moment, and regardless of the purity folks
> "everything must be written in D!" tirades, integrating D into
> MonoDevelop represents the best way to get devs using D right now. Also,
> the D GUI situation leaves a lot to be desired in terms of complex UI's
> like IDE's.
>
> Besides, Mono-D has more pressing issues than a potential stand-alone
> IDE ... CTFE/mixin parsing anybody?

I agree with you. If you want to use the same IDE for EVERYTHING than that will take a lot more work. In that case I don't see much point in reinventing the wheel when we have MonoDevelop and Eclipse. But I think an IDE can be for one language and still be called IDE, although others might call it a glorified text editor.

-- 
/Jacob Carlborg

On Tuesday, 27 March 2012 at 18:06:03 UTC, Adam Wilson wrote:
> Besides, Mono-D has more pressing issues than a potential stand-alone IDE ... CTFE/mixin parsing anybody?

Well, I think the GSoC phase will be about implementing UFCS, Mixin/Expression evaluation and CTFE then. Well cool, so I found the key features that I'll do for Mono-D.

I'll prepare an application document then - so I probably will hand it in to the digitalmars heads tomorrow or on thursday, dunno exactly :)

On 26/03/2012 20:43, Adam Wilson wrote:
> As to an IDE written in D, that's a HUGE project and well outside the
> scope of what can be accomplished in a GSoC project. It takes millions
> of lines of code to make a *DECENT* IDE.

I agree, this idea to write a proper, *fully-featured* IDE in D is simply totally unrealistic. If it's just a D editor with some IDE functionality, sure, someone can toy around and try to work on that, but as for a proper IDE, there is just so much functionality and infrastructure that platforms like Eclipse, Visual Studio, MonoDevelop, Netbeans, etc., provide that is dumb and futile to try replicate all of that in D. There are years of paid, multi-developer teams work behind that infrastructure, and you want one or two guys to replicate that in their free time? Right.
We don't even have a mature, fleshed-out D GUI library, let alone IDE infrastructure...

-- 
Bruno Medeiros - Software Engineer

On 2012-05-18 19:20, Bruno Medeiros wrote:

> I agree, this idea to write a proper, *fully-featured* IDE in D is
> simply totally unrealistic. If it's just a D editor with some IDE
> functionality, sure, someone can toy around and try to work on that, but
> as for a proper IDE, there is just so much functionality and
> infrastructure that platforms like Eclipse, Visual Studio, MonoDevelop,
> Netbeans, etc., provide that is dumb and futile to try replicate all of
> that in D. There are years of paid, multi-developer teams work behind
> that infrastructure, and you want one or two guys to replicate that in
> their free time? Right.
> We don't even have a mature, fleshed-out D GUI library, let alone IDE
> infrastructure...
>

Half of Eclipse is ported to D :)

https://github.com/d-widget-toolkit

-- 
/Jacob Carlborg

On Fri, May 18, 2012 at 2:39 PM, Jacob Carlborg <doob@me.com> wrote:

> On 2012-05-18 19:20, Bruno Medeiros wrote:
>
>  I agree, this idea to write a proper, *fully-featured* IDE in D is
>> simply totally unrealistic. If it's just a D editor with some IDE
>> functionality, sure, someone can toy around and try to work on that, but
>> as for a proper IDE, there is just so much functionality and
>> infrastructure that platforms like Eclipse, Visual Studio, MonoDevelop,
>> Netbeans, etc., provide that is dumb and futile to try replicate all of
>> that in D. There are years of paid, multi-developer teams work behind
>> that infrastructure, and you want one or two guys to replicate that in
>> their free time? Right.
>> We don't even have a mature, fleshed-out D GUI library, let alone IDE
>> infrastructure...
>>
>>
> Half of Eclipse is ported to D :)
>
> https://github.com/d-widget-**toolkit<https://github.com/d-widget-toolkit>


Half of Eclipse ~4-6 years ago ported to D.
That certainly doesn't make it not useful, but DWT hasn't managed to keep
up with Eclipse.

On 2012-05-19 06:03, Andrew Wiley wrote:

> Half of Eclipse ~4-6 years ago ported to D.
> That certainly doesn't make it not useful, but DWT hasn't managed to
> keep up with Eclipse.

I know, I know. Any help is welcome.

-- 
/Jacob Carlborg

Am 18.05.2012 21:39, schrieb Jacob Carlborg:
> On 2012-05-18 19:20, Bruno Medeiros wrote:
>
>> I agree, this idea to write a proper, *fully-featured* IDE in D is
>> simply totally unrealistic. If it's just a D editor with some IDE
>> functionality, sure, someone can toy around and try to work on that, but
>> as for a proper IDE, there is just so much functionality and
>> infrastructure that platforms like Eclipse, Visual Studio, MonoDevelop,
>> Netbeans, etc., provide that is dumb and futile to try replicate all of
>> that in D. There are years of paid, multi-developer teams work behind
>> that infrastructure, and you want one or two guys to replicate that in
>> their free time? Right.
>> We don't even have a mature, fleshed-out D GUI library, let alone IDE
>> infrastructure...
>>
>
> Half of Eclipse is ported to D :)
>
> https://github.com/d-widget-toolkit
>

As someone that has experience developing Eclipse plugins, I would say
that is more like a 1/4 of Eclipse or even less. :)

The UI framework is very little from the complete runtime infrastructure
that Eclipse offers.

--
Paulo

On 2012-05-19 12:20, Paulo Pinto wrote:

> As someone that has experience developing Eclipse plugins, I would say
> that is more like a 1/4 of Eclipse or even less. :)
>
> The UI framework is very little from the complete runtime infrastructure
> that Eclipse offers.

That's why I added the smiley :)

-- 
/Jacob Carlborg