-----Original Message-----
From: Simon D Moser [mailto:SMOSER@xxxxxxxxxx]
Sent: Wednesday, May 30, 2007 3:51 PM
To: BPEL Designer project developer discussions.
Cc: Tishkov, Vitaly V; Michael Illiger2
Subject: RE: Our Dom Facading Knowlegde
Hi Vitaly,
first I moved the discussion to the list - not even sure why this was
started in private ;-)
OK, let's start from there.
In the future I see the following 3 easy steps of 'binding' source view
(structuredTextEditor) and the DOM model:
1) create DOM model;
2) initialize the source view;
3) set the source view model to the DOM model created above.
At the moment StructuredTextEditor doesn't allow changing it's model (the
only method that changes the value of the fStructuredModel field is
deprecated private setModel(). So, we'll probably have to extend
StructuredTextEditor for our needs.
I am OK with the approach. However, the thing is that we probably must use
StructuredSourceEditor or StructuredXMLEditor or something.
Yes, your assumption is correct. Sorry for being not clear.
I'll send my proposal for separating "core" and "view" in another message
Ok, cool. I'm waiting for that one then.
OK, I see.
It seems to me that we'll need a branch for our work, am I correct?
Generally yes. I would think that a branch is the better solution here. Let
me find out how to create one (we can apply the source tab patch on the
branch right away).
Michal, do you know how this works by any chance?