Re: Separating mac modeler code

From: Michael Gentry (blacknex..mail.com)
Date: Tue Jan 08 2008 - 09:51:31 EST

  • Next message: Robert Burrell Donkin: "[NOTICE] Old Incubator Releases Archived"

    I suppose I should've mentioned MacOSXMain. Sorry about that. I have
    a separate Eclipse cayenne-modeler-mac project just to run that part
    of the code. I don't think the changes hurt the Windows/Linux
    versions.

    I went for the quick, easy, practical fix, not necessarily the
    "correct" fix. It just seemed the easiest way to do it at the time.
    I didn't want those menu items to appear there on the Mac, so I made
    them conditional.

    Thanks,

    /dev/mrg

    On Jan 8, 2008 9:35 AM, Andrus Adamchik <andru..bjectstyle.org> wrote:
    >
    > On Jan 8, 2008, at 4:27 PM, Michael Gentry wrote:
    >
    > > It is
    > > still usable and runnable inside Eclipse (preferences, about, and quit
    > > all work, they are just under the application menu).
    >
    >
    > My bad - I started the app from generic Main class. Now running from
    > MacOSXMain, I see those menu items.
    >
    > > I'm not sure moving
    > > the code out will be more beneficial -- you'd either have to entirely
    > > duplicate the menu creation code or go remove things afterwards that
    > > you don't want. This would add more clutter than just conditionally
    > > not adding the menu items in the first place.
    >
    > Splitting menu creation into a bunch of separate methods in a
    > superclass should allow to override some of them in the subclass. This
    > still seems like the right thing to do, but considering the above, it
    > becomes very low priority on my list...
    >
    > Thanks,
    > Andrus
    >
    >
    >
    >

    This archive was generated by hypermail 2.0.0 : Tue Jan 08 2008 - 09:52:03 EST