On Sat, Apr 10, 2010 at 2:25 PM, [email protected] < [email protected]> wrote:
> > "Java UI builders could learn a thing or two from IB. " > > That is such a sad statement! I find IB to be pretty pathetic. But > all the Java UI builders I've used are terrible IMO. > I remember using the UI builder in JBuilder 2 (I think) and was bitten severely when I manually changed some of the generated code and was then unable to use the UI builder any more. IB used to generate a binary file that was essentially a freeze-dried version of your UI. It now generates XML, but it's still easier to use IB than to hand-edit. > Delphi 15 years ago kills both Java and IB for WYSIWYG UI building. I used to work for a guy who really thought Delphi was the bee's knees. I never used it (long-time Pascal prejudice), but I remember him being extremely productive in it.. > I could crank out UIs in Delphi ridiculously fast. And the UIs > actually look like what I designed, unlike IB. IB has all kinds of > weird little issues where a nav bar bars pushes the views down. The > bindings are very much non-obvious. Pretty limited set of widgets. > And the NIB magic is hard to figure out. A lot of iPhone/mac devs > don't bother with IB and just hand code everything. At least you can > tell what's going on and control it. > > The bindings in IB, I thought, were one of its strongest features. Agreed that sometimes what you design differs from the ultimate output, but I didn't encounter that much. > Obj C- not hard to learn. Has some features I wish Java had like > properties, method pointers, dynamic methods, and categories. But > it's still has a lot of clunkiness. String manipulations are a > PITA. Pointers all over the place. Header files (YUCK!) > It's not hard to learn, but there are aspects of it which will trip you up, such as forgetting to convert an Obj-C string to a C string before passing it to a C function. When you're working with most Cocoa libraries, you get to work in an OK OO world, but when you have to call down into anything deeper, you have to convert between OO and C, which can be tedious and easy to mess up. | IMO Objective C needs to be morphed into a pointerless/headerless > language or replaced with something more modern. Agreed! Joey -- Blog: http://joeygibson.com Twitter: http://twitter.com/joeygibson FriendFeed: http://friendfeed.com/joeygibson Facebook: http://facebook.com/joeygibson -- 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.
