<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Prototype 1</title>
	<link>http://1mancms.blogsome.com/2005/10/02/prototype-1/</link>
	<description>Forum and Think Tank for sharing ideas about a simple Content Management System</description>
	<pubDate>Fri, 27 Nov 2009 18:30:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Administrator</title>
		<link>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-12</link>
		<pubDate>Mon, 03 Oct 2005 20:38:37 +0100</pubDate>
		<guid>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-12</guid>
					<description>Regarding the assignment of templates to pages. I played around with a few ideas including the &amp;lt;?xml-stylesheet processing instruction. What I have settled for in prototype 2 is a simple element in each page called &amp;lt;template&amp;gt; which means the template can be changed easily by the user. There is a discussion of the problematic &lt;a href=&quot;http://www-128.ibm.com/developerworks/xml/library/x-wxxm2/index.html&quot; rel=&quot;nofollow&quot;&gt;on IBM developerWorx&lt;/a&gt;.</description>
		<content:encoded><![CDATA[	<p>Regarding the assignment of templates to pages. I played around with a few ideas including the &lt;?xml-stylesheet processing instruction. What I have settled for in prototype 2 is a simple element in each page called &lt;template&gt; which means the template can be changed easily by the user. There is a discussion of the problematic <a href="http://www-128.ibm.com/developerworks/xml/library/x-wxxm2/index.html" rel="nofollow">on IBM developerWorx</a>.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Administrator</title>
		<link>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-11</link>
		<pubDate>Mon, 03 Oct 2005 20:31:46 +0100</pubDate>
		<guid>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-11</guid>
					<description>The publishing process is serial like CityDesk. You work on your site (xml files) and then press &quot;Preview&quot; or &quot;Publish&quot; which builds the entire site and optionally publishes via FTP. Bear in mind we're talking about small 1-man sites here so a build should be less than a minute.

The GUI is still a challenge to be faced. Currently, my main interest lies in bringing a page together (prototype 2 is coming up!!!).

I could do with some suggestions and support on the GUI. I hate re-inventing the wheel and coding forms so I have been considering some automated solutions. One would be a DTD2FORM function which creates a HTML Form for editing the XML Document. Another possibility is &quot;Explorer Integration&quot;. A user would simply browse the file system, right click on a page or component and choose &quot;Edit&quot;. With desktop.ini and customized folders you can make the whole experience very user friendly. If there is gonna be any coding it's gotta be VBS/HTA because this runs automatically on any Windows machine.</description>
		<content:encoded><![CDATA[	<p>The publishing process is serial like CityDesk. You work on your site (xml files) and then press &#8220;Preview&#8221; or &#8220;Publish&#8221; which builds the entire site and optionally publishes via FTP. Bear in mind we&#8217;re talking about small 1-man sites here so a build should be less than a minute.</p>
	<p>The GUI is still a challenge to be faced. Currently, my main interest lies in bringing a page together (prototype 2 is coming up!!!).</p>
	<p>I could do with some suggestions and support on the GUI. I hate re-inventing the wheel and coding forms so I have been considering some automated solutions. One would be a DTD2FORM function which creates a HTML Form for editing the XML Document. Another possibility is &#8220;Explorer Integration&#8221;. A user would simply browse the file system, right click on a page or component and choose &#8220;Edit&#8221;. With desktop.ini and customized folders you can make the whole experience very user friendly. If there is gonna be any coding it&#8217;s gotta be VBS/HTA because this runs automatically on any Windows machine.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeremy</title>
		<link>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-10</link>
		<pubDate>Mon, 03 Oct 2005 14:50:38 +0100</pubDate>
		<guid>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-10</guid>
					<description>Wouldn't it be better if there was someway to dynamically crawl the pages of the site and there be some text file or naming convnention to specify the type of template a page came from so that when it came to regenerating pages this could be done by clicking one button?
</description>
		<content:encoded><![CDATA[	<p>Wouldn&#8217;t it be better if there was someway to dynamically crawl the pages of the site and there be some text file or naming convnention to specify the type of template a page came from so that when it came to regenerating pages this could be done by clicking one button?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeremy</title>
		<link>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-7</link>
		<pubDate>Mon, 03 Oct 2005 14:20:06 +0100</pubDate>
		<guid>http://1mancms.blogsome.com/2005/10/02/prototype-1/#comment-7</guid>
					<description>This all looks good by how do I as a user go about changing a page? There'll need to be some kind of a GUI in order for basic users to edit pages and then are those pages required to be regenerated? If the user edits a component would each page where that component is used need to be regenerated?</description>
		<content:encoded><![CDATA[	<p>This all looks good by how do I as a user go about changing a page? There&#8217;ll need to be some kind of a GUI in order for basic users to edit pages and then are those pages required to be regenerated? If the user edits a component would each page where that component is used need to be regenerated?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
