RE: [cdt-core-dev] Build Console Proposal (was: Build on Windows)

["Schaefer, Doug" <dschaefer@xxxxxxxxxxxx>]

Good point, Dave, this was actually on purpose.  Whenever I do a build that
produces a lot of errors, it is usually the first one or two that cause the
rest.  If the build console only kept the last n lines, you would lose this
important information.

Doug Schaefer
Senior Staff Software Engineer
Rational Software - IBM Software Group
Ottawa (Kanata), Ontario, Canada

-----Original Message-----
From: David Inglis [mailto:dinglis@xxxxxxx] 
Sent: Tuesday, February 25, 2003 8:59 AM
To: cdt-core-dev@xxxxxxxxxxx
Subject: Re: [cdt-core-dev] Build Console Proposal (was: Build on Windows)

Ok, I finally got to look at this... a few comments,

It doesn't really look like a equivalent replacement of what is there now,
it would
appear the this console, once full, no longer shows its output. Where the
current
one will continue to display the last 'n' lines (where n is what you limit
is).



Schaefer, Doug wrote:
> I was wondering if Dave Inglis and anyone else out there could take a look
> at this patch and see if it is something we should put in for the build
> console as a Text widget.  After testing it out, I didn't get that "Wow"
> feeling that it is significantly better.  I'm also not sure whether it
fixes
> the problem that the 512 byte blocking was intented to fix.  It is,
however,
> a much lighter weight implementation for the build console.
> 
> Thanks,
> Doug Schaefer
> Senior Staff Software Engineer
> Rational Software - IBM Software Group
> Ottawa (Kanata), Ontario, Canada
> 
> -----Original Message-----
> From: Schaefer, Doug [mailto:dschaefer@xxxxxxxxxxxx] 
> Sent: Thursday, February 20, 2003 4:35 PM
> To: 'cdt-core-dev@xxxxxxxxxxx'
> Subject: RE: [cdt-core-dev] Build on Windows
> 
> Well, I gave it a shot and have the Build console working with a simple
Text
> widget.  Seems to be a bit faster...
> 
> What I would like to know is which platforms were experiencing the trouble
> with voluminous build output.  I haven't really been able to reproduce
such
> trouble on Windows or Linux/GTK with Eclipse 2.0.2.
> 
> Doug Schaefer
> Senior Staff Software Engineer
> Rational - the software development company
> Ottawa (Kanata), Ontario, Canada
>  
> 
> -----Original Message-----
> From: Schaefer, Doug [mailto:dschaefer@xxxxxxxxxxxx] 
> Sent: Tuesday, February 18, 2003 11:12 AM
> To: 'cdt-core-dev@xxxxxxxxxxx'
> Subject: RE: [cdt-core-dev] Build on Windows
> 
> I finally got finished going through it all and you're absolutely right
> Dave.  The TextViewer makes life much simpler.  However, it looks like it
> doesn't scale to our needs with the build console.  And, yes, to replace
it
> looks like a significant chunk of work.  I've raised a bug report and
we'll
> see when it manages to get to the top of the priority list (sounds like a
> good little project for someone starting to look at UI work...).
> 
> Cheers,
> Doug Schaefer
> Senior Staff Software Engineer
> Rational - the software development company
> Ottawa (Kanata), Ontario, Canada
> 
> -----Original Message-----
> From: David Inglis [mailto:dinglis@xxxxxxx] 
> Sent: Tuesday, February 18, 2003 10:29 AM
> To: cdt-core-dev@xxxxxxxxxxx
> Subject: Re: [cdt-core-dev] Build on Windows
> 
> The only problem with using this low-level approach is you will need to
> implement your own document type management for each projects build
> output. Each projects build output will need to be maintained separately
> from the widget since selecting a project needs to switch the build
console
> contents to the build output for that project. (using the
> IDocument/StyleText
> widget make this very simple).
> 
> Chris McKillop wrote:
> 
>>>Great question.  From what I've seen so far, there is something else
>>>throttling the Console, and my guess, it's the performance of the
>>
>>replace()
>>
>>
>>>method on the document.  But I need to investigate this a little more.
>>>
>>>Could the creator of this code comment more (before we go and wreck it
>>
>>;-)?
>>
>>
>>:) Also, the StyledText widget is a pure java editor, while the Text
> 
> widget
> 
>>is a pure native.  And so Text will always outperform StyledText.
>>
>>    chris
>>
>>
>>_______________________________________________
>>cdt-core-dev mailing list
>>cdt-core-dev@xxxxxxxxxxx
>>http://dev.eclipse.org/mailman/listinfo/cdt-core-dev
> 
> 
> 
> _______________________________________________
> cdt-core-dev mailing list
> cdt-core-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-core-dev
> _______________________________________________
> cdt-core-dev mailing list
> cdt-core-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-core-dev
> _______________________________________________
> cdt-core-dev mailing list
> cdt-core-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-core-dev
> 


_______________________________________________
cdt-core-dev mailing list
cdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-core-dev