Re: [Wonder-disc] ERXClassDescription not returning an inverse key

[Marc B. <ma...@fo...>]

>         One future direction I would like to see Wonder move is to by 
> default
> not automatically set everything up. This way one could link in Wonder
> and by default nothing would happen, then adding in properties in your
> properties file would start to enable features.
>
> Regards,
>         Max

I would endorse this idea also Max.
The hardest part when you are first starting is working out all the 
'invisible side effects'.
Properties like:
er.extensions.ERXNavigationManager.NavigationMenuFileName = 
navmenu.plist

but extended to things like (excuse the naming, just examples):
er.erd2w.ERD2WUseNewRuleEngine = true
er.extensions.ERXUseERXGenericRecords = true

Of course this would mean additional refactoring to ensure that the 
frameworks are encapsulated enough to allow arbitrary combinations of 
feature enabling/disabling.

For example, it's hard to see how some aspects of Anjo's model based 
validation would work without ERXGenericRecords.

But a great principle - could easily get started by having a "master 
switch" preference
er.extensions.ERXUseERExtensions = true
This would enable people to link in the frameworks without fearing 
collapse of their app - then again why link in the frameworks if this 
is false?

So I guess what I'm saying is that some level of componentisation would 
be needed for these property switches to make sense - and for that a 
dependency analysis is needed.

Volunteers?