<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
> cm3ide <BR> > more later<BR>
<BR>Being at the mercy of the rapidly changing web browsers is a very sharp double edged sword.<BR>
<BR>
<BR>An IDE with no editor and no debugger..is not an IDE.<BR>Maybe it is a source browser.<BR>
Maybe an IDE is not worth it.<BR>
People are very slow to change editors.<BR>
Debuggers are hard to write.<BR>
Probably better to try integrating with an actual IDE like VisualStudio or Eclipse.<BR>
Or to have a decent enough language, library, build system, that the language doesn't<BR>
need such costly support. Maybe we do have such a think.<BR>
<BR>
<BR>Hyperlinking the source is nice, but all I need is "find in files".<BR>I can open the documentation from a file system browser, which<BR>open it in a web browser. I should just be able to use online<BR>documentation anyway, not local stuff.<BR>
<BR>
<BR>
Having the real compiler output enough information<BR>
such that writing other lanugage-aware tools, such<BR>
as hyperlinked source generation, is also good.<BR>
Too many systems have their IDE write another parser,<BR>
and no two parsers agree. However it is a tough problem,<BR>
because the compiler's job is different than a source<BR>
browser. For example, a compiler must reject incorrect<BR>
source, but a source browser should be lenient.<BR>
<BR>
<BR>Relying on the browser is a cheap way to get a somewhat<BR>decent somewhat portable very limited gui.<BR>That's about it.<BR>
<BR>
<BR>I don't think it is fixable.<BR>It's just pretty much all wierd and wrong.<BR>
I was quite shocked the first time I used it, having<BR>
heard it described as an IDE.<BR>
<BR>
<BR> - Jay<BR> </body>
</html>