On Jul 2, 2010, at 11:10 AM, Lachlan Deck wrote:
> On 03/07/2010, at 1:00 AM, David Avendasora wrote:
>
>> No big harm. I just hate having red-circles-with-xes show up when I
>> update, and QA would kill me if I modified almost every class in
>> our core frameworks right now.
>
> Wouldn't it make sense, in that case, to have your own templates
> defined (even if just a copy of the default ones) and only update
> them as needed [or allowed] from the default ones?
I think that would be a good patch to file for some Wonder frameworks
like ERIndexing... it gets to be a bit of a chore having to revert the
auto-generated _entity files in those frameworks after each update.
>
>> On Jul 2, 2010, at 10:51 AM, Ramsey Gurley wrote:
>>
>>> That said, the clazz stuff is a pretty nice feature and it cannot
>>> be included without updating (breaking) existing entity
>>> templates. I was sorta hoping you guys would just LOVE the idea
>>> (^_^) Sadly, since I don't hear anyone shouting "Hooray!" I guess
>>> that makes it too radical of a change to include.
>>
>> You know, that's a part of Wonder that I have never even looked
>> into. Can you give me a quick rundown of the kinds of things it
>> gets you (which I'm sure I'll discover I've been doing the hard way
>> for years)?
There's a whole pantload of nifty methods on the Clazz objects. The
docs for EOEnterpriseObjectClazz covers it pretty well
There's also some mumbo jumbo about client-side something something
there too, but I don't think anyone actually uses that stuff anymore
(^_~)d
Ramsey
>>
>> Thanks
>>
>> Dave
>
> with regards,
> --
>
> Lachlan Deck
This archive was generated by hypermail 2.0.0 : Fri Jul 02 2010 - 15:37:13 UTC