Noel,
Fundamentally I agree with you.
But I am not in a position to expend the effort and time to write a completely new IDE, hence I opt for the path of least resistance: take something that basically works, add functionality where feasible (todo, better find / replace), and amend the code structure where I can to enable further improvements (integrated C editing). The CE IDE hasn't taken up *that* much of my time...well, apart from trying to resolve linux / gtk woes recently that is!
And John, re: CE IDE = official IDE
I agree, and know this to be mark's position and understand his desire not to go down this route. However *I* still think that having a small population of trusted developers drawn from the community, all working on an official IDE (i.e. not just mark & skid) is a viable option. So not 100% open, but not 100% closed as it is now.
I'll tell you why I won't work on it: it's the same old IDE. I'm sure you think the code is neat and creative, but the result is the same piece of trash as before. You can come up with all the creative code you want and make the insides look pretty, but in the end you're doing nothing to make the program a more desirable alternative to, say, ConTEXT, Crimson, and other editors that provide the required functionality of a programmer's editor.
If you want to see real progress, focus on the design and not the code. Scrap what you have now, call it trash, print out the source and burn it if you like, but stop going down the road the default IDE took. You're only heading to the waste-bin if you go there. Something you should do is take a look at good editors, like those mentioned above, and Blitz-specific editors and see what they have in common. Take Visual Blitz, Project Studio, Protean, and such and figure out what makes/made them great.
If you want to see real progress, focus on the design and not the code. Scrap what you have now, call it trash, print out the source and burn it if you like, but stop going down the road the default IDE took. You're only heading to the waste-bin if you go there. Something you should do is take a look at good editors, like those mentioned above, and Blitz-specific editors and see what they have in common. Take Visual Blitz, Project Studio, Protean, and such and figure out what makes/made them great.
Fundamentally I agree with you.
But I am not in a position to expend the effort and time to write a completely new IDE, hence I opt for the path of least resistance: take something that basically works, add functionality where feasible (todo, better find / replace), and amend the code structure where I can to enable further improvements (integrated C editing). The CE IDE hasn't taken up *that* much of my time...well, apart from trying to resolve linux / gtk woes recently that is!
And John, re: CE IDE = official IDE
Undoubtedly. Unfortunately, I think the chance of this actually happening is virtually nil.
I agree, and know this to be mark's position and understand his desire not to go down this route. However *I* still think that having a small population of trusted developers drawn from the community, all working on an official IDE (i.e. not just mark & skid) is a viable option. So not 100% open, but not 100% closed as it is now.