From: Kieran K. <kie...@ma...> - 2007-02-26 12:58:28
|
I think it is going to be commonplace for individuals to need/have their own supplementary prototypes, especially given the different domain requirements of projects, and also for project wonder adopters who had a custom prototypes before they adopted Wonder. It might be a good idea to architect EntityModeler database configs to allow two prototypes, "primary" and "auxiliary/user". Then in Properties we could specify sth like this: er.extensions.ERXModelGroup.prototypeModelName=erprototypes er.extensions.ERXModelGroup.auxiliaryPrototypeModelName=wkprototypes .... and the ERModelGroup loading order code could be changed to insert both of these at the beginning of the array of models. Regards, Kieran On Feb 26, 2007, at 3:47 AM, Anjo Krank wrote: > I think this would clutter the prototype tables too much. > > I'm not sure about a good strategy to add your own prototypes apart > from putting them into ERP? Can you add another model in there with > your own? Any ideas? > > Cheers, Anjo > > Am 23.02.2007 um 21:34 schrieb Lachlan Deck: > >> 2 places is definitely common usage in my case (for usual online >> sales). > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |