<?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: Local file editing</title>
	<link>http://www.beyondproject.org/2006/04/24/local-file-editing/</link>
	<description>Genealogy anywhere.</description>
	<pubDate>Fri, 05 Sep 2008 20:58:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Ben</title>
		<link>http://www.beyondproject.org/2006/04/24/local-file-editing/#comment-81</link>
		<pubDate>Mon, 24 Apr 2006 20:40:25 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/04/24/local-file-editing/#comment-81</guid>
					<description>Good point.  And yes, I'm going to focus on the server/web client first, because trying to accomplish all of this all at once would be immensely daunting and nigh well impossible.  I do want to stay open to new ideas that may end up being useful (like this one), and if I'm at least aware of them from the beginning, I can make sure that early design decisions don't render those kinds of things impossible (or even inconvenient).

As I've mentioned before, communication with the server will go through an API (which all of the clients will use, I think, including the web client), which means other people can start work on desktop clients if they want.  The main thing at this point, now that the grand picture has come into focus, is to get a prototype up ASAP and start coding.  I'm inclined to start with the interface first (per &lt;a href=&quot;https://gettingreal.37signals.com/samples/37s-interface-first.pdf&quot; rel=&quot;nofollow&quot;&gt;37signals' advice&lt;/a&gt;), and we'll see where things go.  But first one last final to conquer...</description>
		<content:encoded><![CDATA[<p>Good point.  And yes, I&#8217;m going to focus on the server/web client first, because trying to accomplish all of this all at once would be immensely daunting and nigh well impossible.  I do want to stay open to new ideas that may end up being useful (like this one), and if I&#8217;m at least aware of them from the beginning, I can make sure that early design decisions don&#8217;t render those kinds of things impossible (or even inconvenient).</p>
<p>As I&#8217;ve mentioned before, communication with the server will go through an API (which all of the clients will use, I think, including the web client), which means other people can start work on desktop clients if they want.  The main thing at this point, now that the grand picture has come into focus, is to get a prototype up ASAP and start coding.  I&#8217;m inclined to start with the interface first (per <a href="https://gettingreal.37signals.com/samples/37s-interface-first.pdf" rel="nofollow">37signals&#8217; advice</a>), and we&#8217;ll see where things go.  But first one last final to conquer&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hilton</title>
		<link>http://www.beyondproject.org/2006/04/24/local-file-editing/#comment-79</link>
		<pubDate>Mon, 24 Apr 2006 19:53:37 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/04/24/local-file-editing/#comment-79</guid>
					<description>I really like this idea.  I just wanted to suggest that you at some point componentize Beyond and prioritize the components, because the project scope is getting expansive (server, web client, desktop clients on multiple OS's, etc.).  Based on what I've read, it looks like you'll have the most success with putting together a server/web client and considering expansion of this kernel later.</description>
		<content:encoded><![CDATA[<p>I really like this idea.  I just wanted to suggest that you at some point componentize Beyond and prioritize the components, because the project scope is getting expansive (server, web client, desktop clients on multiple OS&#8217;s, etc.).  Based on what I&#8217;ve read, it looks like you&#8217;ll have the most success with putting together a server/web client and considering expansion of this kernel later.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
