<?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 Mr. xcHong	</title>
	<atom:link href="https://xc-h.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://xc-h.com</link>
	<description>simple ideas change the world</description>
	<lastBuildDate>Fri, 29 Sep 2017 02:29:07 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.1</generator>
	<item>
		<title>
		Comment on Full Screen Clock Update 3 by XH		</title>
		<link>https://xc-h.com/2013/03/21/full-screen-clock-update-3/#comment-1531</link>

		<dc:creator><![CDATA[XH]]></dc:creator>
		<pubDate>Fri, 29 Sep 2017 02:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://xc-h.net/?p=1010#comment-1531</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://xc-h.com/2013/03/21/full-screen-clock-update-3/#comment-1529&quot;&gt;Mike&lt;/a&gt;.

Also I fixed the broken links. Didn&#039;t realize I took the old site down, oops.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://xc-h.com/2013/03/21/full-screen-clock-update-3/#comment-1529">Mike</a>.</p>
<p>Also I fixed the broken links. Didn&#8217;t realize I took the old site down, oops.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Full Screen Clock Update 3 by XH		</title>
		<link>https://xc-h.com/2013/03/21/full-screen-clock-update-3/#comment-1530</link>

		<dc:creator><![CDATA[XH]]></dc:creator>
		<pubDate>Fri, 29 Sep 2017 02:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://xc-h.net/?p=1010#comment-1530</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://xc-h.com/2013/03/21/full-screen-clock-update-3/#comment-1529&quot;&gt;Mike&lt;/a&gt;.

I think it&#039;s called &lt;code&gt;Orbitron&lt;/code&gt;. Looks really cool.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://xc-h.com/2013/03/21/full-screen-clock-update-3/#comment-1529">Mike</a>.</p>
<p>I think it&#8217;s called <code>Orbitron</code>. Looks really cool.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Full Screen Clock Update 3 by Mike		</title>
		<link>https://xc-h.com/2013/03/21/full-screen-clock-update-3/#comment-1529</link>

		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Tue, 26 Sep 2017 15:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://xc-h.net/?p=1010#comment-1529</guid>

					<description><![CDATA[What Fonts are you using?]]></description>
			<content:encoded><![CDATA[<p>What Fonts are you using?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DIY Arm Rest with a Mouse Pad by XH		</title>
		<link>https://xc-h.com/2016/01/24/diy-arm-rest-with-a-mouse-pad/#comment-1528</link>

		<dc:creator><![CDATA[XH]]></dc:creator>
		<pubDate>Tue, 09 May 2017 14:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://xc-h.net/?p=1288#comment-1528</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://xc-h.com/2016/01/24/diy-arm-rest-with-a-mouse-pad/#comment-1527&quot;&gt;louise&lt;/a&gt;.

yeah what I didn&#039;t show in the photos is I attached two velcro straps to the bottom and use them to strap the foam board to the chair arm.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://xc-h.com/2016/01/24/diy-arm-rest-with-a-mouse-pad/#comment-1527">louise</a>.</p>
<p>yeah what I didn&#8217;t show in the photos is I attached two velcro straps to the bottom and use them to strap the foam board to the chair arm.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DIY Arm Rest with a Mouse Pad by louise		</title>
		<link>https://xc-h.com/2016/01/24/diy-arm-rest-with-a-mouse-pad/#comment-1527</link>

		<dc:creator><![CDATA[louise]]></dc:creator>
		<pubDate>Tue, 09 May 2017 06:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://xc-h.net/?p=1288#comment-1527</guid>

					<description><![CDATA[is this mounted to the chair arm ?]]></description>
			<content:encoded><![CDATA[<p>is this mounted to the chair arm ?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Material Design Lite for Meteor by XH		</title>
		<link>https://xc-h.com/portfolio/material-design-lite-for-meteor/#comment-1526</link>

		<dc:creator><![CDATA[XH]]></dc:creator>
		<pubDate>Wed, 18 Jan 2017 18:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://xc-h.net/?post_type=jetpack-portfolio&#038;p=1315#comment-1526</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://xc-h.com/portfolio/material-design-lite-for-meteor/#comment-1525&quot;&gt;Shilpa&lt;/a&gt;.

I&#039;m testing out MDC. Using the core distribution files (js and css) should be easy as the developers say.

However, using source files/modules seems to be really complicated with Meteor.

MDC is using Webpack with custom import paths so its modules can import with &lt;code&gt;@material/component/component.js&lt;/code&gt; and &lt;code&gt;@material/component/component.sass&lt;/code&gt;. This causes problems with Meteor. For example, suppose we are using MDC as a npm package. Importing &lt;code&gt;/node_modules/@material/checkbox/index.js&lt;/code&gt; in file &lt;code&gt;/client/main.js&lt;/code&gt; would then import &lt;code&gt;@material/animation&lt;/code&gt;, which gets resolved as &lt;code&gt;/client/@material/animation&lt;/code&gt;, which doesn&#039;t exist. I tried symlinks and that doesn&#039;t help since &lt;code&gt;@material/component&lt;/code&gt; will always be treated as relative path, unless there is custom import path configurations. I don&#039;t think Meteor has that, nor does &lt;code&gt;fourseven:scss&lt;/code&gt; have that, either. It&#039;s looking pretty bad. I think the &lt;code&gt;webpack:webpack&lt;/code&gt; Meteor package is no longer supported, while I have very little experience with Webpack so I don&#039;t know if it&#039;s gonna work.

Now that&#039;s all about trying to make the Meteor framework work with what MDC has, without touching MDC code as that would increase the cost of maintenance. However as it seems very difficult on the Meteor side, maybe I could try a global find &#038; replace to make all &lt;code&gt;@material/&lt;/code&gt; into &lt;code&gt;{zodiase:mdc-assets}&lt;/code&gt; for example. That way I think at least it would work. But on the other hand, that would require all the component assets to be in one single package. I think MDC eventually is going to break into smaller packages, one for each component, not sure how that&#039;s gonna work.

Let me know your thoughts.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://xc-h.com/portfolio/material-design-lite-for-meteor/#comment-1525">Shilpa</a>.</p>
<p>I&#8217;m testing out MDC. Using the core distribution files (js and css) should be easy as the developers say.</p>
<p>However, using source files/modules seems to be really complicated with Meteor.</p>
<p>MDC is using Webpack with custom import paths so its modules can import with <code>@material/component/component.js</code> and <code>@material/component/component.sass</code>. This causes problems with Meteor. For example, suppose we are using MDC as a npm package. Importing <code>/node_modules/@material/checkbox/index.js</code> in file <code>/client/main.js</code> would then import <code>@material/animation</code>, which gets resolved as <code>/client/@material/animation</code>, which doesn&#8217;t exist. I tried symlinks and that doesn&#8217;t help since <code>@material/component</code> will always be treated as relative path, unless there is custom import path configurations. I don&#8217;t think Meteor has that, nor does <code>fourseven:scss</code> have that, either. It&#8217;s looking pretty bad. I think the <code>webpack:webpack</code> Meteor package is no longer supported, while I have very little experience with Webpack so I don&#8217;t know if it&#8217;s gonna work.</p>
<p>Now that&#8217;s all about trying to make the Meteor framework work with what MDC has, without touching MDC code as that would increase the cost of maintenance. However as it seems very difficult on the Meteor side, maybe I could try a global find &amp; replace to make all <code>@material/</code> into <code>{zodiase:mdc-assets}</code> for example. That way I think at least it would work. But on the other hand, that would require all the component assets to be in one single package. I think MDC eventually is going to break into smaller packages, one for each component, not sure how that&#8217;s gonna work.</p>
<p>Let me know your thoughts.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Material Design Lite for Meteor by Shilpa		</title>
		<link>https://xc-h.com/portfolio/material-design-lite-for-meteor/#comment-1525</link>

		<dc:creator><![CDATA[Shilpa]]></dc:creator>
		<pubDate>Mon, 16 Jan 2017 12:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://xc-h.net/?post_type=jetpack-portfolio&#038;p=1315#comment-1525</guid>

					<description><![CDATA[Hi Xingchen,

Given that Material Design Lite is now in limited support, with development having moved to the Material Components for the web repository, is there any plan to adapt or create a new package for MDC-web and would that be available anytime soon?

- SK]]></description>
			<content:encoded><![CDATA[<p>Hi Xingchen,</p>
<p>Given that Material Design Lite is now in limited support, with development having moved to the Material Components for the web repository, is there any plan to adapt or create a new package for MDC-web and would that be available anytime soon?</p>
<p>&#8211; SK</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
