<?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: 5.0 Edit On Page</title>
	<atom:link href="http://www.d7ux.org/edit-on-page/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.d7ux.org/edit-on-page/</link>
	<description>making Drupal7 an amazing user experience</description>
	<lastBuildDate>Sun, 10 Jan 2010 11:19:49 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rachel</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1233</link>
		<dc:creator>Rachel</dc:creator>
		<pubDate>Fri, 31 Jul 2009 16:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1233</guid>
		<description>Not sure if &lt;a href=&quot;http://www.d7ux.org/appearance/comment-page-1/#comment-1231&quot; rel=&quot;nofollow&quot;&gt;this&lt;/a&gt; post should be transferred to or included on this page, but maybe it could be helpful for both.</description>
		<content:encoded><![CDATA[<p>Not sure if <a href="http://www.d7ux.org/appearance/comment-page-1/#comment-1231" rel="nofollow">this</a> post should be transferred to or included on this page, but maybe it could be helpful for both.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rachel</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1232</link>
		<dc:creator>Rachel</dc:creator>
		<pubDate>Fri, 31 Jul 2009 16:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1232</guid>
		<description>Not sure if &lt;a href=&quot;http://www.d7ux.org/appearance/comment-page-1/#comment-1230&quot; rel=&quot;nofollow&quot;&gt;this&lt;/a&gt; post should be transferred to or included on this page, but maybe it could be helpful for both.</description>
		<content:encoded><![CDATA[<p>Not sure if <a href="http://www.d7ux.org/appearance/comment-page-1/#comment-1230" rel="nofollow">this</a> post should be transferred to or included on this page, but maybe it could be helpful for both.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1092</link>
		<dc:creator>eric</dc:creator>
		<pubDate>Fri, 05 Jun 2009 09:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1092</guid>
		<description>I think folks are over-thinking this. 

What I see here is an interface for editing VISIBLE CONTENT. 

This interface does not PRECLUDE any interface for editing NON-VISIBLE CONTENT. 

(Mind, we haven&#039;t seen that interface yet; this would be a good time for Mark or Leisa to tell us how that fits into this scheme [or where else it fits, as the case may be].)

Audience is a problem in this forum: The vast majority of the time either Verity or Jeremy are going to be editing VISIBLE CONTENT. That&#039;s what happens on stable websites -- i.e., sites that are out of teh development and launch phases. 

We may have a hard time understanding that because many of us: 

a) aren&#039;t involved past launch phase; 

b) are involved, but only to develop or implement new features; 

c) are continually in a development mode on our sites.</description>
		<content:encoded><![CDATA[<p>I think folks are over-thinking this. </p>
<p>What I see here is an interface for editing VISIBLE CONTENT. </p>
<p>This interface does not PRECLUDE any interface for editing NON-VISIBLE CONTENT. </p>
<p>(Mind, we haven&#8217;t seen that interface yet; this would be a good time for Mark or Leisa to tell us how that fits into this scheme [or where else it fits, as the case may be].)</p>
<p>Audience is a problem in this forum: The vast majority of the time either Verity or Jeremy are going to be editing VISIBLE CONTENT. That&#8217;s what happens on stable websites &#8212; i.e., sites that are out of teh development and launch phases. </p>
<p>We may have a hard time understanding that because many of us: </p>
<p>a) aren&#8217;t involved past launch phase; </p>
<p>b) are involved, but only to develop or implement new features; </p>
<p>c) are continually in a development mode on our sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nico</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1091</link>
		<dc:creator>Nico</dc:creator>
		<pubDate>Fri, 05 Jun 2009 09:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1091</guid>
		<description>So one block could have three edit links;

edit node
edit view/module
edit block settings</description>
		<content:encoded><![CDATA[<p>So one block could have three edit links;</p>
<p>edit node<br />
edit view/module<br />
edit block settings</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1090</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Fri, 05 Jun 2009 08:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1090</guid>
		<description>There is the need for a selection of the content piece you want to edit, isn&#039;t it?

So if you have a block you can

a) edit the block settings
b) edit the content source of the block (node, view, module settings)

perhaps this could be done in a tabbed modal window where you select at the time of editing or you select before the editing.</description>
		<content:encoded><![CDATA[<p>There is the need for a selection of the content piece you want to edit, isn&#8217;t it?</p>
<p>So if you have a block you can</p>
<p>a) edit the block settings<br />
b) edit the content source of the block (node, view, module settings)</p>
<p>perhaps this could be done in a tabbed modal window where you select at the time of editing or you select before the editing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Boulton</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1089</link>
		<dc:creator>Mark Boulton</dc:creator>
		<pubDate>Fri, 05 Jun 2009 08:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1089</guid>
		<description>Yes, that&#039;s correct. If the content is a block, view, or any other &#039;type&#039; of content that isn&#039;t directy editable on-page, then when you click &#039;edit&#039; the system will fire up an overlay to edit that specific bit of content.</description>
		<content:encoded><![CDATA[<p>Yes, that&#8217;s correct. If the content is a block, view, or any other &#8216;type&#8217; of content that isn&#8217;t directy editable on-page, then when you click &#8216;edit&#8217; the system will fire up an overlay to edit that specific bit of content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nico</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1087</link>
		<dc:creator>Nico</dc:creator>
		<pubDate>Fri, 05 Jun 2009 07:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1087</guid>
		<description>If the content is in a block view, does the &quot;edit me&quot; link go to the view or the node?
In most of my websites a lot of the content comes from views.</description>
		<content:encoded><![CDATA[<p>If the content is in a block view, does the &#8220;edit me&#8221; link go to the view or the node?<br />
In most of my websites a lot of the content comes from views.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1079</link>
		<dc:creator>eric</dc:creator>
		<pubDate>Thu, 04 Jun 2009 17:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1079</guid>
		<description>Why would you need to be able to configure each field that way? 

Of course some fields (e.g., ones that aren&#039;t explicitly displayed) won&#039;t be editable in place. Are you talking about preventing additional fields from being edited? If so, what would be the use-case?</description>
		<content:encoded><![CDATA[<p>Why would you need to be able to configure each field that way? </p>
<p>Of course some fields (e.g., ones that aren&#8217;t explicitly displayed) won&#8217;t be editable in place. Are you talking about preventing additional fields from being edited? If so, what would be the use-case?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien McKenna</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1078</link>
		<dc:creator>Damien McKenna</dc:creator>
		<pubDate>Thu, 04 Jun 2009 16:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1078</guid>
		<description>Ok, I think this inline comment edit dialog is crap :) And it looks bad in Safari 3.  But I digress.

correction: ... that it would not be saying “I want to edit this node” but rather “this field in this node says it is editable, I would like to edit it”.</description>
		<content:encoded><![CDATA[<p>Ok, I think this inline comment edit dialog is crap <img src='http://www.d7ux.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  And it looks bad in Safari 3.  But I digress.</p>
<p>correction: &#8230; that it would not be saying “I want to edit this node” but rather “this field in this node says it is editable, I would like to edit it”.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien McKenna</title>
		<link>http://www.d7ux.org/edit-on-page/comment-page-1/#comment-1077</link>
		<dc:creator>Damien McKenna</dc:creator>
		<pubDate>Thu, 04 Jun 2009 16:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.d7ux.org/?p=130#comment-1077</guid>
		<description>I&#039;m going to say that each field would have to be configurable to indicate whether it was editable inline or not, and that it would be specifically saying &quot;I want to edit this node&quot; and more &quot;this field in this node says it is editable, I would like to edit it&quot;.</description>
		<content:encoded><![CDATA[<p>I&#8217;m going to say that each field would have to be configurable to indicate whether it was editable inline or not, and that it would be specifically saying &#8220;I want to edit this node&#8221; and more &#8220;this field in this node says it is editable, I would like to edit it&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
