Re: New Web Components failing to compile?
Re: New Web Components failing to compile?
- Subject: Re: New Web Components failing to compile?
- From: Lachlan Deck <email@hidden>
- Date: Wed, 29 Mar 2006 02:07:06 +1100
Hi there,
On 28/03/2006, at 12:00 PM, Chuck Hill wrote:
Hey! This is evangelism / advertising! What did you expect? The
Truth?
It's better than the alternative...
Anyway, I was personally interested in seeing how Eclipse compares as
a development tool. i.e., I'm all for improvements if they make life
easier.
Okay, I'll bite and check this out. No use living in ignorance as
they say.
1) Installation...
Eclipse + WOLips plugins as per <http://www.objectstyle.org/
confluence/display/WOL/Installing+WOLips>
Relatively painless (but not as painless as installing Xcode
+WebObjects but that's a given)
I was just responding to Jerry's overly long and circuitous way of
adding a component in Xcode. It is actually just as easy in Xcode,
I was just pulling Jerry's beard.
It was certainly an interesting approach. For mine, it's not worth
hiding the targets from the newbie. They need to learn at some stage
what they correspond to in the built product.
2) Okay, Right clicking doesn't include New->WOComponent. Okay so
we need to Window->Customise Perspective and tick the WOLips
options for the new submenu. Had to search the help to find this
option. Again Xcode's New options include every file type
installed and categorised nicely as an option by default
(including my own without creating plugins).
That is not what you are supposed to do. You should just switch to
the WLips perspective (Window -> Open Perspective) rather than
editing the Java one. Eclipse perspectives (e.g. WOLips, Debug,
Java) give you multiple views into the same work space.
Righteo... giving that a shot. Just didn't find it intuitive at first
that's all and yes I didn't read enough.
But there's no problem with customisability. They're just
different ways of working. Okay, so now that it's got the New-
>WOComponent (etc) options we move on. Okay bonus points for
automatically creating the package paths and inserting it into the
java file. (I'm sure I could customise Xcode to do the same but
granted it's not a java ide).
If you do figure out how to customize Xcode, please do let us know.
Seen the scripts menu?
3) Cannot see any way to get Eclipse to utilise WebObjects Builder
as an external tool. Double clicking on a MyComponent.wo simply
expands the group...
Nor do I see a convenient list of available re-usable components...
I suspect that is partly because you are looking in a view that
these are not part of. In the WOLips view there is a Related
Window. Clicking on the .wod file will open WOBuilder. Eclipse,
like most non-Mac tools won't treat directories as packages.
Ahh okay, I got it to open the *.wo (but not via a double click).
Unfortunately the option to add keys/actions are disabled.
you just skipped the tutorials,
http://www.objectstyle.org/confluence/display/WOL/Tutorials
Like the second one:
http://www.objectstyle.org/confluence/display/WOL/Create+a+new+WO
+Application
Reading some docos really does help.
Yep, got me :-) Whoever reads the manual first up?
I like Xcode groups but can't see a way of organising like files/
folders together in Eclipse and so it looks like given a project
of reasonable size the organisation could get out of hand. Where
do you create groups for other resources?
I don't. But the Related window allows you to quickly navigate
between the various bits. And the internal WOComponentEditor
http://www.objectstyle.org/confluence/display/WOL/Edit+a+WO
+Component opens all the pieces in a nice tabbed interface with
code completion, validation, and other nice things missing from
WOBuilder.
What are the 'other nice things'? Okay code completion's nice for
tags, but the absence of drag/drop elements/bindings is a bummer.
I suggest giving it another hour or two. Certainly what you have
seen so far is no justification for switching. Now, what is
justification for switching?
- as you type code analysis. In Eclipse, the compile is part of the
IDE. Unlike Xcode where the build is a process contracted out to
jam etc., building happens as you type in Eclipse. The major
benefit of this for me is that I _never_ have to build to see if I
have a syntax/spelling error. My cursor rarely leaves the line the
error is on. Eliminating the build cycle from finding and fixing
these errors is a huge productivity gain for me. This, alone,
makes Eclipse worthwhile (in my evangelical opinion of course). A
less visible result of this is that the code is in memory as a
model of the source. This allows the easy development of tools
that would be very difficult in Xcode.
Yes, I noticed this at first and certainly it is nice. I've imported
a project into Eclipse - however I'm getting a compile error (missing
package) that wasn't present in Xcode. I'm guessing it's to do with
the -extdirs compiler flag missing.
How do I add the equivalent?
-extdirs /Library/WebObjects/Extensions:/Library/Java/Extensions:/
System/Library/Java/Extensions:/System/Library/Frameworks/
JavaVM.framework/Home/lib/ext
- no build cycle period. Unless you opt to use the Ant builder,
your project is built in the background as you save each file.
There is never any build cycle, no Build and Run and wait for it to
be ready. You just Run and it does. This saves a lot of time.
- real, effective, intelligent code completion
- an excellent Java debugger. No more needs to be said.
- command-click navigation in source. Command click on a variable,
method, or class to navigate directly to the file and place where
it is declared
Those are my top reasons. There are many more.
Certainly those reasons are compelling. The reason(s) why, so far,
it's not 'working' for me is the clunky interface, lack of intuition,
bugs (to be expected), and non-mac-like keyboard shortcuts (which I'd
need to spend time fixing so that it behaves as most Mac apps do as
I'm used to).
Thanks for the tips...
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden