Hello,

> In 1.3 (trunk) we have two metamodels: sculptormetamodel and
> sculptorguimetamodel.

I had some time to look at the model which is great in its own right.

My first impression is, that it is very close to the WebFlow terminology. 
So in MDA speak, maybe they classify as PSMs.

What I have in mind is a PIM for general description of GUIs which I
would transform to a model suited for rich client generation.

Such a model would of course be easily mappable to one which uses web
technology, but it would keep it free of implementations details (what is a 
Flow,
BTW? Is it a View or an Action?).

On the other hand, maybe I'm just mis-interpreting the model and it
is meant to be platform independent. Then I would recommend to rename the 
'Flows' to something which makes sense for people who don't use WebFlow.

Ideally, there would be sub-cartridges for WebFlow, Eclipse Rich Client,
Javascript single page applications etc. but I can currently only work 
on the RCP part.

For me, this means that you have to decide whether I should copy paste
the generator to create a gui metamodel which is suitable for a rich client
(because I won't have the time to transform that to one for web UIs)
and we could later merge your web and my rich client gui generator
or whether we can somehow coordinate the work.

> We could create a separate wiki page, if you think it would contribute to
> our joint effort, but we don't have time with too much documentation
> overhead of the development.

I think a central place to document event small snippets or brain dumps
would be good.


Many thanks


Kambiz


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer

Reply via email to