On Jan 09, 2007, at 23:28 UTC, Seth Willits wrote: > It's not worth all of the hassle of jumping through hoops just to get > a fonts panel (as a simple example) or a color picker (that crashes) > when they come for free in Cocoa. Meatier examples would be the > entire text architecture in Cocoa or the outline and table views.
OK, I know I said I wouldn't reply again, but I think this brings up a point that really needs to be driven home. Rewriting the framework in Cocoa does NOT imply that you're going to get these other things for free. Would it magically make a FontPanel class appear, for example? No. Somebody at RB would have to actually write such a class to add it to the framework (after careful consideration of what the API should be, what that API should do on other platforms, etc.). It's not something you get for free just because more of the framework is Cocoa. You still get, out of the box, only the set of features you get out of the box. Anything more than that, you have to use plugins or declares, same as before. This is a really important point. I think that many of the people shouting "I want a Cocoa framework!" really mean "I want this long list of new features in the RB framework!" And they imagine that these two demands are the same thing. They are not. The most likely outcome of a rewritten framework, IMHO, is pretty much exactly the same feature set, with a new slew of bugs. So if RB succumbs to the demands and spends months doing this instead of something more useful, remember, you asked for it. And don't complain when all those features you were imagining don't magically appear. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
