Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » TMF (Xtext) » problem outline
problem outline [message #878772] Tue, 29 May 2012 22:47 Go to next message
Gianluca Viscomi is currently offline Gianluca Viscomi
Messages: 33
Registered: April 2012
Location: Italy
Member
hi

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!
Re: problem outline [message #878897 is a reply to message #878772] Wed, 30 May 2012 06:44 Go to previous messageGo to next message
Jan Koehnlein is currently offline Jan Koehnlein
Messages: 656
Registered: July 2009
Senior Member
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:
> hi
>
> 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!


--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Re: problem outline [message #890705 is a reply to message #878897] Fri, 22 June 2012 22:03 Go to previous messageGo to next message
Missing name Missing name is currently offline Missing name Missing name
Messages: 2
Registered: October 2011
Junior Member
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?
Re: problem outline [message #891005 is a reply to message #890705] Sat, 23 June 2012 18:26 Go to previous messageGo to next message
Jan Koehnlein is currently offline Jan Koehnlein
Messages: 656
Registered: July 2009
Senior Member
Try

fragment = parser.antlr.XtextAntlrGeneratorFragment {
options = {
ignoreCase = true
}
}

in your workflow (also for the XtextAntlrUiGeneratorFragment).
For identifiers, the ImportNamespacesScopingFragment has an ignoreCase
option, too.

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?
>


--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Re: problem outline [message #891803 is a reply to message #891005] Tue, 26 June 2012 05:18 Go to previous messageGo to next message
Missing name Missing name is currently offline Missing name Missing name
Messages: 2
Registered: October 2011
Junior Member
So I guess this is not possible from within the Xtext grammar itself?

Where would I have to add the fragment definition (what file)?

Thanks a lot for your help.

[Updated on: Tue, 26 June 2012 05:20]

Report message to a moderator

Re: problem outline [message #891804 is a reply to message #891803] Tue, 26 June 2012 05:31 Go to previous message
Christian Dietrich is currently offline Christian Dietrich
Messages: 6385
Registered: July 2009
Senior Member
Hi,

next to your there is a workflow that allows you to do such config changes.
(so change/not add) it there

~Christian
Previous Topic:Adding a language library to a non java project
Next Topic:Serialization - order of unordered features
Goto Forum:
  


Current Time: Fri Oct 24 08:39:49 GMT 2014

Powered by FUDForum. Page generated in 0.07806 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software