Initial cut at having the enum objects from the spec generated as classes with public static string…

Initial cut at having the enum objects from the spec generated as classes with public static strings.
Type/enum aren't being generated yet.

R=paulberry@google.com, scheglov@google.com

Committed: https://code.google.com/p/dart/source/detail?r=39240

[Paul Berry, 2014-08-13 23:53:24]

lgtm

https://codereview.chromium.org/462253005/diff/40001/editor/tools/plugins/com...
File
editor/tools/plugins/com.google.dart.server/src/com/google/dart/server/generated/types/SearchResultKind.java
(right):

https://codereview.chromium.org/462253005/diff/40001/editor/tools/plugins/com...
editor/tools/plugins/com.google.dart.server/src/com/google/dart/server/generated/types/SearchResultKind.java:26:
public static final String DECLARATION = "DECLARATION";
We're currently inconsistent about documenting enum values in the spec.  If I'm
not mistaken, SearchResultKind is the only class where we document the
individual enum values and not just the enum type.  I'm hoping that in the
future we can add documentation to more enum values.

When such documentation is present, let's go ahead and generate the
corresponding docstrings.

[scheglov, 2014-08-14 02:39:10]

LGTM

[jwren, 2014-08-14 05:21:50]

https://codereview.chromium.org/462253005/diff/40001/editor/tools/plugins/com...
File
editor/tools/plugins/com.google.dart.server/src/com/google/dart/server/generated/types/SearchResultKind.java
(right):

https://codereview.chromium.org/462253005/diff/40001/editor/tools/plugins/com...
editor/tools/plugins/com.google.dart.server/src/com/google/dart/server/generated/types/SearchResultKind.java:26:
public static final String DECLARATION = "DECLARATION";
Agreed!  At first I had all of the comment blocks generated but most were empty.
 Couldn't figure out a way to check for a non-empty comment to conditionally
include it, so I just took it out.

On 2014/08/13 23:53:24, Paul Berry wrote:
> We're currently inconsistent about documenting enum values in the spec.  If
I'm
> not mistaken, SearchResultKind is the only class where we document the
> individual enum values and not just the enum type.  I'm hoping that in the
> future we can add documentation to more enum values.
> 
> When such documentation is present, let's go ahead and generate the
> corresponding docstrings.

[jwren, 2014-08-14 05:23:06]

Committed patchset #4 manually as 39240 (presubmit successful).