On Oct 2, 2009, at 1:14 PM, Andrew R. Kinnie wrote:
> I like the idea, myself. Though I pretty much hate all things
> Eclipse, except for the bit about it being the only sensible way to
> develop in WO. The more yeoman-like work you feel like doing to
> make it more mac-like the better, as far as I'm concerned.
>
> My $.02
>
> Andrew
>
There are things about the eclipse interface that just drive me nuts.
On the other hand, I could be stressed about all those things and get
nothing done. So, it is just not worth it to worry about how to make
an eclipse plug-in do something un-eclipse-like.
But that leads me to strange places. For example, I have a command-
line version of EOModeler. I got to a point where I was looking at
changing a few things about a few attributes in a lot of entites. It
was easier to write something with which I could say "take all
attributes like this in entities like this and set some key to some
value." It turned out to be not difficult. EOModeler is just, after
all, a plist editor on steroids.
Things like multiple object selection (shift-click on a Mac) seem to
just be completely missing from eclipse and I do not know what to do
about that. And for instance, double-click on something in a
WOComponent and the selection that results is completely random and
often obviously wrong. Not sure what to do about that either. But then
again, if I tear my hair out about this, eclipse does not care and I
have less hair.
And remember Mac apps sometimes do not get Inspector windows right.
The Inspector window in IB is particularly bad, if you want to see
some weird crap going on. Is it an inspector? When the focus changes,
what happens to it? When does it close or not close? That kind of stuff.
Anyway. Eclipse sucks (at times), but waiting for Apple to fix bugs in
a java IDE would be far, far worse.
- ray
>
> On Oct 2, 2009, at 4:09 PM, Mike Schrag wrote:
>
>> It would work like inspectors on normal Mac apps -- it would just
>> be "Inspector Window" ... you wouldn't close and reopen for each
>> one, it would change with selection (like old EOModeler).
>>
>> Technically you can tear off the current view, but the layout is
>> undesirable for an inspector panel. This kind of goes back to the
>> main question of whether we're an Eclipse app or a Mac app. If
>> we're a Mac app, I think there's no question that this should be a
>> separator inspector window -- You really don't see embedded
>> inspector views very often on the Mac.
>>
>> I'm undecided on it at the moment. Just something I'm tossing around.
>>
>> ms
>>
>> On Oct 2, 2009, at 3:34 PM, David Avendasora wrote:
>>
>>> I often step through attributes and relationships to check/set
>>> things, I don't want to have to open the inspector and then close
>>> it again when I'm done only to reopen it on the next attribute.
>>>
>>> Maybe making it so it is it's own pane like the console might be
>>> better so those that want it separate and not taking up space in
>>> the main window could move it or close it.
>>>
>>> Dave
>>>
>>> On Oct 2, 2009, at 2:19 PM, Mike Schrag wrote:
>>>
>>>> http://skitch.com/mikeschrag/nbwcr/eclipse
>>>>
>>>> On Oct 2, 2009, at 2:12 PM, Mike Schrag wrote:
>>>>
>>>>> I've been _contemplating_ pulling the properties panel out of
>>>>> Entity Modeler and moving to an Inspector-style approach ...
>>>>> This is VERY un-eclipse, though. How do people feel about this?
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Sat Oct 03 2009 - 13:34:23 EDT