Question Migrating Sculptor to TMF xText

[Todd Ferrell]

I've started migrating sculptor to TMF xText, when I have the time to work on it and I've made some progress, but I have a question.  oAw xText has an xTend file called org::openarchitectureware::xtext::registry::Modelloader.ext which delegates to CachingModelLoad.java.  ModelLoader.ext is referenced by sculptor's GenExtensions.ext.  Is there a TMF xText equivalent to ModelLoader.ext?  Or would this behavior have to move into sculptor?

Todd

[Steffen Stundzig]

Hi todd,

TMF is much faster on model loading and parsing. So I think, a special
CachingModelLoad is not needed anymore.

regards

ootferrell schrieb:
> I've started migrating sculptor to TMF xText, when I have the time to work on
> it and I've made some progress, but I have a question.  oAw xText has an
> xTend file called
> org::openarchitectureware::xtext::registry::Modelloader.ext which delegates
> to CachingModelLoad.java.  ModelLoader.ext is referenced by sculptor's
> GenExtensions.ext.  Is there a TMF xText equivalent to ModelLoader.ext?  Or
> would this behavior have to move into sculptor?
>
> Todd

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fornax-developer mailing list
Fornax-developer@...
https://lists.sourceforge.net/lists/listinfo/fornax-developer

[Patrik Nordwall]

Hi Todd

It makes me very happy that you have started the TMF migration.
Can we add you to the Sculptor development team?

I think it is good if we can try to use the "standard" mechanisms in TMF Xtext and in case that doesn't work or if we need some special functionality we can add our own extensions.

The import mechanism is one area which was not good enough in oAW Xtext and therefore we added some of special stuff.

Another area which I expect a lot of changes in is linking. It was complicated in oAW Xtext and the code completion result was not always satisfactory.

/Patrik  

Steffen Stundzig wrote:

Hi todd,

TMF is much faster on model loading and parsing. So I think, a special
CachingModelLoad is not needed anymore.

regards

ootferrell schrieb:
> I've started migrating sculptor to TMF xText, when I have the time to work on
> it and I've made some progress, but I have a question.  oAw xText has an
> xTend file called
> org::openarchitectureware::xtext::registry::Modelloader.ext which delegates
> to CachingModelLoad.java.  ModelLoader.ext is referenced by sculptor's
> GenExtensions.ext.  Is there a TMF xText equivalent to ModelLoader.ext?  Or
> would this behavior have to move into sculptor?
>
> Todd

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fornax-developer mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/fornax-developer

[Steffen Stundzig]

Hi,

you could find some howtos for the migration on

http://wiki.eclipse.org/OAW_Working_Group/Migration_Guide_oAW_4.3.1_to_oAW_5.0

regards

Patrik Nordwall schrieb:

> Hi Todd
>
> It makes me very happy that you have started the TMF migration.
> Can we add you to the Sculptor development team?
>
> I think it is good if we can try to use the "standard" mechanisms in TMF
> Xtext and in case that doesn't work or if we need some special functionality
> we can add our own extensions.
>
> The import mechanism is one area which was not good enough in oAW Xtext and
> therefore we added some of special stuff.
>
> Another area which I expect a lot of changes in is linking. It was
> complicated in oAW Xtext and the code completion result was not always
> satisfactory.
>
> /Patrik  
>
>
>
>
> Steffen Stundzig wrote:
>> Hi todd,
>>
>> TMF is much faster on model loading and parsing. So I think, a special
>> CachingModelLoad is not needed anymore.
>>
>> regards
>>
>> ootferrell schrieb:
>>> I've started migrating sculptor to TMF xText, when I have the time to
>>> work on
>>> it and I've made some progress, but I have a question.  oAw xText has an
>>> xTend file called
>>> org::openarchitectureware::xtext::registry::Modelloader.ext which
>>> delegates
>>> to CachingModelLoad.java.  ModelLoader.ext is referenced by sculptor's
>>> GenExtensions.ext.  Is there a TMF xText equivalent to ModelLoader.ext?
>>> Or
>>> would this behavior have to move into sculptor?
>>>
>>> Todd
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Fornax-developer mailing list
>> Fornax-developer@...
>> https://lists.sourceforge.net/lists/listinfo/fornax-developer
>>
>>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fornax-developer mailing list
Fornax-developer@...
https://lists.sourceforge.net/lists/listinfo/fornax-developer

[Todd Ferrell]

Hi Patrik,
Yes, I would love to be part of the team, but I'm not exactly sure what all that entails, so feel free to contact me directly to discuss any details.

My current plan is to migrate the sculptor functionality as is, using as much standard TMF functionality as possible.  However, I'm sure there will be areas that a more experienced sculptor developer will be able to improve upon, after review.

I'll know more about model loading after the GUI migration, but it's interesting that CachingModelLoad.java in oAW 4 doesn't actually cache anything.  The name was left unchanged for backwards compatibility.  I'll probably use that code just to get it working, then start looking for a better approach.

Yes, the linking has changed considerably and I haven't "yet" seen a need to implement scopes for the business tier generation, but I haven't migrated the editor yet and I'll likely create some ScopeProviders for content assist.

Todd

Hi Todd

It makes me very happy that you have started the TMF migration.
Can we add you to the Sculptor development team?

I think it is good if we can try to use the "standard" mechanisms in TMF Xtext and in case that doesn't work or if we need some special functionality we can add our own extensions.

The import mechanism is one area which was not good enough in oAW Xtext and therefore we added some of special stuff.

Another area which I expect a lot of changes in is linking. It was complicated in oAW Xtext and the code completion result was not always satisfactory.

/Patrik  

Steffen Stundzig wrote:

Hi todd,

TMF is much faster on model loading and parsing. So I think, a special
CachingModelLoad is not needed anymore.

regards

ootferrell schrieb:
> I've started migrating sculptor to TMF xText, when I have the time to work on
> it and I've made some progress, but I have a question.  oAw xText has an
> xTend file called
> org::openarchitectureware::xtext::registry::Modelloader.ext which delegates
> to CachingModelLoad.java.  ModelLoader.ext is referenced by sculptor's
> GenExtensions.ext.  Is there a TMF xText equivalent to ModelLoader.ext?  Or
> would this behavior have to move into sculptor?
>
> Todd

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fornax-developer mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/fornax-developer

[Patrik Nordwall]

Welcome on board. The TMF migration is an important step forward and we will all help you.
I will contact you regarding the details.

/Patrik


Hi Patrik,
Yes, I would love to be part of the team, but I'm not exactly sure what all that entails, so feel free to contact me directly to discuss any details.

My current plan is to migrate the sculptor functionality as is, using as much standard TMF functionality as possible.  However, I'm sure there will be areas that a more experienced sculptor developer will be able to improve upon, after review.

I'll know more about model loading after the GUI migration, but it's interesting that CachingModelLoad.java in oAW 4 doesn't actually cache anything.  The name was left unchanged for backwards compatibility.  I'll probably use that code just to get it working, then start looking for a better approach.

Yes, the linking has changed considerably and I haven't "yet" seen a need to implement scopes for the business tier generation, but I haven't migrated the editor yet and I'll likely create some ScopeProviders for content assist.

Todd

Patrik Nordwall wrote:

Hi Todd

It makes me very happy that you have started the TMF migration.
Can we add you to the Sculptor development team?

I think it is good if we can try to use the "standard" mechanisms in TMF Xtext and in case that doesn't work or if we need some special functionality we can add our own extensions.

The import mechanism is one area which was not good enough in oAW Xtext and therefore we added some of special stuff.

Another area which I expect a lot of changes in is linking. It was complicated in oAW Xtext and the code completion result was not always satisfactory.

/Patrik  

Steffen Stundzig wrote:

Hi todd,

TMF is much faster on model loading and parsing. So I think, a special
CachingModelLoad is not needed anymore.

regards

ootferrell schrieb:
> I've started migrating sculptor to TMF xText, when I have the time to work on
> it and I've made some progress, but I have a question.  oAw xText has an
> xTend file called
> org::openarchitectureware::xtext::registry::Modelloader.ext which delegates
> to CachingModelLoad.java.  ModelLoader.ext is referenced by sculptor's
> GenExtensions.ext.  Is there a TMF xText equivalent to ModelLoader.ext?  Or
> would this behavior have to move into sculptor?
>
> Todd

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fornax-developer mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/fornax-developer