RESOLVED FIXED34144
Web Inspector: Implement simple highlighter for HTML.
https://bugs.webkit.org/show_bug.cgi?id=34144
Summary Web Inspector: Implement simple highlighter for HTML.
Pavel Feldman
Reported 2010-01-25 11:42:48 PST
This change also introduces parse state that is necessary to keep generated lexer code compact.
Attachments
[PATCH] Proposed change. (252.42 KB, patch)
2010-01-25 11:44 PST, Pavel Feldman
no flags
[PATCH] Proposed change (style fix). (252.43 KB, patch)
2010-01-25 11:56 PST, Pavel Feldman
no flags
[PATCH] Same with better naming and CSS tokenizer bonus. (331.38 KB, patch)
2010-01-25 14:23 PST, Pavel Feldman
timothy: review+
Pavel Feldman
Comment 1 2010-01-25 11:44:48 PST
Created attachment 47361 [details] [PATCH] Proposed change.
WebKit Review Bot
Comment 2 2010-01-25 11:48:20 PST
Attachment 47361 [details] did not pass style-queue: Failed to run "WebKitTools/Scripts/check-webkit-style" exit_code: 1 Skipping input 'WebCore/inspector/front-end/JavaScriptTokenizer.js': Can't open for reading WebCore/inspector/front-end/TokenizerForHTML.js:78: Line contains tab character. [whitespace/tab] [5] WebCore/inspector/front-end/TokenizerForHTML.js:79: Line contains tab character. [whitespace/tab] [5] Total errors found: 2 If any of these errors are false positives, please file a bug against check-webkit-style.
Pavel Feldman
Comment 3 2010-01-25 11:56:56 PST
Created attachment 47364 [details] [PATCH] Proposed change (style fix). Please ignore style failures in the removed file.
Timothy Hatcher
Comment 4 2010-01-25 12:09:29 PST
Comment on attachment 47361 [details] [PATCH] Proposed change. I prefer HTMLTokenizer over TokenizerForHTML, like you had JavaScriptTokenizer. It is a better class name. (Even though the new name keeps the files together.) Otherwise r+.
Pavel Feldman
Comment 5 2010-01-25 14:23:32 PST
Created attachment 47368 [details] [PATCH] Same with better naming and CSS tokenizer bonus.
Timothy Hatcher
Comment 6 2010-01-25 17:29:13 PST
Comment on attachment 47368 [details] [PATCH] Same with better naming and CSS tokenizer bonus. > - this._tokenizer = new WebInspector.JavaScriptTokenizer(); > + this._tokenizer = new WebInspector.SourceCSSTokenizer(); What tokenizer should this be set to?
Pavel Feldman
Comment 7 2010-01-25 21:41:33 PST
(In reply to comment #6) > (From update of attachment 47368 [details]) > > - this._tokenizer = new WebInspector.JavaScriptTokenizer(); > > + this._tokenizer = new WebInspector.SourceCSSTokenizer(); > > What tokenizer should this be set to? This is going to be determined by the mimeType passed to the editor (simple mapping). Currently just hardcoded for testing. I think I am one patch away form the editor as a viewer.
Pavel Feldman
Comment 8 2010-01-26 02:19:11 PST
Committing to http://svn.webkit.org/repository/webkit/trunk ... R WebCore/inspector/front-end/JavaScriptTokenizer.js => WebCore/inspector/front-end/SourceJavaScriptTokenizer.js R WebCore/inspector/front-end/JavaScriptTokenizer.re2js => WebCore/inspector/front-end/SourceJavaScriptTokenizer.re2js M WebCore/ChangeLog M WebCore/WebCore.gypi M WebCore/WebCore.vcproj/WebCore.vcproj A WebCore/inspector/front-end/SourceCSSTokenizer.js A WebCore/inspector/front-end/SourceCSSTokenizer.re2js A WebCore/inspector/front-end/SourceHTMLTokenizer.js A WebCore/inspector/front-end/SourceHTMLTokenizer.re2js M WebCore/inspector/front-end/TextEditorHighlighter.js M WebCore/inspector/front-end/WebKit.qrc M WebCore/inspector/front-end/inspector.html Committed r53846
Note You need to log in before you can comment on or make changes to this bug.