2007/6/11, Sam Ruby: > > > The reason I think keeping Twintsam separate from html5lib is better > > is that I'd like Twintsam to first act as an XmlReader (i.e. without > > reordering elements, such as moving things into <head>) then add a > > "tree builder" on top of this. This is I think enough different from > > html5lib's design to deserve its own development tree, roadmap et al. > > As opposed to html5lib which acts first as a tokenizer (i.e. without > reordering elements, such as moving thigs into <head>) then adds a > "html5parser" on top of this, ultimately calling out into a pluggable > treebuilder of your choice.
Well, the html5parser also deals with misnested tags, optional tags et al. Please note also that I must say I never went deep down into the html5parser code and design, and haven't thought much about how to do it in Twintsam (I might have done it back in January but, if so, I forgot everything); so I might be wrong about Twintsam and html5lib being so different. > Just something to think about. What you chose to work on, and where you > chose to do it is certainly up to you. My main interests are to see if > we can grow a sustainable developer community and to build a > comprehensive test suite. Actually, one of my "problems" with having the Ruby and Python code into the same repository is that there aren't two clearly distinct branches, so I'm "polluted" with every check-in happening in the Ruby port. Maybe just moving some folders could solve everything, i.e.: - trunk/python/ -> setup.py, parse.py, python examples, test_* scripts, and maybe src/ renamed to html5lib/ to ease imports from within unit tests (you just need to add ".." ahead of sys.path) - trunk/ruby/ -> everything relative to the Ruby port (seems like what exists today) - trunk/tests/ -> only unit-tests data (i.e. the tokenizer/, encoding/, tree-construction/ and serializer/ subfolders), not linked to any programming language (but maybe retrieved from within python/ and ruby/ branches using svn:external; see below for the rationale) That way I could just check-out trunk/python/ and not have anything related to ruby. We could then add other ports in, say, trunk/php/ Again, just thinking out loud ;-) .. and maybe that's just me and I should try to live with this ;-) -- Thomas Broyer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to html5lib-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/html5lib-discuss?hl=en-GB -~----------~----~----~----~------~----~------~--~---
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4