On 20.04.2006, at 17:09 Uhr, Pierre Frisch wrote:
> and Eclipse 3.1 crashes on me at least once a day.
Only once? Cool.
I have issues with:
- Often Eclipse doesn't set the focus for the correct "tab" in the
window. This happens every time I use the included shortcut to create
a JavaDoc comment. Then after a while copy & paste will not work
anymore.
- Sometimes when I use quickfix for a but (like "import package
xyz"), the Java editor part of the component editor doesn't update
the display. I have to close the file and re-open it to see the changes.
- Sometimes Eclipse leaves "trash" behind when quitting. Running
instances of a WO app and so on.
- If the current user have not WRITE permissions to the Eclipse
application folder, I can't create new projects ... what the **** is
going on with that?
- In the html part of the component editor the shortcuts are "a bit
odd" - I don't like using harder words but ... *argl* I haven't found
a way to configure the keys for this editor. It may be that there is
a way, but I haven't found it.
- If you don't set your Eclipse default Editor encoding to UTF-8,
Strings in Java classes have broken umlauts WHEN RUNNING THE APP! I
even haven't opened the file - just checked it out from CVS, started,
garbage is writting to the db.
- Sometimes Eclipse doesn't want to come to the front when switching
via Command-Tab or clicking on special places in the window. Try this
when you do D2W development and have to switch back to Eclipse for
every change because this damned thing doesn't see the changed rule
file ... :-( Annoying!
- "The contents of XY are not in sync with the file system" - in CVS/
Team mode ... hell, just reload that stuff and shut up.
- "Rebuilding workspace" when opening Eclipse. I have a Powerbook G4
1.25GHz - do I have to tell more?
All these things are Eclipse problems - not WOLips I think (not sure
about the Component Editor stuff, but a friend has similar problems
with a WO free box and a clean Eclipse 3.1.x).
Add to this all a couple of WOLips problems, annoyances,
glitches, ... (there aren't a lot, but you have to know how to get
everything working) WOLips is in active development. Great. I love it
and I'm really happy about that.
Don't get me wrong: I use Eclipse with WOLips currently about 8 to 12
hours a day but I would NEVER NEVER EVER recommend it to a WebObjects
beginner even if he knows Java/Eclipse. My co-worker just started
working with WebObject/Eclipse and it took us a day to get the
environment up and running for some simple apps from the CVS. In the
end we copied over my "halfway running Eclipse installation" to his
machine. And now he'll be lost if he can't ask me on all the small
undocumented problems and "you should know" things to get WO and
Eclipse play together.
So: for the WOLips/WOProject team: great work! I appreciate it and I
use it. For the Ecllipse team: bullshit. The thing is bloated, slow,
and unstable. It has excellent features, and it is a great IDE - but
often it doesn't work at all.
For the combination: Hey, being on the edge might be cool, but I
don't have the time for it. I hope 3.2 will be more stable and that
we soon have a working and stable WOLips release for all the people
which have to get their work done and don't have the time to test new
WOLips/Eclipse combinations every week.
In the end: I wouldn't start my next project on Eclipse/WOLips. I
would use Xcode, hate it for its lack of Java support and the stupid
"code senseless" and for the project after the next I would use
Eclipse again. And so on ...
cug - two days to holiday ...
This archive was generated by hypermail 2.0.0 : Thu Apr 20 2006 - 12:37:51 EDT