Thanks for the fast response.
Let's see:
- I'm not sure about the Styled Text Engine, but he wrote in his blog: "My
first project was to create a text engine that could handle more than one
font, size, and color at a time." so if this is the same, then
theoretically yes, something like the BTextView.
- As far as i know, there is already some patches to get BeIDE working *on*
and *with* gcc5.
- Ofc, i understand your point, and makes sense, but as BeIDE developed
exclusively for Haiku and as it using extensively the BeOS features
(plugins and scripting, etc.), it would be nice to not let rotten somewhere
in a storage room, but to make it available. I don't mean it must be
included in Haiku, i don't propose to make it default, but it got a not so
bad code-editor, console, project handling features, so maybe somebody
would see opportunities to get it updated, or extend it.
I had much experiences with BeIDE, and it wasn't bad, sure, we cannot
compare it to any current IDE.
Thanks.
--miqlas
2017-07-18 13:42 GMT+02:00 Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>:
18 juillet 2017 12:55 "miqlas" <miqlas@xxxxxxxxx> a écrit:
And there is that part from Hiroshi Lockheimer. He is at Google rightnow, and as he wrote a nice
article about the old times at Be [hiroshi-lockheimer ] i think he will let us
https://www.linkedin.com/pulse/so-how-did-you-get-here-
reuse his code.
If this is the same thing powering BTextView, we have a replacement in
Haiku already. Or is it a different thing?
is possible to relicense
So my plan is to contact the current copyright holders and asking if it
the IDE for us. The question is: have anybody tried it already? Havesomebody got more information
about the current copyright holders? Does my plan actually makes sense?Opinions, ideas?
Assuming they even know where the source is, which is far from obvious.
What are your plans following getting your hands on the sources?
What you will get is 15 to 20 years old sourcecode, which will require a
lot of work to just get it building on Haiku, getting people to be familiar
with it, etc. This is a rather large task, and you need some (or let's say
at least one) developer up for it. You can't get the thing open sourced and
then just let the HaikuArchive guy handle it.
Personally I would rather put my bet on writing something using modern
tools. As I mentionned on IRC, we have the ycm engine for code completion,
which could be ported from Linux. We have Koder on the way to becoming a
good modern editor, or vim for people who prefer that. We have DontWorry
which is open source and could be used as an interface between ycm and the
BeAPI world (and Koder in particular). We have Paladin, which is far from
perfect, but a good start for an IDE the Haiku way.
This is where the future lies: a combination of independant modules: a
text editor, a code completion engine, a project manager, a build system.
Each of these should be independant and replaceable. As I like to put it,
bring the UNIX philosophy to the GUI age. Small tools which you can combine
in creative and useful ways.
As a result, I have no interest in messing with 20 years old monolithic
applications like BeIDE. Let them rest in the 1990s and show how Haiku is a
suitable platform for a much better future.
--
Adrien.
