Re: Normalizing EOModel plists and avoiding CVS merge conflicts

From: Mike Schrag (mschra..dimension.com)
Date: Mon Jul 17 2006 - 14:41:29 EDT

  • Next message: Mike Schrag: "Re: EOModel Editor: Issue loading the fetchSpec: Unknown class NSNumber"

    You're referring to how plist serialization in WO will sometimes do
    ( value1, value2, value3 ) instead of:
    (
            value1,
            value2,
            value3
    )
    , right? It looks like PropertyListSerialization in Cayenne always
    does individual lines, so we get that for free ...

    ms

    On Jul 17, 2006, at 2:34 PM, Anjo Krank wrote:

    >
    > Am 17.07.2006 um 19:20 schrieb Chuck Hill:
    >
    >>>> I just had a vision: an EOModeler that writes plists in a
    >>>> deterministic fashion. Wow. Now THAT would be cool! :-P
    >>>
    >>> Imagine!? I just switched back to CVS so I'm looking forward to
    >>> testing this.
    >>
    >> Ugh. This must be my most hated bug in EOModeler.
    >
    > The new RuleModeler in ProjectWonder saves all D2W rules (sorted by
    > prio) each on its own line. A similar approach would be useful for
    > EOM, wouldn't it?
    >
    > Cheers, Anjo

    This archive was generated by hypermail 2.0.0 : Mon Jul 17 2006 - 14:41:34 EDT