Jeff Schwab wrote: > Robert Walker wrote: > Mostly agreed. It's very much like Rails, or C++ template
This seems to me to be a gross oversimplification. While there may be some similarities, in that they both implement the basic MVC design pattern, Cocoa development involves design patterns that are rarely seen in Rails, or any other web framework. Patterns such as chain of responsibility, decorator/delegation, command, composite/view hierarchy, key value code/key value observing. My only real point here is that any similarities with Rails falls away very quickly when you get into the inner workings of the Cocoa framework. > metaprogramming, in the sense that convention is leveraged to define > program structure. Restrictions aren't necessarily a bad thing. The > one aspect of Cocoa development that does really bother me is that it's > only really meant to be done in XCode, with which I am not thrilled. I do admit that Xcode's text editor could use some work. However, I'd rather use Xcode's integrated editor over many of the other IDEs I've used like Eclipse, NetBeans, JDeveloper, etc. However, as Jim stated, you don't have to use it. You can use whatever editor you want. The fact is though, that there is much more focus placed on features for dealing with the complexities of desktop application development, which don't apply to web based frameworks like Rails. All you really need to develop a Rails application is a text editor and a command line. Xcode is, by necessity, much more that a simple text editor. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
