• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Eclipse / wolips / X-Code –– Baffled
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Eclipse / wolips / X-Code –– Baffled


  • Subject: Re: Eclipse / wolips / X-Code –– Baffled
  • From: Chuck Hill <email@hidden>
  • Date: Mon, 16 Oct 2006 13:49:24 -0700

Hi Andrew,


On Oct 16, 2006, at 1:38 PM, email@hidden wrote:

I'm reading between the lines on this mailing list over and over amongst the whispers and murmours and am still not quite sure what is going to happen with the WO toolset. I can appreciate that EOM and WOB are going to get the axe, although there is no clear indication of *when* they are going to go. Is it going to happen at 5.3.?/5.4/5.5/...?

I have no idea when this will happen.


Yesterday Chuck said in a post...

Apple is deprecating their Xcode and tool support in favor of WOLips.

My interpretation, not their words.


...but in one of Apple's open emails to this list they say...

...Making WO work well with ANT and the most popular IDEs, including Xcode and Eclipse

Which mentions X-Code and Eclipse. Is it the case that they will be advocating wolips's ANT tasks as the only viable build process for WO?

Yes, that is my interpretation of that statement. They may provide their own tasks, but that would seem to be a waste of effort for them.



What about SSD or do we have to arrange that ourselves open- source style?

I don't use it, but I was under the impression that WOProject (the Ant part of WOLips) did this already.



Is it the intention of Apple that eclipse will be the only viable platform for WO development?

I was not aware that Xcode ever was a viable platform for WO development. Grin.


I expect that Xcode will always be able to build WO apps. But once the other tools go away, you would need to use Eclipse and WOLips to edit models, components, etc. Well, that or emacs.


and want to encourage variety within the community...We will work to assist the community...been working with several open source projects. This will become public soon.

It's a really big ask to expect somebody to stop work for a week in order to fly all the way from New Zealand to conference in the USA every single year just on the off chance there is any meaningful/ new WO information imparted. I feel that claiming to be "assisting the community" and then keeping the bulk of the community (including some like me who do contribute articles and framework) in the dark on timing and logistics of these obviously quite massive changes is an extraordinary contradiction.

You are not the only one saying that. However, this mentality runs very deep at Apple.


Chuck

--

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


  • Follow-Ups:
    • Re: Eclipse / wolips / X-Code –– Baffled
      • From: shaun <email@hidden>
    • Re: Eclipse / wolips / X-Code –– Baffled user of D2WS
      • From: Gordon Maynard <email@hidden>
References: 
 >Eclipse / wolips / X-Code –– Baffled (From: email@hidden)

  • Prev by Date: Eclipse / wolips / X-Code –– Baffled
  • Next by Date: Re: Eclipse / wolips / X-Code –– Baffled user of D2WS
  • Previous by thread: Eclipse / wolips / X-Code –– Baffled
  • Next by thread: Re: Eclipse / wolips / X-Code –– Baffled user of D2WS
  • Index(es):
    • Date
    • Thread