• 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: Anything new on the Horizon of Webobjects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Anything new on the Horizon of Webobjects


  • Subject: Re: Anything new on the Horizon of Webobjects
  • From: Marek Wawrzyczny <email@hidden>
  • Date: Thu, 30 Oct 2003 15:31:01 +1100

Just my vote on this.

All I can say is heaven forbid that Apple bound WO or EOF to Cocoa.

Yes Cocoa is faster, yes Cocoa is prettier but in the end Cocoa is Apple and in the ideal world 90%+ of computers are Windows (whether we don't like it or don't like it). At the end of the day it is the clients that will dictate what environment the program-to-be will operate in. Try to factor in the cost of upgrading the organizations entire computer base into your coding estimates... you will not get too far.

Fine, let Apple tightly integrate Cocoa into EOF but not at the expanse of multi-platform deployment. This is one of WO's strengths at the moment.


On Thursday, Oct 30, 2003, at 10:33 Australia/Sydney, Ricardo Strausz wrote:


<...>

But was there anything else to expect from such a secretive organization as Apple? This lack of communication could be construed in three ways:

(A) Snobbism vis-a-vis their very own user base. (B) Don't care one way or another. (C) Don't have a clue in the first place.

In any case, here is my very own playful "Road Map" fantasy :)

(1) Migrate out of the Foundation legacy.

Most of what can be found in com.webobjects.foundation serves no purpose whatsoever aside from ego inflation and intellectual masturbation. Clumsily pretending to support ancient legacy projects is not the way to go forward.

Better: they should use com.apple.cocoa.foundation.* insteed. It is a problem to have so many foundations...

<...>


(3) Migrate out of the AppKit legacy

It's time for WebObjects supporting cast of midly amusing clowns (PB, EOModeler, WOBuilder & Co) to move out from the AppKit legacy. Move to Swing or SWT. Better yet, provide integration with mainstream third parties (e.g Eclipse and such).

Had you build a Cocoa app?? come on!! Swing is a SLOW tourtle bisides Cocoa's AppKit.
And what about the VERY usefull makeKeyAndOrderFront method (which is missing in Swing). There's no way Swing can compit with Cocoa...



(4) Reuse

Apple is a small company. WebObjects is a minor product. Its development team fits in the cupboard of a small minivan. They cannot do everything.

For instance, synchronization across multiple instance of WOApps is not properly handled. Leveraging Java Message Service or other communication toolkits (e.g. Javagroups) could help.

No comments. I do Cocoa/EOF most of the time.

<...>


Marek Wawrzyczny

software engineer
-------------------------->
ish group pty ltd
7 Darghan St Glebe 2037 Australia
phone +61 2 9660 1400   fax +61 2 9660 7400
http www.ish.com.au | email email@hidden
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Anything new on the Horizon of Webobjects
      • From: Denis Stanton <email@hidden>
References: 
 >Re: Anything new on the Horizon of Webobjects (From: Ricardo Strausz <email@hidden>)

  • Prev by Date: WO 5.2.2 - Getting an app to launch - java.lang.NoClassDefFoundError
  • Next by Date: Re: Java date questions
  • Previous by thread: Re: Anything new on the Horizon of Webobjects
  • Next by thread: Re: Anything new on the Horizon of Webobjects
  • Index(es):
    • Date
    • Thread