• 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: Apple's Support of WebObjects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple's Support of WebObjects


  • Subject: Re: Apple's Support of WebObjects
  • From: Kieran Kelleher <email@hidden>
  • Date: Fri, 4 May 2007 16:38:59 -0400


On May 4, 2007, at 3:18 PM, Don Lindsay wrote:

Hello;

I know that Apple had decided last year to deprecate/stop development of Web Objects.

Has there been any change in the status of Web Objects support?
When will it quit being distributed as part of XCode?
Has/or will Apple give the source code of WebObjects to the community so it can continue to be developed?
If so, I would like to volunteer to assist with development of WebObjects.


The other responders have replied to these points already.

I like the apple tools. I know WOLips and project WOnder exist for eclipse but I do not like these tools much.

I used Apple Tools for a few years and switched to WOLips/Eclipse at the start of this year. Recently I had to work on an old XCode project and after 2 days, I was suicidal and I *had* to convert it to WOLips .... it was just too slow and painful to work in XCode.... and the pain is worse the bigger the project is. If you used both sets of tools for 3 months, you would not say that, especially when productivity and profit is at stake. The *majority* of Apple WO developers use Eclipse/WOLips, not XCode .... and that's public knowledge if you listen to certain podcasts.

WOnder is invaluable ..... it adds an absolute ton of additional frameworks that save you immense amounts of programming, it fixes many bugs and auomatically patches those replacement classes in at application launch time plus it provides solutions to many of the common shortcomings of the standard WO frameworks.... and these are often enabled by just simply setting up a few properties in the Properties file.

I have several products that I wish to use WebObjects for, but it is difficult to proceed with these projects using WebObject when it's future is in doubt.

I really like WebObjects, it's design makes it the most powerful development package,

It is.... :-)

as well as the Apple design tools allow for fast application design.

They don't........ :-p

The learning curve is steep, but i you know java well, have a basic knowledge of the basic design patterns (Head First Design Patterns), study the Practical WebObjects book, etc. you will understand what is going on in the WO frameworks in a short time

Have fun and don't overlook Eclipse/WOLips :-)


Don
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com


This email sent to email@hidden

_______________________________________________ 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: Apple's Support of WebObjects
      • From: Miguel Arroz <email@hidden>
    • Re: Apple's Support of WebObjects
      • From: Mike Schrag <email@hidden>
References: 
 >Apple's Support of WebObjects (From: Don Lindsay <email@hidden>)

  • Prev by Date: Re: Apple's Support of WebObjects
  • Next by Date: Re: Apple's Support of WebObjects
  • Previous by thread: Re: Apple's Support of WebObjects
  • Next by thread: Re: Apple's Support of WebObjects
  • Index(es):
    • Date
    • Thread