Removing D embedded in HTML feature

[Unknown W. Brackets]

In practice, none of these solutions would use HTML.  They would all use 
XML, zip-based packages (like the open office formats), or separate 
side-by-side files (like ASP.NET.)

HTML is the wrong way to solve those problems.  XML has CDATA, which 
makes it quite a lot easier to write actual code inside the XML file. 
All of these things could (and would) be formatted with a xslt 
stylesheet, which means the data is available for other things (Flash 
charts, js coolness, or even just interpretation by 3rdparty tools.)

XHTML might be "the right way" in some ways, but it hasn't really gained 
actual traction much yet (most browsers do not actually read XHTML, so 
the benefits of CDATA are unavailable.)

-[Unknown]


Bjoern wrote:
> Walter Bright schrieb:
>> Scott suggested this be removed for D 2.0. Is anyone at all using it, 
>> or have plans to use it, or can make a good case for keeping it?
>>
>> http://www.digitalmars.com/d/2.0/html.html
> 
> Please keep it.
> 
> I am conviced that "text only" is not enough for next generation code 
> editors. a few examples :
> 
> a database application could embedd an Entity Relationship model. This 
> could be a simple static graphic, or even an interactive live model 
> which generates D code. (using java applets, ActiveX, ...)
> 
> D has strong OOP features, why not having an interactive UML modeler 
> within the code.
> 
> D has builtin profiler support, why not embedding a charts, coloring 
> time critical sections.
> 
> extented Documentation support
> 
> I am convinced that, once the first HTML base D code-editor is released, 
> several new, fantastic ideas will be born.
> 
> I guess java applets can be used as code generators, code watcher 
> (safeD, without using the compiler) ....
> 
> I thinking about : "how a next generation code editor should look like" 
> for quit a while and hope to implement an HTML based (or hypertext based 
> in general) Editor for D for use in my IDE.
> 
> Bjoern
> 
>