<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: REALbasic on iPhone Debate</title>
	<atom:link href="http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/</link>
	<description>Software Development Using REALbasic</description>
	<lastBuildDate>Sun, 05 Sep 2010 16:00:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Bob Keeney</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-313</link>
		<dc:creator>Bob Keeney</dc:creator>
		<pubDate>Thu, 08 Apr 2010 21:14:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-313</guid>
		<description>New today is this new except from the iPhone 4.0 SDK:

3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).

Here, they are explicitly saying what language is allowed!  Wow.  That seems awful restrictive.</description>
		<content:encoded><![CDATA[<p>New today is this new except from the iPhone 4.0 SDK:</p>
<p>3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).</p>
<p>Here, they are explicitly saying what language is allowed!  Wow.  That seems awful restrictive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Schmitz</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-271</link>
		<dc:creator>Christian Schmitz</dc:creator>
		<pubDate>Tue, 23 Mar 2010 08:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-271</guid>
		<description>Well, to sign you need your private developer key and the provision profile. I have for example 3 private keys for 3 different accounts and I need to choose the right one for each project to sign it correctly. But I&#039;m not sure whether it is a good idea to upload those keys to a server somewhere. Does Apple allow/deny that? And why should RS not simply say: iPhone development is Mac only and please install Xcode first?</description>
		<content:encoded><![CDATA[<p>Well, to sign you need your private developer key and the provision profile. I have for example 3 private keys for 3 different accounts and I need to choose the right one for each project to sign it correctly. But I&#8217;m not sure whether it is a good idea to upload those keys to a server somewhere. Does Apple allow/deny that? And why should RS not simply say: iPhone development is Mac only and please install Xcode first?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Dent</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-270</link>
		<dc:creator>Andy Dent</dc:creator>
		<pubDate>Tue, 23 Mar 2010 03:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-270</guid>
		<description>It would be a useful addition to the Enterprise edition to allow someone to sign iPhone apps on others&#039; behalf. This could then become a consulting activity where you could find some other provider of the service rather than having to rely on RS running an inhouse server.</description>
		<content:encoded><![CDATA[<p>It would be a useful addition to the Enterprise edition to allow someone to sign iPhone apps on others&#8217; behalf. This could then become a consulting activity where you could find some other provider of the service rather than having to rely on RS running an inhouse server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Perlman</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-269</link>
		<dc:creator>Geoff Perlman</dc:creator>
		<pubDate>Mon, 22 Mar 2010 13:31:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-269</guid>
		<description>If REAL Software disappeared and REAL Studio wasn&#039;t acquired by some other company, having to find access to a Mac so that you can install your certificate would be the least of your problems. The fact is, the code signing utility that Apple provides runs only on a Mac. I&#039;m imagining that we could provide a Mac server as a convenience to Windows users. I would rather not have to do that but unfortunately, this is one issue that may not have a better, more feasible solution.</description>
		<content:encoded><![CDATA[<p>If REAL Software disappeared and REAL Studio wasn&#8217;t acquired by some other company, having to find access to a Mac so that you can install your certificate would be the least of your problems. The fact is, the code signing utility that Apple provides runs only on a Mac. I&#8217;m imagining that we could provide a Mac server as a convenience to Windows users. I would rather not have to do that but unfortunately, this is one issue that may not have a better, more feasible solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Ballman</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-268</link>
		<dc:creator>Aaron Ballman</dc:creator>
		<pubDate>Mon, 22 Mar 2010 13:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-268</guid>
		<description>@Geoff -- are you intending for the iPhone offerings to mostly target the hobbyist market?  I ask because there are some serious flaws I would worry about as a professional.  Servers go down, companies disappear, etc -- expecting me to rely on a third party for basic functionality any time I wish to release an application is a high risk.  And telling me &quot;well, just go buy a Mac if you&#039;re worried about that&quot; is an awfully expensive hidden cost, and doesn&#039;t jive at all with REALbasic&#039;s long history of allowing me to write code on one platform and run it on another.</description>
		<content:encoded><![CDATA[<p>@Geoff &#8212; are you intending for the iPhone offerings to mostly target the hobbyist market?  I ask because there are some serious flaws I would worry about as a professional.  Servers go down, companies disappear, etc &#8212; expecting me to rely on a third party for basic functionality any time I wish to release an application is a high risk.  And telling me &#8220;well, just go buy a Mac if you&#8217;re worried about that&#8221; is an awfully expensive hidden cost, and doesn&#8217;t jive at all with REALbasic&#8217;s long history of allowing me to write code on one platform and run it on another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Perlman</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-267</link>
		<dc:creator>Geoff Perlman</dc:creator>
		<pubDate>Sat, 20 Mar 2010 16:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-267</guid>
		<description>There&#039;s no need to sign the app on a Windows machine. We would easily provide a service where the user could upload their code signing certificate and app to a Mac at REAL which would then sign the app via Apple&#039;s code signing utility and then download it again. Others have solved this problem. The article also mentions running the iPhone SDK on a non Apple-branded machine. But a REAL Studio user would not be using the iPhone SDK at all. They would be using our framework so that&#039;s not an issue either.</description>
		<content:encoded><![CDATA[<p>There&#8217;s no need to sign the app on a Windows machine. We would easily provide a service where the user could upload their code signing certificate and app to a Mac at REAL which would then sign the app via Apple&#8217;s code signing utility and then download it again. Others have solved this problem. The article also mentions running the iPhone SDK on a non Apple-branded machine. But a REAL Studio user would not be using the iPhone SDK at all. They would be using our framework so that&#8217;s not an issue either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Keeney</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-266</link>
		<dc:creator>Bob Keeney</dc:creator>
		<pubDate>Sat, 20 Mar 2010 15:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-266</guid>
		<description>Lest anyone forget that Apple guards access to their kingdom very closely, I suggest you read the article at http://www.informationweek.com/news/software/linux/showArticle.jhtml?articleID=224000202.  

The relevant quote:  &quot;It would be a technical violation of the Apple SDK to [generate and sign an iPhone binary] on a Windows machine,...&quot;

I believe RS would have to jump through the same problems *if* they made iPhone support cross-platform.  Since this is all mental gyrations at this point it doesn&#039;t really matter.</description>
		<content:encoded><![CDATA[<p>Lest anyone forget that Apple guards access to their kingdom very closely, I suggest you read the article at <a href="http://www.informationweek.com/news/software/linux/showArticle.jhtml?articleID=224000202" rel="nofollow">http://www.informationweek.com/news/software/linux/showArticle.jhtml?articleID=224000202</a>.  </p>
<p>The relevant quote:  &#8220;It would be a technical violation of the Apple SDK to [generate and sign an iPhone binary] on a Windows machine,&#8230;&#8221;</p>
<p>I believe RS would have to jump through the same problems *if* they made iPhone support cross-platform.  Since this is all mental gyrations at this point it doesn&#8217;t really matter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Young</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-264</link>
		<dc:creator>Mike Young</dc:creator>
		<pubDate>Mon, 15 Mar 2010 12:31:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-264</guid>
		<description>I&#039;ve built several real estate analytical apps in RB. Owing to the number of input fields, the &quot;real estate&quot; on the iPhone/iPod Touch is too small. On the iPad, however, we have the perfect platform for my apps. I am too old to learn the languages needed to reprogram my apps for the iPad but would like an easy way to migrate from standalone RB to iPad. That would be a home run for me.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve built several real estate analytical apps in RB. Owing to the number of input fields, the &#8220;real estate&#8221; on the iPhone/iPod Touch is too small. On the iPad, however, we have the perfect platform for my apps. I am too old to learn the languages needed to reprogram my apps for the iPad but would like an easy way to migrate from standalone RB to iPad. That would be a home run for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith DeLong</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-248</link>
		<dc:creator>Keith DeLong</dc:creator>
		<pubDate>Fri, 05 Mar 2010 17:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-248</guid>
		<description>&lt;a href=&quot;#comment-232&quot; rel=&quot;nofollow&quot;&gt;@Bob Keeney &lt;/a&gt; 
I would not be at all opposed if the solution was Mac OS X only.</description>
		<content:encoded><![CDATA[<p><a href="#comment-232" rel="nofollow">@Bob Keeney </a><br />
I would not be at all opposed if the solution was Mac OS X only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jjb</title>
		<link>http://www.bkeeneybriefs.com/2010/03/realbasic-on-iphone-debate/comment-page-1/#comment-247</link>
		<dc:creator>jjb</dc:creator>
		<pubDate>Fri, 05 Mar 2010 00:03:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.bkeeneybriefs.com/?p=582#comment-247</guid>
		<description>&quot;Do you think RS should use *EXISTING* development resources to make REALbasic support the iPhone.&quot;

My understanding of the latest REAL blog entry is that the forthcoming switch to using LLVM is that amongst its benefits is to provide a VM to native compiler for the iphone.
Also, (and I&#039;m guessing) having no longer to maintain the 2 backend compilers will free up some resources for other uses  :smile:  
I&#039;d like to read your take on the implications of the switch to the LLVM.</description>
		<content:encoded><![CDATA[<p>&#8220;Do you think RS should use *EXISTING* development resources to make REALbasic support the iPhone.&#8221;</p>
<p>My understanding of the latest REAL blog entry is that the forthcoming switch to using LLVM is that amongst its benefits is to provide a VM to native compiler for the iphone.<br />
Also, (and I&#8217;m guessing) having no longer to maintain the 2 backend compilers will free up some resources for other uses  <img src='http://www.bkeeneybriefs.com/wp-includes/images/smilies/icon_smile.gif' alt=':smile:' class='wp-smiley' /><br />
I&#8217;d like to read your take on the implications of the switch to the LLVM.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
