<?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 on: Introducing Clickframes!</title>
	<atom:link href="http://info.rmatics.org/2009/07/06/introducing-clickframes/feed/" rel="self" type="application/rss+xml" />
	<link>http://info.rmatics.org/2009/07/06/introducing-clickframes/</link>
	<description>Healthcare, Informatics, Software - in the real world.</description>
	<lastBuildDate>Wed, 07 Jul 2010 21:30:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: William Crawford</title>
		<link>http://info.rmatics.org/2009/07/06/introducing-clickframes/comment-page-1/#comment-2080</link>
		<dc:creator>William Crawford</dc:creator>
		<pubDate>Tue, 14 Jul 2009 13:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://info.rmatics.org/?p=338#comment-2080</guid>
		<description>Hi Naaka,

Actually, we&#039;ve thought about doing just that. We&#039;re starting with XML because that lets us get the model just right, and with modern editors and XML Schema we can get a lot of the cross-checking done. I remember the old struts.xml - I hated it, mostly because you had to maintain knowledge, by hand, in more than one place. 

We&#039;ve started building a very simple authoring tool for managing an AppSpec through a GUI, and will release it in the next month or so (it&#039;s a 20% project). The first version will be pretty simple, but we&#039;ll roll in some drag and drop graphical editing in the future.

We&#039;d love to hear any additional comments you may have - join the mailing list!

Will</description>
		<content:encoded><![CDATA[<p>Hi Naaka,</p>
<p>Actually, we&#8217;ve thought about doing just that. We&#8217;re starting with XML because that lets us get the model just right, and with modern editors and XML Schema we can get a lot of the cross-checking done. I remember the old struts.xml &#8211; I hated it, mostly because you had to maintain knowledge, by hand, in more than one place. </p>
<p>We&#8217;ve started building a very simple authoring tool for managing an AppSpec through a GUI, and will release it in the next month or so (it&#8217;s a 20% project). The first version will be pretty simple, but we&#8217;ll roll in some drag and drop graphical editing in the future.</p>
<p>We&#8217;d love to hear any additional comments you may have &#8211; join the mailing list!</p>
<p>Will</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: naaka</title>
		<link>http://info.rmatics.org/2009/07/06/introducing-clickframes/comment-page-1/#comment-2073</link>
		<dc:creator>naaka</dc:creator>
		<pubDate>Tue, 14 Jul 2009 09:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://info.rmatics.org/?p=338#comment-2073</guid>
		<description>Hi,
this is one of the best idea i&#039;ve seen in the last 2 years!

One suggestion.

Xml is overused, it&#039;s flat structure is not targeted to describe a graph, and become rapidly a mess (does anyone remember the old struts.xml).

So why not do the reverse ?

Instead of generating a live specification (i.e. the CLIPs) from the xml, give the possibility to build and edit live the specification (the CLIPs), and to export an xml from it.


What do you think ?</description>
		<content:encoded><![CDATA[<p>Hi,<br />
this is one of the best idea i&#8217;ve seen in the last 2 years!</p>
<p>One suggestion.</p>
<p>Xml is overused, it&#8217;s flat structure is not targeted to describe a graph, and become rapidly a mess (does anyone remember the old struts.xml).</p>
<p>So why not do the reverse ?</p>
<p>Instead of generating a live specification (i.e. the CLIPs) from the xml, give the possibility to build and edit live the specification (the CLIPs), and to export an xml from it.</p>
<p>What do you think ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
