Josh Simmons: > So simple 2d graphics ey? vector or raster based? immediate rendering > or scene graph representation? animation? fonts? textures?
Raster, immediate rendering, no need to specify animations, basic support for fonts and textures. Leaving most things out is not a problem here. Time ago someone has shown here a nice D module that works on Windows, Linux, that's is short. This module doesn't replace other graphics libs or GUI modules, it's something simple and small for small purposes. > XML ey? SAX, DOM, Pull, Data Binding? XPath? XSLT? > > The problem with php isn't just it's awesome naming, it's the fact > that anything that seemed like something somebody might use was added > as opposed to limiting itself to the must-haves. Some people like wide libraries like Python (batteries included), others don't like that. Both choices have their serious advantages and serious disadvantages. There are not general rules to solve this problem, each case needs to be discussed. I think a good JSON module needs to be in Phobos, while for XML maybe it just needs a standard D API (this also comes from practical size considerations: a JSON module is probably small. A good XML module will probably become large). Bye, bearophile
