Add attribute information table so we generate correct setters.

Add attribute information table so we generate correct setters.
It is from the spec, with things removed that are not supported yet.
We might want to replace most of this with mirrors. But even then, we still need the renames.
Fixes issue #112

Committed: https://github.com/dart-lang/dart-web-components/commit/c259ef6

[sqs, 2012-10-27 00:38:11]

Any reason for not including TextAreaElement.value?
http://dev.w3.org/html5/spec-LC/the-button-element.html#the-textarea-element

[Siggi Cherem (dart-lang), 2012-10-27 00:46:45]

lgtm % some style/naming questions. I'm not sure about the right answer either,
so I'd be ok with the current names. :)

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/emitters.dart
File lib/src/emitters.dart (right):

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/emitters.dart#...
lib/src/emitters.dart:225: var allowedTags = htmlAttributeTags[name];
nit: maybe some alternative name? allowedTags rings a different bell. Maybe
tagsWithAttribue, tagsAllowingAttribute, validTags?

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/emitters.dart#...
lib/src/emitters.dart:228: var renamed = elementFieldRenames[name];
elementFieldRenames => domToDartHtml?

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/html5_utils.dart
File lib/src/html5_utils.dart (right):

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/html5_utils.da...
lib/src/html5_utils.dart:134: const allHtmlElements = const ['*'];
nit: => ALL_HTML_ELEMENTS? 
or are we leaning towards not using CAPS for constants?

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/html5_utils.da...
lib/src/html5_utils.dart:148: * renamed.
... in 'dart:html'?

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/html5_utils.da...
lib/src/html5_utils.dart:194: 'disabled': const ['button', 'fieldset', 'input',
'keygen', 'optgroup', 'option', 'select', 'textarea'],
80 col? (here & below)

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/html5_utils.da...
lib/src/html5_utils.dart:271: const elementFieldRenames = const {
maybe rename to also use ALL_CAPS

[Jennifer Messerly, 2012-10-29 18:08:29]

On 2012/10/27 00:38:11, sqs wrote:
> Any reason for not including TextAreaElement.value?
> http://dev.w3.org/html5/spec-LC/the-button-element.html#the-textarea-element

Ugh. Good catch! It's not listed in:
http://dev.w3.org/html5/spec/section-index.html#attributes-1

which means my TODO was right :(  ... the table I used does not have all the
relevant DOM properties.

I'll go through the DOM IDL and make sure they're getting captured. Sorry about
that. Expect and update to this CL.

[Jennifer Messerly, 2012-10-30 06:08:45]

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/html5_utils.dart
File lib/src/html5_utils.dart (right):

https://chromiumcodereview.appspot.com/11315020/diff/1/lib/src/html5_utils.da...
lib/src/html5_utils.dart:134: const allHtmlElements = const ['*'];
On 2012/10/27 00:46:45, Siggi Cherem (dart-lang) wrote:
> nit: => ALL_HTML_ELEMENTS? 
> or are we leaning towards not using CAPS for constants?

IMO, we should not use CAPS.

It does not really make sense as a convention. It's supposed to be easy to
switch a fields to a getter and vice versa, but that doesn't work if they have a
different naming scheme. We had this problem when we were playing around with
specifying Font styles in code. It looked really silly too
(FontFace.SANS_SERIF). C# avoided CAPS for the same reason
(http://stackoverflow.com/questions/242534/c-sharp-naming-convention-for-const...)

Granted, you could argue that SCREAMING_CAPS is an indication you can use it in
a const expression. But that hardly ever matters, and if you use a non-const as
a const, you already get an error from all the tools.

[Jennifer Messerly, 2012-11-06 02:56:43]

PTAL. New approach uses compile time mirrors to get information from dart:html.
The resulting metadata is then checked in.

Note: we won't want to read this automatically any time soon. It takes ~14
seconds(!) to read dart:html.

[Siggi Cherem (dart-lang), 2012-11-06 03:20:36]

lgtm!

https://chromiumcodereview.appspot.com/11315020/diff/10001/build/gen_html_set...
File build/gen_html_setters.dart (right):

https://chromiumcodereview.appspot.com/11315020/diff/10001/build/gen_html_set...
build/gen_html_setters.dart:7: // TODO(jmesserly): should be importing packages.
packages => a dartdoc package?

https://chromiumcodereview.appspot.com/11315020/diff/10001/lib/src/emitters.dart
File lib/src/emitters.dart (right):

https://chromiumcodereview.appspot.com/11315020/diff/10001/lib/src/emitters.d...
lib/src/emitters.dart:240: typeName = htmlElementExtends[typeName];
emulating dart semantics, yay!  -- sarcasm ;-)

https://chromiumcodereview.appspot.com/11315020/diff/10001/lib/src/emitters.d...
lib/src/emitters.dart:747: var elementName = htmlElementNames[node.tagName];
you probably want to fix it here too

[Jennifer Messerly, 2012-11-06 03:51:57]

https://chromiumcodereview.appspot.com/11315020/diff/10001/build/gen_html_set...
File build/gen_html_setters.dart (right):

https://chromiumcodereview.appspot.com/11315020/diff/10001/build/gen_html_set...
build/gen_html_setters.dart:7: // TODO(jmesserly): should be importing packages.
On 2012/11/06 03:20:36, Siggi Cherem (dart-lang) wrote:
> packages => a dartdoc package?

Done.

https://chromiumcodereview.appspot.com/11315020/diff/10001/lib/src/emitters.dart
File lib/src/emitters.dart (right):

https://chromiumcodereview.appspot.com/11315020/diff/10001/lib/src/emitters.d...
lib/src/emitters.dart:240: typeName = htmlElementExtends[typeName];
On 2012/11/06 03:20:36, Siggi Cherem (dart-lang) wrote:
> emulating dart semantics, yay!  -- sarcasm ;-)

Hah, yeah :\. OTOH, it's kind of Web IDL semantics, so it's not as bad as it
looks :)

https://chromiumcodereview.appspot.com/11315020/diff/10001/lib/src/emitters.d...
lib/src/emitters.dart:747: var elementName = htmlElementNames[node.tagName];
On 2012/11/06 03:20:36, Siggi Cherem (dart-lang) wrote:
> you probably want to fix it here too

I don't think "new autogenerated.UnknownElement" would do the right thing,
though. I'll leave this alone since your change affects it too :)