Thanks for your ideas of improvement.

The intention of separating some customization to
sculptor-generator.properties is that those properties are of global
character and typically a technical design choice. They are normally not
changed very often. I don't want to pollute model.btdesign with that kind of
things, if I don't see a benefit in defining the property on a specific
element. In best of worlds we would have even more DSLs with different
responsibilities, linked together. E.g. database settings.

Your example with gap and scaffold on different levels is interesting, but
I'm not sure if it is necessary to be able to define it on the Module level.
It can also be confusing. 

I like our previous conclusions about hint, but we should not use it for
everything. It's purpose should be for customization of things that we have
not been able to think of in advance (or have decided to only support
through customization).

Let us implement the hint.
http://fornax.itemis.de/jira/browse/CSC-385

/Patrik


PaloT wrote:
> 
> Hello,
> aren't generator properties just Application level hints. What about:
> Application myApp hint="GenerateGapClass" {...
> 
> And than of course:
> Entity SomeEntity hint="NoGenerateGapClass" {...
> 
> Advantage should be to have "GenerateGapClass" for example on Module.
> 
> What about "scaffold"? Put in on Application and all Entities became
> scaffolded.
> 
> Isn't this same mechanism?
> 
> Should we build this extension functions some generic way that for
> example when I define GenerateGapClass on Application and than I put
> "NoGenerateGapClass" on Module and ask in entity template inside this
> module hasHint("GenerateGapClass") it will return false?
> 
> Is it too far?
> 
> Pavel
> 

-- 
View this message in context: 
http://www.nabble.com/New-concept-tp24252062s17564p24277957.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.


------------------------------------------------------------------------------
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer

Reply via email to