jQuery datepicker年显示(jQuery datepicker years shown)

 语言跳转可以。 一旦你超过了[和]的最初的冲击。 然而，图书馆和框架的冲击将是巨大的。 
 
 与.Net框架相比，Cocoa和Touch框架明显更轻，所以至少你可以看到光明的一面，你学习的少一些。 但它们的基本哲学，布局和历史演进路径与C＃/ .Net框架截然不同。 这是否容易或难，难以理解。 一些个人意见 
 
 
 
 可可的构建UI的方式是光年之前的任何东西 .Net框架今天，Forms或WPF。 一开始就难以掌握，但如果你的意思是这样，那将会很有意义。 它是基于Smalltalk框架的好的“ 模型 - 视图 - 控制器” ，并且将自然地引导您设计UI的正确路径。 
 
 
 图形，视频，媒体将来自另一个星球，来自.Net背景。 但尽管它们的表现非常神秘，但Cocoa的产品却非常强大，尽管不尽如人意。 
  
 
   
 可可绘图指南简介 
 
   
 石英2D概述 
 
   
 核心视频编程指南简介 
 
   
 核心音频概述 
 
  
 
 
 动画将是一个巨大的叹息。 可可动画简单易用 ，而且.Net中没有什么相似之处 
  
 
   
 核心动画编程指南简介 
 
  
 
 
 如果你做OpenGL而不是Cocoa的原生图形，那么OpenGL和openGL在任何平台上都是一样的。 
 
 
 网络编程在可可方面较差。 你有一些基本的支持，不得不承认，至少API的设计真的很难做愚蠢的东西（它强制你使用异步编程，所以没有更多的单线程每个客户端非感觉），但我' d赌你会错过.Net糖工具（WebRequest，WebClient等） 
  
 
   
 NSConnection类参考 
 
   
 分布式对象简介 
 
  
 
 
 XML解析。 可可支持只是简单的原始。 至少，XML解析是事件驱动的，所以要引导你更好的程序，但是组合起来很复杂。 
  
 
   
 Cocoa事件驱动XML编程指南简介 
 
  
 
 
 数据库。 将是一个不同的世界。 您可以选择进行原始SQLite或核心数据。 核心数据更好。 是一个高水平的ORM和活跃的记录种类的东西，底层存储的所有错综复杂的抽象出来。 易于使用和强大，只要你要求它做一些它知道如何做的事情。 令人难以置信的麻烦，迫使它做一些不知道该怎么办的事情。 对于任何ORM，最终都是真的。 你会想念LINQ，你必须忘记SQL。 其要点是，.Net中的DB编程经验不会转移到Core Data世界。 原始SQLite的替代方案看起来更加熟悉，但是级别非常低，将会比2010年的.NET更像是编写1990年的ODBC。 
  
 
   
 核心数据编程指南简介 
 
  
 
 
 键值编码编程 。 这个概念没有直接的.Net等价物。 这可能听起来像某种简单的字典，但其实是更强大的方式。 它与[Objective-C]的Objective部分的运行时引擎进行交互，并产生一些整洁的技巧。 您需要了解键值编码才能有效利用Core Animation或Core Data。 您可以将其视为类固醇的反射。 它可以实现Linq对对象可以做的一些相同的技巧，但不会像Linq那样优雅。 
 
 
 是C ++。 Objective-C是C ++的超集 ，并且由最近的gcc下载支持，所以你可以随时回到C ++。 STL ，函子， 模板元编程 ，它们都工作。 您可以在同一应用程序中混合使用纯Cocoa和Core Objective-C与C ++。 您将无法做一些像C ++类继承Objective-C类的内容，但是您可以在C ++类和Objective-C对象之间进行通信。 不知道boost或Loki支持的当前状态是什么。 
 
 
 Cocoa的许多地区都有不同的第三方图书馆，但是我无法比较所有Cocoa第三方与.Net 3r方面的对比，我有一个生命... 
 
 总的来说，我将很快总结一下， 在Objective-C中，条目栏更高。 带大脑 

The language jump is OK. Once you get past the initial shock of [ and ]. However, the libraries and Framework shock will be substantial.
 
The Cocoa and Touch frameworks are significantly lighter when compared with .Net Framework, so at least you can look at the bright side, you have less to learn. But their underlying philosophy, layout and historic evolution path is very different from the C#/.Net framework. Whether this will be easy or hard, is difficult to appreciate. Some personal opinions:
 
 
 
The Cocoa way of building UI is light years ahead of anything .Net framework has today, Forms or WPF. It will be difficult to grasp at first, but if your grok it, it will make a LOT of sense. It is good ole' Model-View-Controller based on Smalltalk framework and will naturally guide you down a right path of designing UI.
 
 
Graphics, video, media are going to feel as from another planet when coming from .Net background. But despite their apparent arcane appearance, the Cocoa offerings are very powerful, although somehow low level. 
  
 
   
Introduction to Cocoa Drawing Guide
 
   
Quartz 2D Overview
 
   
Introduction to Core Video Programming Guide
 
   
Core Audio Overview
 
  
 
 
Animation is going to be a huge sigh of relief. Cocoa animation is just plain easy to use, and there isn't anything equivalent in .Net 
  
 
   
Introduction to Core Animation Programming Guide
 
  
 
 
If you do openGL instead of Cocoa native graphics, then is openGL and openGL is pretty much the same flavor on any platform.
 
 
Network programming is poorer on Cocoa side. You have some basic support and gotta admit that at least the API is designed that is really hard to do stupid stuff (it forces you to use async programming, so no more one-thread-per-client non-sense), but I'd bet you'll miss the .Net sugar utilities (WebRequest, WebClient etc) 
  
 
   
NSConnection Class Reference
 
   
Introduction to Distributed Objects
 
  
 
 
XML parsing. Cocoa support is just plain primitive. At least, again, the XML parsing is event driven so is going to guide you toward better programs, but is complicated to put together. 
  
 
   
Introduction to Event-Driven XML Programming Guide for Cocoa
 
  
 
 
Database. Is going to be a different world. You have the choice of going raw SQLite or Core Data. Core Data is better imho. Is a high level ORM and active record kind of stuff, with all the intricacies of the underlying storage abstracted away. Easy to use and powerful, as long as you ask it to do something it knows how to do. Unbelievably cumbersome to force it to do something it doesn't know how to do. True for any ORM, ultimately. You'll miss LINQ, and you'll have to forget SQL. The gist of it is that the DB programming experience from .Net just doesn't transfer to Core Data world. The alternative of raw SQLite will look more familiar, but is very low level, will feel more like programing 1990 ODBC than 2010 .Net. 
  
 
   
Introduction to Core Data Programming Guide
 
  
 
 
Key-Value Coding Programming. This concept has no direct .Net equivalent. It may sound like some sort of simple dictionary, but in fact is way more powerful. It interweaves with the runtime engine of the Objective part of [Objective-C] and gives birth to some neat tricks. You'll need to understand Key-Value coding to make efficient use of Core Animation or Core Data. You can think at it as reflection on steroids. It can achieve some of the same tricks Linq-to-Objects can do, but is not going to be anywhere as elegant as Linq.
 
 
Is C++. Objective-C is a superset of C++ and is backed by recent drops of gcc, so you can fall back to C++ anytime. STL, functors, template metaprogramming, they all work. You can mix and match in the same application pure Cocoa and Core Objective-C with C++. You won't be able to do something like inherit an Objective-C class as a C++ class, but you will be able to communicate between a C++ class and an Objective-C object. Not sure what is the current status of boost or Loki support. 
 
 
Many of the areas covered poorly in Cocoa have various 3rd party libraries, but I can't enter into comparison all Cocoa 3rd parties vs. .Net 3r parties, I have a life...
 
Overall, I would sum it up shortly as In Objective-C the entry bar is higher. Bring a brain.