Re: New Web Components failing to compile?
Re: New Web Components failing to compile?
- Subject: Re: New Web Components failing to compile?
- From: Chuck Hill <email@hidden>
- Date: Mon, 27 Mar 2006 17:00:43 -0800
Hi,
On Mar 24, 2006, at 10:30 PM, Lachlan Deck wrote:
On 24/03/2006, at 5:02 AM, Chuck Hill wrote:
On Mar 23, 2006, at 5:20 AM, Jerry W. Walker wrote:
The easiest way to add a component on Mac OS X using the standard
WO tools is:
* Open your project in Xcode
* Create your new component in WOBuilder
* Save the new component you've built in WOBuilder into your
project's directory
* WOBuilder will ask whether you want the component added to
the project, click Yes.
The component is added to the correct target in the correct
location and automatically appears in Xcode within the Web
Components group. No muss, no fuss, no worries about targets.
This, you feel is easier than
* Open your project in Eclipse.
* Right click, New -> WOComponent
Ah, how devious are the easier ways of Mac tools!
Hang on. That looks like a truncated list! Whistling indeed ;-)
Hey! This is evangelism / advertising! What did you expect? The
Truth? Facts just twist the truth around.
Or is that whistling in scheme. It's no wonder (excuse the pun)
you're listed as the WOLips 'chief evangelist'. Ah, an ulterior
motive. ;-)
I had nothing to do with that. They just appointed me for some
reason... :-P
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.
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.
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.
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...
No 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.
Initial setup... (done once only in Eclipse. Not needed in Xcode)...
* Open Eclipse
* (Menu) Window > Customise Perspective
* Select 'New' from Submenus
* Tick WOLips WO5.1. WO5.2 in Shortcut categories
Window -> Open Perspective -> select WOLips
Per project...
* Open project in Eclipse
* Right click (or ctl-click), New -> WOComponent
* Give it a name and a package.
I don't see any obvious way to get Eclipse to open the component in
WebObjects Builder... perhaps why you stopped short on your list ;-)
Naw, 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.
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.
Anyway, so far I've seen a singular benefit (that of easier package
creation/organisation) but that doesn't seem compelling enough
given the lack of other built-in features for WebObjects that come
for free with Xcode. But naturally I've not given it much time yet...
You did not get into it very far then, 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.
- 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.
Your tongue in cheek,
Chuck
Always amusing...
And hopefully educational today.
Chuck
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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