<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Sources</title>
	<link>http://www.beyondproject.org/2006/05/01/sources/</link>
	<description>Genealogy anywhere.</description>
	<pubDate>Wed, 07 Jan 2009 02:02:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Ben</title>
		<link>http://www.beyondproject.org/2006/05/01/sources/#comment-142</link>
		<pubDate>Thu, 04 May 2006 19:09:13 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/05/01/sources/#comment-142</guid>
					<description>I think red squiggly lines might make the user think the data was misspelled, because it's used almost exclusively in the word processor/spellchecker domain.  As for the yellow warning triangle, I'd hesitate to make the &quot;wrongness&quot; of not having a source so strongly marked.  (That level probably ought to be reserved for real errors -- conflicts, impossibilities, etc.)  The more subtle psychological almost-but-not-quite-there feel to the greyed-out text seems to be not quite so grating.  But that's just me. :)  Anyway, I'll try to get some prototypes up soon so we can see if this grey-out idea actually works.</description>
		<content:encoded><![CDATA[<p>I think red squiggly lines might make the user think the data was misspelled, because it&#8217;s used almost exclusively in the word processor/spellchecker domain.  As for the yellow warning triangle, I&#8217;d hesitate to make the &#8220;wrongness&#8221; of not having a source so strongly marked.  (That level probably ought to be reserved for real errors &#8212; conflicts, impossibilities, etc.)  The more subtle psychological almost-but-not-quite-there feel to the greyed-out text seems to be not quite so grating.  But that&#8217;s just me. :)  Anyway, I&#8217;ll try to get some prototypes up soon so we can see if this grey-out idea actually works.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Logan Allred</title>
		<link>http://www.beyondproject.org/2006/05/01/sources/#comment-139</link>
		<pubDate>Thu, 04 May 2006 05:27:35 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/05/01/sources/#comment-139</guid>
					<description>Another thought is to use the red squiggly lines like you have when a word is misspelled (though probably a bit more subdued in color and brightness). I like  having that notion that something is &quot;wrong&quot; when there aren't sources, and that will lead people to fix it. Another might be to badge it with a warning yellow triangle, or things like that.</description>
		<content:encoded><![CDATA[<p>Another thought is to use the red squiggly lines like you have when a word is misspelled (though probably a bit more subdued in color and brightness). I like  having that notion that something is &#8220;wrong&#8221; when there aren&#8217;t sources, and that will lead people to fix it. Another might be to badge it with a warning yellow triangle, or things like that.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
<div id='error'>
			<p class='wpdberror'><strong>WordPress database error:</strong> [Table './blanksl1_beyond/wp_bdprt_targets' is marked as crashed and should be repaired]<br />
			<code>SELECT target_ident, last_updated, target_page_url, taregt_page_title FROM wp_bdprt_targets WHERE target_page_url='/index.php' </code></p>
			</div><div id='error'>
			<p class='wpdberror'><strong>WordPress database error:</strong> [Table './blanksl1_beyond/wp_bdprt_targets' is marked as crashed and should be repaired]<br />
			<code>INSERT INTO wp_bdprt_targets (target_page_url, taregt_page_title, last_updated) VALUES ('/index.php', 'FEED Sources', '1231293742')</code></p>
			</div>