<?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 for Solipsism Gradient</title>
	<atom:link href="http://brockerhoff.net/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://brockerhoff.net/blog</link>
	<description>Rainer Brockerhoff’s blog</description>
	<lastBuildDate>Wed, 11 Jan 2012 08:53:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on AddLicense tool by Rainer Brockerhoff</title>
		<link>http://brockerhoff.net/blog/2010/02/10/addlicense-tool/comment-page-1/#comment-14901</link>
		<dc:creator>Rainer Brockerhoff</dc:creator>
		<pubDate>Wed, 11 Jan 2012 08:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/bb/viewtopic.php?p=2779#comment-14901</guid>
		<description>Yes, those two languages are tricky; they&#039;re encoded into the Classic two-byte encoding, not into Unicode, and not all characters are supported. I did test it at the time by pasting in some random Korean and Japanese text, but never used it myself in practice. Can you email me the actual text?

At any rate, I&#039;m currently on vacation and have limited time and facilities for testing this. Will try to look into it when I come back in late January 2012.</description>
		<content:encoded><![CDATA[<p>Yes, those two languages are tricky; they&#8217;re encoded into the Classic two-byte encoding, not into Unicode, and not all characters are supported. I did test it at the time by pasting in some random Korean and Japanese text, but never used it myself in practice. Can you email me the actual text?</p>
<p>At any rate, I&#8217;m currently on vacation and have limited time and facilities for testing this. Will try to look into it when I come back in late January 2012.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on AddLicense tool by cylon</title>
		<link>http://brockerhoff.net/blog/2010/02/10/addlicense-tool/comment-page-1/#comment-14899</link>
		<dc:creator>cylon</dc:creator>
		<pubDate>Wed, 11 Jan 2012 08:04:36 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/bb/viewtopic.php?p=2779#comment-14899</guid>
		<description>I use your source code to AddLicense, but it does not work for language &#039;ja&#039; and &#039;ko&#039;
Do you know how to use this
Thank you for your code</description>
		<content:encoded><![CDATA[<p>I use your source code to AddLicense, but it does not work for language &#8216;ja&#8217; and &#8216;ko&#8217;<br />
Do you know how to use this<br />
Thank you for your code</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RBSplitView on Lion by Rainer Brockerhoff</title>
		<link>http://brockerhoff.net/blog/2011/07/21/rbsplitview-on-lion/comment-page-1/#comment-10710</link>
		<dc:creator>Rainer Brockerhoff</dc:creator>
		<pubDate>Wed, 12 Oct 2011 23:11:19 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/blog/?p=2687#comment-10710</guid>
		<description>Hi Peter, nothing much new, unfortunately. One idea I discussed with another user was to convert the RBSplitView as above, then unpack the RBSplitSubviews out of the RBSplitView, removing that entirely.
Then move the RBSplitSubviews to the top level in the nib, and re-build the RBSplitView programatically. I don&#039;t know if this would work yet for a more complex case; if you don&#039;t have nesting, it should work.
Unfortunately I have no time to try it out myself right now...</description>
		<content:encoded><![CDATA[<p>Hi Peter, nothing much new, unfortunately. One idea I discussed with another user was to convert the RBSplitView as above, then unpack the RBSplitSubviews out of the RBSplitView, removing that entirely.<br />
Then move the RBSplitSubviews to the top level in the nib, and re-build the RBSplitView programatically. I don&#8217;t know if this would work yet for a more complex case; if you don&#8217;t have nesting, it should work.<br />
Unfortunately I have no time to try it out myself right now&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RBSplitView on Lion by Peter</title>
		<link>http://brockerhoff.net/blog/2011/07/21/rbsplitview-on-lion/comment-page-1/#comment-10709</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 12 Oct 2011 23:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/blog/?p=2687#comment-10709</guid>
		<description>Hi,
Pitty to read about the problems.
We are using your splitview in two of our apps, and would, actualy have to, update them for Lion.
Did you found a solution or a new idea how to get it working under Lion?

Thank you very much.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Pitty to read about the problems.<br />
We are using your splitview in two of our apps, and would, actualy have to, update them for Lion.<br />
Did you found a solution or a new idea how to get it working under Lion?</p>
<p>Thank you very much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Highly Advanced But Obsolete by Rodolfo Koeppel</title>
		<link>http://brockerhoff.net/blog/2003/12/14/highly-advanced-but-obsolete-2/comment-page-1/#comment-10327</link>
		<dc:creator>Rodolfo Koeppel</dc:creator>
		<pubDate>Fri, 07 Oct 2011 18:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/bb/viewtopic.php?p=719#comment-10327</guid>
		<description>Herr Brockerhoff: What a great pleasure to receive this Blog address and being able to read about how you did the QI-900 software. 

I purchased a unit, the first commercial computer for my applications software company and it worked fine, flawless, during many years, before being superseeded  by the IBM-PC. 

The availability of flexible disks of different sizes (5 1/4 and 8 inches), and also a &quot;huge&quot; Harddisk (not the size - 5 Megabytes, but the weight!) made your QI-900 an outstanding work-horse. The avalilability of a special program, which supported reading and writing more than one hundred distincts protocols, made the machine specially useful for a software house.

And of course, the concept of windows, drop-down menus, etc made it a very interesting machine, besides full CP/M compatibility. 

At that time, we did the processing for many large brazillian financial companies. Usually the systems run in some mini-computers (type Data General, Type Nixdorf, etc mini computers) but we used the QI-900 to develop and test new programs. 

One, specially, has surprised us: usually, in order to calculate the IRR - internal rate of return - for each financing contract, it took two hours each day, for a typical daily batch. Which did not permit us to acumulate any batches during the week, otherwise we could not catch up afterwards. The first day we tested it on the QI-900, it took less than 2 minutes.  We imagined that nothing had been processed... And to our astonhisment, every IRR was computed! From that day on, we started moving from mini-computers to QI-800 and QI-900 microcomputers, cheaper and faster. 

The minicomputers were not bad if you used other languages - Assembly or Basic, but for Cobol language translation, it took almost one hour to compile a single program. In the QI-900 it was almost instantaneus!

The QI-900 keyboard was something really made to last a thousand years! Very nice to the touch, very well organized, never failed.

I kept the QI-900 for many years, donating it afterwards to Prodemge (the State Computing Center in Minas Gerais) Museum, where it dissapeared when they closed the Museum. It was still running like it were the first day of purchase!

Now I will go to your blog and get some more interesting stories. Best Regards from Rodolfo Koeppel</description>
		<content:encoded><![CDATA[<p>Herr Brockerhoff: What a great pleasure to receive this Blog address and being able to read about how you did the QI-900 software. </p>
<p>I purchased a unit, the first commercial computer for my applications software company and it worked fine, flawless, during many years, before being superseeded  by the IBM-PC. </p>
<p>The availability of flexible disks of different sizes (5 1/4 and 8 inches), and also a &#8220;huge&#8221; Harddisk (not the size &#8211; 5 Megabytes, but the weight!) made your QI-900 an outstanding work-horse. The avalilability of a special program, which supported reading and writing more than one hundred distincts protocols, made the machine specially useful for a software house.</p>
<p>And of course, the concept of windows, drop-down menus, etc made it a very interesting machine, besides full CP/M compatibility. </p>
<p>At that time, we did the processing for many large brazillian financial companies. Usually the systems run in some mini-computers (type Data General, Type Nixdorf, etc mini computers) but we used the QI-900 to develop and test new programs. </p>
<p>One, specially, has surprised us: usually, in order to calculate the IRR &#8211; internal rate of return &#8211; for each financing contract, it took two hours each day, for a typical daily batch. Which did not permit us to acumulate any batches during the week, otherwise we could not catch up afterwards. The first day we tested it on the QI-900, it took less than 2 minutes.  We imagined that nothing had been processed&#8230; And to our astonhisment, every IRR was computed! From that day on, we started moving from mini-computers to QI-800 and QI-900 microcomputers, cheaper and faster. </p>
<p>The minicomputers were not bad if you used other languages &#8211; Assembly or Basic, but for Cobol language translation, it took almost one hour to compile a single program. In the QI-900 it was almost instantaneus!</p>
<p>The QI-900 keyboard was something really made to last a thousand years! Very nice to the touch, very well organized, never failed.</p>
<p>I kept the QI-900 for many years, donating it afterwards to Prodemge (the State Computing Center in Minas Gerais) Museum, where it dissapeared when they closed the Museum. It was still running like it were the first day of purchase!</p>
<p>Now I will go to your blog and get some more interesting stories. Best Regards from Rodolfo Koeppel</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Perspective by Francis</title>
		<link>http://brockerhoff.net/blog/2011/10/06/perspective-2/comment-page-1/#comment-10306</link>
		<dc:creator>Francis</dc:creator>
		<pubDate>Fri, 07 Oct 2011 08:50:05 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/blog/?p=2690#comment-10306</guid>
		<description>Always great to hear from you, Rainer! All the best!</description>
		<content:encoded><![CDATA[<p>Always great to hear from you, Rainer! All the best!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Re: WWDC2011 (part1) by James G</title>
		<link>http://brockerhoff.net/blog/2011/06/13/re-wwdc2011-part1/comment-page-1/#comment-6264</link>
		<dc:creator>James G</dc:creator>
		<pubDate>Mon, 13 Jun 2011 18:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/blog/?p=2678#comment-6264</guid>
		<description>now if only apple could figure out how to get a &quot;compile this file&quot; command into xcode so I could actually use it, then I could switch to all the great new tools. The java-tization of xcode is somewhat annoying IMO.</description>
		<content:encoded><![CDATA[<p>now if only apple could figure out how to get a &#8220;compile this file&#8221; command into xcode so I could actually use it, then I could switch to all the great new tools. The java-tization of xcode is somewhat annoying IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lion is coming by hsoi</title>
		<link>http://brockerhoff.net/blog/2011/02/28/lion-is-coming/comment-page-1/#comment-4795</link>
		<dc:creator>hsoi</dc:creator>
		<pubDate>Thu, 10 Mar 2011 11:56:28 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/blog/?p=2672#comment-4795</guid>
		<description>I didn&#039;t realize Rosetta was going to go away. That&#039;s understandable from Apple&#039;s &quot;moving forward&quot; perspective, but also a real bummer because yes, there are still a few PPC-only apps that I still have to use (Quicken, for instance... maybe I will have to finally upgrade, tho their upgrade isn&#039;t as good as the older versions, from my understanding).

I guess I&#039;ll need to survey to see what else I have that&#039;s still PPC-only.</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t realize Rosetta was going to go away. That&#8217;s understandable from Apple&#8217;s &#8220;moving forward&#8221; perspective, but also a real bummer because yes, there are still a few PPC-only apps that I still have to use (Quicken, for instance&#8230; maybe I will have to finally upgrade, tho their upgrade isn&#8217;t as good as the older versions, from my understanding).</p>
<p>I guess I&#8217;ll need to survey to see what else I have that&#8217;s still PPC-only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The private API thing by Rainer Brockerhoff</title>
		<link>http://brockerhoff.net/blog/2010/04/07/the-private-api-thing/comment-page-1/#comment-4231</link>
		<dc:creator>Rainer Brockerhoff</dc:creator>
		<pubDate>Mon, 07 Feb 2011 09:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/bb/viewtopic.php?p=2793#comment-4231</guid>
		<description>&lt;blockquote&gt;I want to know if apple will allow apps that have references to small APIs or header files that in turn reference cocoa, that a developer might have built for his own person use to do the same kind of tasks across many apps without coding all over again?&lt;/blockquote&gt;
Sure, that sort of thing is very common; it&#039;s done as either a private framework or a static library that you link into your executable. As long as those don&#039;t use private APIs themselves, you&#039;re in the clear.</description>
		<content:encoded><![CDATA[<blockquote><p>I want to know if apple will allow apps that have references to small APIs or header files that in turn reference cocoa, that a developer might have built for his own person use to do the same kind of tasks across many apps without coding all over again?</p></blockquote>
<p>Sure, that sort of thing is very common; it&#8217;s done as either a private framework or a static library that you link into your executable. As long as those don&#8217;t use private APIs themselves, you&#8217;re in the clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The private API thing by Neerav Kothari</title>
		<link>http://brockerhoff.net/blog/2010/04/07/the-private-api-thing/comment-page-1/#comment-4227</link>
		<dc:creator>Neerav Kothari</dc:creator>
		<pubDate>Mon, 07 Feb 2011 02:51:21 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/bb/viewtopic.php?p=2793#comment-4227</guid>
		<description>I want to know if apple will allow apps that have references to small APIs or header files that in turn reference cocoa, that a developer might have built for his own person use to do the same kind of tasks across many apps without coding all over again?

for example, an EngineeringMath.h file that lets me perform advance mathematical operations without coding for them all over again.</description>
		<content:encoded><![CDATA[<p>I want to know if apple will allow apps that have references to small APIs or header files that in turn reference cocoa, that a developer might have built for his own person use to do the same kind of tasks across many apps without coding all over again?</p>
<p>for example, an EngineeringMath.h file that lets me perform advance mathematical operations without coding for them all over again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mac App Store by Rainer Brockerhoff</title>
		<link>http://brockerhoff.net/blog/2010/10/21/the-mac-app-store/comment-page-1/#comment-2679</link>
		<dc:creator>Rainer Brockerhoff</dc:creator>
		<pubDate>Fri, 22 Oct 2010 01:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/blog/?p=2666#comment-2679</guid>
		<description>&lt;blockquote&gt;There could be a day when only apps bought through the app store are allowed onto your system.&lt;/blockquote&gt;
Well, I think that this will happen soon for certain types of users, as I said; I think it&#039;s unlikely that Apple will force this on all users, including so-called power users, unless they plan stop selling desktop Macs entirely.</description>
		<content:encoded><![CDATA[<blockquote><p>There could be a day when only apps bought through the app store are allowed onto your system.</p></blockquote>
<p>Well, I think that this will happen soon for certain types of users, as I said; I think it&#8217;s unlikely that Apple will force this on all users, including so-called power users, unless they plan stop selling desktop Macs entirely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mac App Store by Daniel</title>
		<link>http://brockerhoff.net/blog/2010/10/21/the-mac-app-store/comment-page-1/#comment-2677</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Thu, 21 Oct 2010 20:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://brockerhoff.net/blog/?p=2666#comment-2677</guid>
		<description>I think you need to add the words &quot;for now&quot;. As in &quot;the huge difference from the iOS App Store is that developers are perfectly free to write software outside the guidelines, and users are perfectly to install them &#039;for now&#039;&quot;. 

There could be a day when only apps bought through the app store are allowed onto your system.</description>
		<content:encoded><![CDATA[<p>I think you need to add the words &#8220;for now&#8221;. As in &#8220;the huge difference from the iOS App Store is that developers are perfectly free to write software outside the guidelines, and users are perfectly to install them &#8216;for now&#8217;&#8221;. </p>
<p>There could be a day when only apps bought through the app store are allowed onto your system.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

