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: Sat, 25 Mar 2006 17:30:27 +1100
Hi there,
On 24/03/2006, at 5:02 AM, Chuck Hill wrote:
On Mar 23, 2006, at 5:20 AM, Jerry W. Walker wrote:
Hi, Jeffrey,
While he's walking away whistling, Chuck will soon have you
believing that the only way to develop a WO project is under
Windows in Eclipse.
Sir! I take offence! I demand satisfaction! I challenge you to a
duel of IDEs. The OS X platform, dawn, tomorrow.
<grin>
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 ;-)
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. ;-)
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)
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).
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).
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...
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
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 ;-)
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?
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...
Your tongue in cheek,
Chuck
Always amusing...
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