Brilliant.
I'm glad to see a protobuf descriptor editor come out of Google. I wrote my own using the XText 1.0 SDK but it was quick and dirty, I like this one much better.
There are a few corner cases missing from the syntax however. I know I had a lot of trouble dealing with them using XText because the protobuf grammar has some oddities in it, especially when it comes to enumerations and custom options.
The first couple things I noticed when I pulled up the protos I use are:
1) Imports are required to exist in the same directory as the importing proto. Is this intentional? When I used importURI in XText it allowed the files to simply be present in the same project, which allowed for more cleanly managing what proto files are part of the project and which are simply imports. (change in XText 2.0?)
2) Enum Value options are not supported by the current grammar.
i.e.
...where the country code type is defined earlier in the same file and "
evo.name" is defined by an import.
3) Custom options that are enumerations are not supported by the current grammar:
I need to pull down the project and see if these would be easy to add to the grammar, but I would be glad to contribute to the project as I've been meaning to release my own for some time now and this is a much better starting point. Once I get a better look at the issues and possibly some solutions I'll post them to the project's issue tracker.
Thanks for all the hard work - I'm very appreciative and I'm certain the rest of the protobuf community will be as well.
-Ben Wright