Brad Anderson wrote:
> On Linux, you may have some case sensitivity on the *.D files.  In the plugin.xml file, change the
> 
> extensions="d" attribute in the <editor> tag to lowercase.  Just a thought.
> 
> BA

Windows Eclipse has the exact same issues as on Linux.  I'm getting annoyed with Eclipse.  At first I thought it was neat.  Now I find it frustratingly complex for simple tasks.

What I want to do is simply open up a new D project.  But then I probably can't do that if I'm currently in a default Java perspective (which seems to be active when I start eclipse).  If I want to open a existing D file, it seems the only logical place to do it is using the File->Open External File... selection.  When I do that, that's when the editor has an error and prints "ERROR" in the new document view.  I can't seem to find any D views, perspectives, or project modes (perhaps currently are non existant with the D plugin?) to activate to make it all work.  It's a major pain.  I can't even find a straightforward way to add d files to a project.  If the D plugin just turns Eclispe into a D editor, I can find simpler programs that do the same thing.

I'm finding the whole eclipse interface confusing. And that's after spending some time reading documentation and experimenting.  I'm finding nothing intuitive about eclipse at all.  If this is the kind of IDE we are heading towards for D, I'm not looking forward to it.

I think I'll just stick to something simple like SCite.

> P.S.  You ready to look at some dwt code?  I still have forward reference problems that are driving me crazy.
> 

Have you been using the makefile to compile?  Send the files my way; I'll try to get to the bottom of some of the issues.

Later,

John

You may want to be patient.  I've had some luck with Eclipse for Java, in fact, I really am impressed.  If we could enhance the current D plugin to have some of the features in the Java development portion of Eclipse, I'd be thrilled.

I just don't know how to do it, and I'd like to get thru the other project first.  Alex is also finishing up work on the JS plugin, and then he may be able to help.

For now, I have a few "simple projects", not Java projects, that hold my D stuff.  That may be one of your sticking points.  I have a hierarchy under the src folder, and I can single-click *.d files and they open up like a champ.  I also call 'make' with appropriate arguments as an External Tool.  The console is captured, and all messages from the compiler are there for me.  I never leave Eclipse.  Syntax highlighting is also nice, but Alex is right.  It'd be nice to have an outline, code formatter, auto-complete like Intellisense in MSVS and code errors/warnings displayed in the Tasks/Problems area.  Hopefully we'll get there.

BA

> If the D plugin just turns Eclispe into a D editor, I can find simpler 
> programs that do the same thing.
>
> I'm finding the whole eclipse interface confusing. And that's after spending some time reading documentation and experimenting.  I'm finding nothing intuitive about eclipse at all.  If this is the kind of IDE we are heading towards for D, I'm not looking forward to it.
> 

Brad Anderson wrote:
> You may want to be patient.  I've had some luck with Eclipse for Java, in fact, I really am impressed.  If we could enhance the current D plugin to have some of the features in the Java development portion of Eclipse, I'd be thrilled.
> 
> I just don't know how to do it, and I'd like to get thru the other project first.  Alex is also finishing up work on the JS plugin, and then he may be able to help.
> 
> For now, I have a few "simple projects", not Java projects, that hold my D stuff.  That may be one of your sticking points.  I have a hierarchy under the src folder, and I can single-click *.d files and they open up like a champ.  I also call 'make' with appropriate arguments as an External Tool.  The console is captured, and all messages from the compiler are there for me.  I never leave Eclipse.  Syntax highlighting is also nice, but Alex is right.  It'd be nice to have an outline, code formatter, auto-complete like Intellisense in MSVS and code errors/warnings displayed in the Tasks/Problems area.  Hopefully we'll get there.
> 

Ok thanks for explaining that.  I guess I was overreacting.  I didn't realize the directory structure was critical.  I was looking for ways to import d files into a new project in a separate directory.  When I did what you said on the dwt src, it displayed all the d files properly. These opened properly in the editor view.

Thanks!

John R

PS which "make" are you using? DMC's, Borland's, or GNU?

DMC

> PS which "make" are you using? DMC's, Borland's, or GNU?

Brad Anderson wrote:
> You may want to be patient.  I've had some luck with Eclipse for Java, in fact, I really am impressed.  If we could enhance the current D plugin to have some of the features in the Java development portion of Eclipse, I'd be thrilled.
> 
> I just don't know how to do it, and I'd like to get thru the other project first.  Alex is also finishing up work on the JS plugin, and then he may be able to help.

Can someone who's better at parsers than me create a semantic stack for D in Java? If you can do that, the rest is a piece of cake.

-- 
Alex

Sark7 wrote:

> On Thu, 12 Feb 2004 22:06:55 -0500, Alex Fitzpatrick <alex.nospam.fitzpatrick@videotron.nospam.ca> wrote:
> 
>> Has anyone looked into creating an Eclipse plugin for editing D?
>>
>> Is there any other IDE yet?
>>
> 
> I use Colorer for syntax highlighting, and CDT for error parsing and common management.

Are you getting the CDT to assign breakpoints and stop code execution?  What components are you using?

DMD - compiler
DM Make - make
???? - debugger

If not, do you know how to write the semantic stack that Alex is talking about?

BA

On Mon, 16 Feb 2004 09:53:22 -0600, Brad Anderson <brad@sankaty.dot.com> wrote:

> Sark7 wrote:
>
>> On Thu, 12 Feb 2004 22:06:55 -0500, Alex Fitzpatrick <alex.nospam.fitzpatrick@videotron.nospam.ca> wrote:
>>
>>> Has anyone looked into creating an Eclipse plugin for editing D?
>>>
>>> Is there any other IDE yet?
>>>
>>
>> I use Colorer for syntax highlighting, and CDT for error parsing and common management.
>
> Are you getting the CDT to assign breakpoints and stop code execution?  What components are you using?
>
> DMD - compiler
> DM Make - make
> ???? - debugger
>
> If not, do you know how to write the semantic stack that Alex is talking about?
>
> BA

I don't use any debugger for now :D
I don't know anything about "semantic stack", I'm not guru in Eclipse plugin writing :/
And, I use MinGW make, it is much more powerful than DM's one.

A bit more about Colorer, if you interested:

Colorer is a Eclipse plugin that do highlighting and outlining, based on it's
own HRC schemes. HRC describes language's highlighting/outling in regular
expressions. I create my own HRC scheme for D and use it. I think, dedicated
D plugin would be much better, but as temporary solution Colorer works :)