The default behavior out the outline is to show the "name" attribute of
the elements. Have a look at the docs how to customize that.
If you're referring to the sample 'Greetings' grammar, the root node
does not have such an attribute, that's why it show unnamed.
By default, Xtext languages are case sensitive, so "HELLO" will not
match the keyword "Hello".
Am 30.05.12 00:47, schrieb Gianluca Viscomi:
> When for the first time I ran the example "HELLO WORLD", following the
> lead of the outline seems to not work because the result is:
> parent node as the file name and then two strings <unnamed>!
> Can anyone tell me if I am the attvare otline somewhere!
> Thanks a lot!
in your workflow (also for the XtextAntlrUiGeneratorFragment).
For identifiers, the ImportNamespacesScopingFragment has an ignoreCase
Am 23.06.12 00:03, schrieb Missing name Mising name:
> Jan: Quote:
>> By default, Xtext languages are case sensitive, so "HELLO" will not
>> match the keyword "Hello".
> Is there a way to match a keyword on a case-insensitive manner?