Vladimir Panteleev Wrote:

> Anyway, this is really something - especially the code formatter :D
> As a minor feature request, I'd like to see an option to format classes like this:
> 
> class Foo
> {
> 	int x;
> 
> private:
> 	int y;
> 
> public:
> 	int z;
> }
> 
> This indentation style is used quite often in Phobos, and I use it as well.
> I guess it might require adding "negative" indentation for certain elements to the formatter engine...
> 

Not hard at all; I'll get on that!

Gregor Richards Wrote:

> Ary Manzana wrote:
> > The plugin still doesn't integrate with a compiler. We are looking at the best way to seamlessly integrate it, so that compiling programs is as easy as it can be.
> 
> [Warning!! Shameless plug levels at critical!]
> 
> May I suggest integrating with DSSS? This would make your job much easier, since you wouldn't have to worry about specific compiler quirks or differences in making libraries etc on different platforms.
> 
>   - Gregor Richards

That's certainly a good idea. However, since descent will be internally tracking changes, dependencies, etc., I'm not sure exactly how this'll work I was thinking that DSSS integration for libraries, (perhaps even for symbol lookup if that's feasible - so if a user enters an unrecognized symbol, they could click a button to look it up in all DSSS-installed libraries, automatically add the library to the build path, and automatically add the necessary imports to the source file... libraries already on the build path and modules internal to the project and other projects in the workspace will of course also be considered, like in the JDT).

Integration with the net feature would be even crazier. Imagine how awesome (if not _that_ useful...) it'd be to enter "IMG_LoadPNG_RW" or something, have a red squiggle appear below it, click three times, and have DerlictSDL-Image automatically be downloaded (in the background), installed and added to the build path, and have the import statement added to the source file. And with all that it would be trivial to have the IDE generate "dsss.conf" files.

If you have the time, I'd like to meet up at the conference to discuss all this. That being said, this is Ary's brainchild, so I'll leave the final say up to him. Also, looking over DSSS, it doesn't seem to internally keep lists of symbols, so the IDE would need to be aware of the DSSS paths and keep its own symbol:module mapings, perhaps in the workspace directory.

Fun. Firt thing I try breaks

pragma(msg,">>" __FILE__ ":");

it compiles under DMD

BCS escribió:
> Fun. Firt thing I try breaks
> 
> pragma(msg,">>" __FILE__ ":");
> 
> it compiles under DMD
> 
> 

That's a tricky one. You can only concatenate string literals in that way, but it happen that DMD's lexer replaces __FILE__ with the current filename and treat it is a string literal token (instead of identifier)... but Descent not.

Well, now it does! :-)

Uninstall Descent and reinstall it. Remeber to run eclipse with "-clean" so the update manager refreshes the update site. You should see the new version: 0.4.20070813 (the previous one was 0.4.20070812).

Thanks for the bug report,
Ary

P.D.: It didn't break, there were just the red squiggles.

Reply to Ary,

> BCS escribió:
> 
>> Fun. Firt thing I try breaks
>> 
>> pragma(msg,">>" __FILE__ ":");
>> 
>> it compiles under DMD
>> 
> That's a tricky one. You can only concatenate string literals in that
> way, but it happen that DMD's lexer replaces __FILE__ with the current
> filename and treat it is a string literal token (instead of
> identifier)... but Descent not.

I expected as much (IIRC, my lexer treat __FILE__, __LINE__ and friends as special tokens)

> 
> Well, now it does! :-)

Thanks

> 
> Uninstall Descent and reinstall it. Remeber to run eclipse with
> "-clean" so the update manager refreshes the update site. You should
> see the new version: 0.4.20070813 (the previous one was 0.4.20070812).
> 
> Thanks for the bug report,
> Ary
> P.D.: It didn't break, there were just the red squiggles.
> 

OK.... <rolls eyes> It didn't /actualy/ break anything :o)

p.s.

for code formatting; could we get a "add newline between static "else" and "static if"

static if(foo == 1) bar();
else
static if(foo == 2) baz();
else
static if(foo == 3) bil();
else
static if(foo == 4) bat();

it makes commenting stuff out faster sometimes

//static if(foo == 1) bar();
//else
static if(foo == 2) baz();
//else
//static if(foo == 3) bil();
else
static if(foo == 4) bat();

vs.

//static if(foo == 1) bar();
/*else*/ static if(foo == 2) baz();
//else static if(foo == 3) bil();
else tatic if(foo == 4) bat();

Robert Fraser escribió:
> Gregor Richards Wrote:
> 
>> Ary Manzana wrote:
>>> The plugin still doesn't integrate with a compiler. We are looking at the best way to seamlessly integrate it, so that compiling programs is as easy as it can be.
>> [Warning!! Shameless plug levels at critical!]
>>
>> May I suggest integrating with DSSS? This would make your job much easier, since you wouldn't have to worry about specific compiler quirks or differences in making libraries etc on different platforms.
>>
>>   - Gregor Richards
> 
> That's certainly a good idea. However, since descent will be internally tracking changes, dependencies, etc., I'm not sure exactly how this'll work I was thinking that DSSS integration for libraries, (perhaps even for symbol lookup if that's feasible - so if a user enters an unrecognized symbol, they could click a button to look it up in all DSSS-installed libraries, automatically add the library to the build path, and automatically add the necessary imports to the source file... libraries already on the build path and modules internal to the project and other projects in the workspace will of course also be considered, like in the JDT).
> 
> Integration with the net feature would be even crazier. Imagine how awesome (if not _that_ useful...) it'd be to enter "IMG_LoadPNG_RW" or something, have a red squiggle appear below it, click three times, and have DerlictSDL-Image automatically be downloaded (in the background), installed and added to the build path, and have the import statement added to the source file. And with all that it would be trivial to have the IDE generate "dsss.conf" files.
> 
> If you have the time, I'd like to meet up at the conference to discuss all this. That being said, this is Ary's brainchild, so I'll leave the final say up to him. Also, looking over DSSS, it doesn't seem to internally keep lists of symbols, so the IDE would need to be aware of the DSSS paths and keep its own symbol:module mapings, perhaps in the workspace directory.

I also like the idea of intergrating with dsss, but integrating with a compiler comes first.

I created a patch for setting breakpoints. This patch fix a problem of not being able to set breakpoint correctly when i get the binary moved to somewhere which is not right under the ${workspace_loc} or something.

http://www.dsource.org/forums/viewtopic.php?p=16025#16025

there umm indentation lost, you can get my patch in this post

"Vladimir Panteleev" <thecybershadow@gmail.com> wrote in message
news:op.twyuciosm02fvl@irc.irastex.local...
On Sun, 12 Aug 2007 20:30:55 +0300, Ary Manzana <ary@esperanto.org.ar>
wrote:

> So, I decided to give Descent a shot, and tried to import my current project (created a new project based on an existing source directory). However, after clicking "Finish", Eclipse seemed to freeze and started eating tons of resources. I almost gave up on it finishing, when it finally "unfroze". Given that I was running Eclipse in a Linux VM (although my host is a decent machine), and the project being fairly sizeable (over 8000 lines of code), the ~5 minute analysis time doesn't sound too unreasonable - however, is it possible to add some kind of visual feedback, or if not - detect that the processing may take a long time and display a warning or something?


I'm also having this problem on a project of about 5000 lines.
It seems to kick in every now and then and lockes up for a couple of
minutes.

Simen Haugen wrote:
> "Vladimir Panteleev" <thecybershadow@gmail.com> wrote in message news:op.twyuciosm02fvl@irc.irastex.local...
> On Sun, 12 Aug 2007 20:30:55 +0300, Ary Manzana <ary@esperanto.org.ar> wrote:
> 
>> So, I decided to give Descent a shot, and tried to import my current project (created a new project based on an existing source directory). However, after clicking "Finish", Eclipse seemed to freeze and started eating tons of resources. I almost gave up on it finishing, when it finally "unfroze". Given that I was running Eclipse in a Linux VM (although my host is a decent machine), and the project being fairly sizeable (over 8000 lines of code), the ~5 minute analysis time doesn't sound too unreasonable - however, is it possible to add some kind of visual feedback, or if not - detect that the processing may take a long time and display a warning or something?
> 
> 
> I'm also having this problem on a project of about 5000 lines.
> It seems to kick in every now and then and lockes up for a couple of minutes. 

Do you mean it happens also after the project has been created? Vladimir  was talking about the freeze at the project creation.