手机差距VS MonoTouch的数据密集型应用程序 [英] phone gap vs monotouch for data intensive app
问题描述
我们正在寻找开发用于移动设备的数据密集型应用。我们的核心问题是
We are looking to develop a data intensive application for mobile devices. Our central problem is
- 我们将必须存储相当大量的数据在客户端上
- 客户希望应用程序脱机工作
- 我们的技能非常多的Web开发C＃ASP.Net。非也目标C
我们已经想到了三种可能性进行开发
We have thought of three possibilities for dev
Web application using HTML5 local storage leveraging the offline application cache. We are on a 5MB limit for local storage but this might be down to 2.5MB for certain browsers
Web应用程序= http://phonegap.com/\">PhoneGap 来创建本机应用程序。
大的优势在这里是我们可以使用文件系统进行存储。不利的一面是，它必须要经过的App Store（iOS设备尤其是） - 30％的收入夹头订阅应用苹果
Web application through PhoneGap to create a native app. Big advantage here is that we can use the file system for storage. The down side is that it will have to go through App Store (for iOS especially) - 30% chuck of revenue for a subscription app to Apple
我们打造出使用
好 - C＃和.NET，我们可以做到这一点。糟糕 - 没有黑莓
We build out the app using MonoTouch for Android and iOS. Good - C# and .Net we can do this. Bad - no Blackberry
问
我挣扎看到在这种情况下使用MonoTouch的过度的PhoneGap的任何真正的优势。他们是什么？难道他们的？
I'm struggling to see any genuine advantages of using MonoTouch over PhoneGap in this instance. What are they? Are they any?
在本实例的例子这将是非常有用的数据保存到文件系统，但我相信，手机差距可以通过做到这一点的<一个HREF =http://docs.phonegap.com/en/1.0.0/phonegap_file_file.md.html#File>文件对象。很显然的MonoTouch将利用System.IO
As an example in this instance it would be really useful to save data onto the file system but I believe that phone gap can do this through the File object. Obviously monoTouch would leverage System.IO.
有情况下，人们在MonoTouch的明确附加功能 - 这是移动开发例如特别有用的功能地理位置或相机类型函数？还是手机的差距几乎已经全部这些覆盖。
Is there instances where there is definite additional functionality in MonoTouch - particularly functions that are useful to mobile dev e.g. Geolocation or camera type functions?. Or does phone gap pretty much have all these covered.
厚颜无耻的其他问题
是否有我错过了任何其他选项或任何其他主要优势/劣势我提出，我已经忘记了这三种方法？
Is there any other options I have missed or any other major advantages/disadvantages for the three approaches I have outlined that I have forgotten about?
每个人的专长谢谢
推荐答案
我们刚刚完成写在MonoTouch的一个非常数据密集型应用程序。该应用程序访问SAP数据，通过一个中间层，并公开本上的应用程序。它还允许直接更新从应用程序到SAP，再通过同样的中间层。
We have just finished a very data intensive app written in MonoTouch. The app accesses SAP data, through a middle tier, and exposes this on the app. It also allows direct updates from the app to SAP, again through the same middle tier.
我们在这个移植到Windows Phone，并使用Android的MonoDroid的的过程。
We are in the process of porting this to Windows Phone and Android using MonoDroid.
我花了一段时间来说服老板的MonoTouch是转发的方式，我们尝试了一些不同的产品事先包括jQuery Mobile的，ExtJS的和的OBJ℃。
It took me a while to convince the boss that MonoTouch was the way forwards, and we tried a few different products beforehand including jQuery mobile, ExtJS and Obj C.
我试图说服他的时间是Attachmate公司收购时，它看起来，有时候，喜欢的MonoTouch是注定要失败。幸运的是（我的），Xamarin上涨就像众所周知的凤凰从火焰，他们继续发展单声道*到今天的样子。
The time I was trying to convince him was the time of the Attachmate acquisition and it looked, at times, like MonoTouch was doomed. Luckily for us (me), Xamarin rose like the proverbial Phoenix from the flames, and they have continued to develop Mono* to what it is today.
作为一个C＃开发人员（和Mono爱好者）以上的OBJ C或任何HTML的主胜/ JavaScript的是事实，我可以使用C＃来完成这项工作。该文档是非常好，而当DOCO并没有完全把它（最近被更新）社区做到了。
As a C# developer (and Mono enthusiast) the main win over Obj C or any of the HTML/JavaScript was the fact that I could use C# to get the job done. The documentation was very good, and when the doco didn't quite cut it (recently been updated) the community did.
在IRC频道中非常活跃，与Xamarin员工和社区的传道者总是愿意帮助或提供洞察问题。由于是邮件列表。
The IRC channel is very active, with Xamarin employees and community evangelists always willing to help or provide insight into a problem. As are the mailing lists.
另一个好处是它周围越来越多的MT生态系统。 MT.Dialog使得开发基于表格的界面相比，相当于XCode的绝对轻而易举。夫妇与此.NET基础类库这是不可否认基于Silverlight的一个子集，但它有一切从系列化，电邮密码等..如果.NET不覆盖它，还是没有一个具体的单声道*项目，你仍然可以使用ObjC插件与MT的代码。
Another plus are the Eco-systems which are growing around MT. MT.Dialog makes developing Table based UI's an absolute breeze compared to the XCode equivalent. Couple with this the .Net BCL which is, admittedly a subset based on Silverlight, but it has everything from Serialization, Email to Cryptography etc... If .Net doesn't cover it, or there isn't a specific Mono* project, you can still use ObjC plugins with your MT code.
我不同意MT有尚未证明自己作为一个成熟的平台。我们正在使用它，而我们是一个相对较小的公司，有很多大公司也使用它。一些苹果在这里澳元电视广告展示了应用程序是，据报道，写的MT。
I disagree that MT has 'yet to prove itself' as a proven platform. We are using it, and whilst we are a relatively small company, there are lots of larger companies also using it. A few of the apps showcased by Apple in the TV ads here in Aus are, reportedly, written in MT.
为了保持客观，2'缺点'的MonoTouch的，我一直认为你还需要能够读取ObjC（虽然TBH，我不认为这是一个骗子......作为C＃的开发者，我必须能够读取和写入过多反正语言）和事实，从历史上看，MonoDevelop的已经有点马车。 ！主要的错误似乎被压扁，并与它是一个开源项目，你总是可以解决这些问题，并帮助我们的休息
In order to remain objective, the 2 'cons' of MonoTouch for me have been that you still need to be able to read ObjC (though, tbh, I don't see this as a con... As a 'C#' developer I have to be able to read and write a plethora of languages anyway) and the fact that, historically, MonoDevelop has been a bit buggy. The major bugs appear to have been squashed and, with it being an open source project, you can always fix them and help the rest of us!
要回答您的问题：
- 我们将必须存储相当大量的数据在客户端上
使用的.Net的System.IO类在C＃。如果您不确定这些，MSDN有例子不减当年（MT隐藏的iOS实现文件存储）
Use the System.IO classes of .Net in C#. If you are unsure of these, MSDN has oodles of examples (MT hides the iOS implementation of file storage)
- 的客户想要的应用脱机工作
他们都可以做到这一点，但本机应用程序总是会感觉更好，我认为。
they can all do this, but a Native app is always going to feel better in my opinion.
- 我们的技能非常多的Web开发C＃ASP.Net。非也目标C
MonoTouch的是C＃ - 在几周发挥自己的优势，并有一个应用程序，而不是几个月。
MonoTouch is C# - play to your strengths and have an app in weeks, not months!
我的2便士！我会毫不犹豫地再次选择同样的路线，一遍又一遍。
My 2 pennies! I would not hesitate to choose the same route again, again and again.
这篇关于手机差距VS MonoTouch的数据密集型应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
