[haiku-development] Re: Creating or porting an IDE [was Re: What's the status of Haiku?]
- From: "Wayne Peter Corwin" <wayne.peter.corwin@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 1 Sep 2014 19:47:42 +0200
> Sent: Monday, September 01, 2014 at 7:33 PM
> From: "Stephan Aßmus" <superstippi@xxxxxx>
> To: haiku-development@xxxxxxxxxxxxx
> Subject: [haiku-development] Re: Creating or porting an IDE [was Re: What's
> the status of Haiku?]
>
>
> Am 31.08.2014 um 17:01 schrieb Earl Pottinger (Redacted sender
> "earl_colby_pottinger@xxxxxxxxx" for DMARC) <dmarc-noreply@xxxxxxxxxxxxx>:
>
> > What would a good IDE for Haiku look like and what features are really
> > needed?
>
> An IDE needs to be better than what we have now. To me this means that there
> is a lot more, well, „integration“. And by that I don’t mean to put make file
> management into the app, or GCC error and warning parsing, or everything in a
> single window.
>
> An IDE needs to use a compiler as a library (so probably Clang, not GCC). And
> it needs to have full knowledge of the build-system (jam integration), so it
> sees the code like the compiler sees it (regarding defines and includes).
>
> I would like the features that are possible by that, like
> * error highlighting as I type
> * code completion
> * looking up declarations
> * finding /all/ places where a method is called
> * refactoring (at least renaming)
I believe wx is ported to Haiku? That should make porting code::blocks within
reach. Not a perfect IDE, but open source and works well with clang and gcc.
Best wishes,
- wpc
Other related posts:
