You can open a text based resource with a standard EMF editor already -
the textual form is just a type of serialization.

Not sure I understand what you are trying to do. It sounds like you have
a resource in XMI form and you want to edit it as text. Is that correct?

Regards
- henrik

On 8/31/11 6:57 PM, Vitaly Savickas wrote:
> Hi,
>
> I am completely new to Xtext, and first impression is very good:) I've
> managed to generate an editor for my existing ecore model. Now what I
> already have is a well-built Eclipse-based platform that has its own
> resources, not even EMF compatible. But there is an EMF-based
> implementation of resource that persists EMF model to these specific
> resources, which allows to open them with let's say standard EMF editor.
> Now what would be cool is to customise the generated Xtext editor so
> that it uses the existing EMF-based resource for persistence i.e.
> loading/saving. Is it possible and where to start?
>
> Regards,
> Vitaly

But platform can read the XMI if the parser is installed - it is loaded
just like any other resource. It is only if you need to send the model
someplace where the parser is not present that you would need an XMI
representation of it. Likewise, if you receive a model in XMI, you can
simply load it, serialize it to text and save it.

You could probably come up with a scheme that creates the text on the
fly, user edits, and when saving, it is saved in XMI. The problem is
that you loose all textual information that is not stored in the model.
Each time the text is opened it is the auto-formatted/serialied result
that is presented. Most notably, comments will be missing.

It is probably better to run a builder that synchronizes between a
textual representation and xmi. (If the text does not exist, it is
created from the xmi, and after that, the xmi is synched to changes in
the text).

- henrik

On 9/1/11 11:21 AM, Vitaly Savicks wrote:
> Yes, the file is in XMI (but not standard) and I need to persist it in
> this format for platform to understand it, not in plain text. The
> generated Xtext editor stores it as plain text. So my question is simply
> how to customise the generated editor to persist it as needed by
> platform, essentially to use existing custom resource implementation
> which does correct XMI persistence via save/load methods.
>
> Regards,
> Vitaly
>
> Quote:
>> You can open a text based resource with a standard EMF editor already -
>> the textual form is just a type of serialization.
>>
>> Not sure I understand what you are trying to do. It sounds like you have
>> a resource in XMI form and you want to edit it as text. Is that correct?
>>
>> Regards
>> - henrik
>>
>> On 8/31/11 6:57 PM, Vitaly Savickas wrote:
>> > Hi,
>> >
>> > I am completely new to Xtext, and first impression is very good:) I've
>> > managed to generate an editor for my existing ecore model. Now what I
>> > already have is a well-built Eclipse-based platform that has its own
>> > resources, not even EMF compatible. But there is an EMF-based
>> > implementation of resource that persists EMF model to these specific
>> > resources, which allows to open them with let's say standard EMF
>> editor.
>> > Now what would be cool is to customise the generated Xtext editor so
>> > that it uses the existing EMF-based resource for persistence i.e.
>> > loading/saving. Is it possible and where to start?
>> >
>> > Regards,
>> > Vitaly
>