2. No support for logical model vs physical model of project files
-- Eclipse 3.2 DOES have a logical model API, but we're not
currently using it in WOLips (and I haven't looked at how to yet).
I missed this for about 15 minutes. Then I realized my projects
should have their code in packages - and support files can live in
folders. Now I don't.
Well, one other thing it's potentially nice for is making .eomodeld
and .wo appears as bundles instead of folders in package explorer.
I /think/ this is possible with Eclipse's logical model API. It's
not a huge deal, but it tightens up the UI.
3. User Interface doesn't "feel OS Xish" -- This is leveled a lot,
but I'm REALLY curious to find out SPECIFICS of what people mean
by it. One of the most noticeable ones is that tabs don't look
like aqua tabs -- this is also on my list, but potentially harder
to change because Eclipse tabs can do more than aqua tabs. What
else is wonky?
The biggest complaint I've heard is that text selection
(specifically triple clicking) doesn't work as expected for a Mac
app. Though, personally, I could care less.
This is fixed in the Eclipse 3.3 stream, so this hopefully will cease
to be an issue in the next release.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
