Are you ready to switch to HTML parsing permanently?

Poll: A global switch to HTML parsing

Are you ready?

donP	#24183 2010-04-18 17:55
Members	# urlkiller :i dont know why this should be such a problem having the user choose at installation or via config wich parser they would like to use? Migration is easy i think so everything should be ok with the HTML solution for me... there is no realy difference then. The problem is that a few guys won't abandon BBCodes in favor of HTML and so, the presence of two parsing methods (to preserve compatibility) would suck, only increasing database and slowing down the Core. For that reason I think we have to make te ability to choose parsing method in config.php and let go the core and database with only ONE parser... urlkiller: i have faith that you guys will surprise me with a cool innovative new "Textboxer" CKEditor is a very very good WYSIWYG editor, and with HTML parsing I wouldn't need other tools. in [color=#729FCF][b]BLUES[/b][/color] I trust

donP

#24183 2010-04-18 17:55

# urlkiller :i dont know why this should be such a problem having the user choose at installation or via config wich parser they would like to use? Migration is easy i think so everything should be ok with the HTML solution for me... there is no realy difference then.

The problem is that a few guys won't abandon BBCodes in favor of HTML and so, the presence of two parsing methods (to preserve compatibility) would suck, only increasing database and slowing down the Core. For that reason I think we have to make te ability to choose parsing method in config.php and let go the core and database with only ONE parser...

urlkiller:
i have faith that you guys will surprise me with a cool innovative new "Textboxer"

CKEditor is a very very good WYSIWYG editor, and with HTML parsing I wouldn't need other tools.

in [color=#729FCF][b]BLUES[/b][/color] I trust

Yes, if migration is automated	83.3%	65
No, never	1.3%	1
Please support multiple parsers, despite it is hard to maintain!	15.4%	12