Hi Jonnan, What's are your main ideas, drives, intentions or incentives as for "moving completely to" xhtml?
1) To allow for better parsing by 'external' apps? 2) To be more strict on the use of attributes, structure, naming? 3) To switch to possibly more future-proof name-space conventions? 4) To be prepared for the ubiquiteous dawn of svg? 5) To possibly improve embedability, portability and os-independence even further? 6) Do you just have that gut feeling that it might be a drawback not to make the move (any time soon)? Just in general, I find XML to be an utterly awful construct and I wish some sort of js/json dialect would be the slick kind of structure defining all web-elements, instead of this sort of bloated, exhaustively redundant, hardly readable format ...and I don't mean to just rant away on it. It's good to have reliable standards and XML surely has evolved into that for many people, just like good 'ol java did ...just can't do without main(). I'ts just that, in some respects, XML feels like a straitjacket which you'd rather want to take off, asap. By the way... is there any svg playground of yours to be played with out there? Tobias. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en -~----------~----~----~----~------~----~------~--~---
