It's not just about the widgets. AWT and Swing need you to handle event dispatch, layout, accessibility, and a few other things I'm probably forgetting. I don't know how much of that you would pick up from the Java sources in OpenJDK, and how much you'd have to do yourself.
The other thing that makes this hard is that Cocoa has a "main thread" that works pretty much like AWT-Event-Dispatch -- anything that touches the UI has to be on this thread -- so Mac JNI calls for a lot of careful coordination and use of performSelectorOnMainThread:. On Oct 26, 5:15 pm, Fabrizio Giudici <[email protected]> wrote: > On 10/26/2010 09:42 PM, Chris Adamson wrote: > > > Scott Kovatch, who worked on SWT for OS X at Apple, had this to say to > > say about the scope of such a project (http://twitter.com/#!/skovatch/ > > status/28570794726): > > > "@kirillcool 5 FTE's took one year to create #SWT Cocoa port; 4 of > > the 5 knew the API inside out. A new AWT would take at least as long." > > > 5 engineers, at California salaries, benefits, and taxes, is probably > > around US$1million a year. So that's where I would estimate the pricet > > of a production-quality AWT/Swing port. > > But I'm not talking of redoing the same thing Apple did. As fas as I > know, Quaqua (100% pure Java Aqua widgets) would be ok and I'm just > thinking of a "lightweight" (if we can say so) porting so at least > JWindow and JFrame run inside a Cocoa window. > > -- > f.g. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
