OK, answering my question (sort of) and posting the solution so I
don't violate "Mike's thread ribbon rules" ;-) ....... it seems
EntityModeler only merges your custom prototypes IF they are named
EOPrototypes.
So in summary, if you want a few custom prototypes in addition to
Wonder's prototypes, just create a new proto framework called whatever
you like and inside it a new EOModel named whatever you want and
create a prototypes entity named "EOPrototypes". After you include
that framework into your buildpath, your custom prototype attributes
will be merged with the erprototypes in the ptototype drop-down in
entity modeler.
make sure to use a prefix such as "wk" or "my" or sth like that so
your proto attribute names are namespaced and so they don't clash with
erprototypes attribute names.
Mike, if there is other conventions for custom proto entity names so
that they get recognized by EntityModeler, please let us know, and I
will post the info on the wiki.
-Kieran
On Jun 19, 2009, at 4:52 PM, Kieran Kelleher wrote:
> Mikes blog post from March 2009 says
>
> "Entity Modeler now supports the new custom prototypes naming
> convention from Wonder."
>
> So I have a custom eomodel with a custom proto entity that I want to
> use alongside ERPrototypes. I am using orefixed proto attribute
> names too so I don't clash with erprototype attr. names.
>
>
> I have added these properties to the Properties file that has the
> EOModel I am editing ..... Am I wrong in expecting EntityModeler to
> look at this to add my custom protos to the proto dropdown menu?
>
> er.extensions.ERXModelGroup.prototypeModelNames = erprototypes,
> WKCompatiblePrototypes
> WKCompatiblePrototypes.EOPrototypesEntity = MySQLCompatiblePrototypes
This archive was generated by hypermail 2.0.0 : Fri Jun 19 2009 - 17:15:40 EDT