|
|
|
|
|
|
Re: CSS Validation [message #1005743 is a reply to message #1005727] |
Mon, 28 January 2013 13:46 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Hi,
No offense taken ;-) - I guess because the parser is generated upgrading
Xtext to 2.4.0 can't lead to such a problem. So if it works with 2.3.1
it will still work with 2.4.0.
Knowing what Steven has installed would help to find out who is the one
to blame.
Tom
Am 28.01.13 13:31, schrieb Sebastian Zarnekow:
> Sorry Tom, didn't meant to blame e(fx)clipse for that one. The e4 css
> stuff sounds more likely to cause the issue.
>
> Regards,
> Sebastian
>
> Am 28.01.13 13:20, schrieb Tom Schindl:
>> e(fx)clipse is perfectly happy with .9em and translate it to what it is
>> 0.9em ;-) but I'm running with xtext 2.3.1 have not yet tried 2.4.0.
>>
>> It could also be the e4 css editor, which is also based on xtext
>>
>> Tom
>>
>> Am 28.01.13 09:55, schrieb Sebastian Zarnekow:
>>> Am 27.01.13 15:07, schrieb Steven Spungin:
>>>> I do not see any installed plugin with xtext and css in the name.
>>>> Which
>>>> feature would have (or should have) installed the css validator?
>>>
>>> Probably e(fx)clipse? I'm not sure - don't know each and every
>>> application of Xtext.
>>>
>>> Regards,
>>> Sebastian
>>
>
>
|
|
|
Re: CSS Validation [message #1005871 is a reply to message #1005743] |
Tue, 29 January 2013 07:18 |
Sebastian Zarnekow Messages: 3118 Registered: July 2009 |
Senior Member |
|
|
Hi Tom,
yes, upgrading to 2.4.0 but still using e(fx)clipse that was compiled to
2.3.1 will lead to all sorts of problems but not this one :-)
Regards,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 28.01.13 14:46, schrieb Tom Schindl:
> Hi,
>
> No offense taken ;-) - I guess because the parser is generated upgrading
> Xtext to 2.4.0 can't lead to such a problem. So if it works with 2.3.1
> it will still work with 2.4.0.
>
> Knowing what Steven has installed would help to find out who is the one
> to blame.
>
> Tom
>
> Am 28.01.13 13:31, schrieb Sebastian Zarnekow:
>> Sorry Tom, didn't meant to blame e(fx)clipse for that one. The e4 css
>> stuff sounds more likely to cause the issue.
>>
>> Regards,
>> Sebastian
>>
>> Am 28.01.13 13:20, schrieb Tom Schindl:
>>> e(fx)clipse is perfectly happy with .9em and translate it to what it is
>>> 0.9em ;-) but I'm running with xtext 2.3.1 have not yet tried 2.4.0.
>>>
>>> It could also be the e4 css editor, which is also based on xtext
>>>
>>> Tom
>>>
>>> Am 28.01.13 09:55, schrieb Sebastian Zarnekow:
>>>> Am 27.01.13 15:07, schrieb Steven Spungin:
>>>>> I do not see any installed plugin with xtext and css in the name.
>>>>> Which
>>>>> feature would have (or should have) installed the css validator?
>>>>
>>>> Probably e(fx)clipse? I'm not sure - don't know each and every
>>>> application of Xtext.
>>>>
>>>> Regards,
>>>> Sebastian
>>>
>>
>>
>
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03977 seconds