Well, it's less that it's hard to match old EOModeler (which is
probably not too hard -- it's got to be a pretty small set of rules
that it Apple's plist writer uses) and more that it's specifically a
feature that the new one writes the way it does. Entity Modeler
writes everything in a consistent sort order so that successive
writes give you clean diffs as opposed to old EOModeler which doesn't
define the sort order for lists or maps and ends up shuffling the
order of the plist all over the place (basically making it a huge
pain in the butt to diff against). I can see how if a company has a
mix of people using EOModeler and Entity Modeler on the same models
that it might be busy looking diffs. However, EOModeler is going to
shuffle your data and touch every file, anyway, so I'm not sure we're
much worse in that respect?
ms
On Jul 25, 2006, at 2:48 PM, Sébastien Sahuc wrote:
> I noticed that as well. Actually rewriting all model files is fine
> as long as the svn diff doesn't scream verbosely. What happens here
> is the difference in final file formatting between the legacy
> EOModeler and the new exciting model editor. Unfortunately from
> what I read in this list, there is no way to play with the final
> formatting to match 100% with the original EOModeler, is that
> correct ?
>
> Thanks,
>
> Sebastien
>
> On Jul 25, 2006, at 11:23 AM, Watkins, Garry wrote:
>
>> Do you re-write all of the entities when you save? If you do, I
>> would
>> like to put in a request that it only write files (entities, fetch
>> specs) after they have been changed. That way subversion doesn't
>> tell me
>> that all 200+ files of my model have changed. One more thing, it is
>> writing an initial blank line, which causes subversion to pick up
>> differences.
>>
>>
>> Thanks
>> Garry
>>
>>
>> -----Original Message-----
>> From: Mike Schrag [mailto:mschra..dimension.com]
>> Sent: Tuesday, July 25, 2006 1:28 PM
>> To: woproject-de..bjectstyle.org
>> Subject: Re: EOModeler Attributes
>>
>> They should all be editable, but via the attribute "inspector panel"
>> right now (if you're in the Entity Modeler perspective, you will have
>> the Properties view in the lower right. If you select an
>> attribute, the
>> editor will appear there) ... The list of columns in the table is not
>> configurable right now and probably won't be before WWDC unless
>> someone
>> else wants to take this on (it's a bit of a tricky problem to do it
>> live). I've intentionally selected the columns in the attribute
>> view at
>> the moment to encourage the use of prototypes, which is why these
>> other
>> fields don't appear as columns by default.
>>
>> ms
>>
>> On Jul 25, 2006, at 1:14 PM, Jake Fisher wrote:
>>
>>> Mike,
>>>
>>> Can you add the following as either columns or editable attributes
>>> in the new integrated EOModeler?. We make use of them fairly
>>> often in
>>> our models.
>>>
>>> Missing EOAttribute attributes:
>>>
>>> value Class = 'valueClassName'
>>> precision = 'precision'
>>> scale = 'scale'
>>> as an example:
>>> {
>>> allowsNull = Y;
>>> columnName = ID_AMOUNT;
>>> externalType = DECIMAL;
>>> name = amount;
>>> precision = 7;
>>> scale = 2;
>>> valueClassName = NSDecimalNumber;
>>> }
>>>
>>>
>>> Thanks,
>>> ~jake
>>
>>
>>
>>
>>
>> Confidential & Privileged
>>
>> Unless otherwise indicated or obvious from its nature, the
>> information contained in this communication is attorney-client
>> privileged and confidential information/work product. This
>> communication is intended for the use of the individual or entity
>> named above. If the reader of this communication is not the
>> intended recipient, you are hereby notified that any
>> dissemination, distribution or copying of this communication is
>> strictly prohibited. If you have received this communication in
>> error or are not sure whether it is privileged, please immediately
>> notify us by return e-mail and destroy any copies--electronic,
>> paper or otherwise--which you may have of this communication.
>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Tue Jul 25 2006 - 14:56:48 EDT