<?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: The pattern is not full</title>
	<atom:link href="http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/feed/" rel="self" type="application/rss+xml" />
	<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/</link>
	<description>Change thrives on me</description>
	<lastBuildDate>Tue, 07 Feb 2012 17:18:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: nakliyat</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6923</link>
		<dc:creator>nakliyat</dc:creator>
		<pubDate>Tue, 03 Nov 2009 23:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6923</guid>
		<description>The change detection is possible at the level of this Jetpack. On the first request you could ask bugzilla for all the fields. Then on subsequent requests you’d only need to ask for the delta. Once you detect a change you could ask for all fields again and determine what changed. The code for this wouldn’t be that hard and you could display the change in some fashion that replaces the current notification. However the next part is hard.</description>
		<content:encoded><![CDATA[<p>The change detection is possible at the level of this Jetpack. On the first request you could ask bugzilla for all the fields. Then on subsequent requests you’d only need to ask for the delta. Once you detect a change you could ask for all fields again and determine what changed. The code for this wouldn’t be that hard and you could display the change in some fashion that replaces the current notification. However the next part is hard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crowder</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6657</link>
		<dc:creator>crowder</dc:creator>
		<pubDate>Mon, 15 Jun 2009 17:24:25 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6657</guid>
		<description>I think automatically reloading could be disorienting (maybe do that as a pref?), but a reload link would be nice.  Also, it would be nice if my own posts didn&#039;t constitute a change, can you update the change time to the time of the load, if I&#039;m on a process_bug page?

Haven&#039;t looked at your code yet, too much of my own to worry about...</description>
		<content:encoded><![CDATA[<p>I think automatically reloading could be disorienting (maybe do that as a pref?), but a reload link would be nice.  Also, it would be nice if my own posts didn&#8217;t constitute a change, can you update the change time to the time of the load, if I&#8217;m on a process_bug page?</p>
<p>Haven&#8217;t looked at your code yet, too much of my own to worry about&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6656</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Mon, 15 Jun 2009 17:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6656</guid>
		<description>Fred: wow, I was certain that was a bug in Firefox from a while ago where you needed to set browser.cache.disk_cache_ssl to true for that to work.  I guess I can update the code to add a document.reload(); link in there or even try to automatically reload.

Thanks crowder!  Take a look at the source and let me know if you have any improvements.

Max: That would be sweet!  I&#039;d love to have some way to display the history.

Also, if you don&#039;t mind, I was getting some inconsistencies checking the ifModified header; any ideas on that?  That could have been some passing bug in my code but it seemed like bugzilla was not updating the ifModified flag so I always had to grab the XML.  (i commented out the ifModified section in the source http://userscripts.org/jetpacks/27/source)</description>
		<content:encoded><![CDATA[<p>Fred: wow, I was certain that was a bug in Firefox from a while ago where you needed to set browser.cache.disk_cache_ssl to true for that to work.  I guess I can update the code to add a document.reload(); link in there or even try to automatically reload.</p>
<p>Thanks crowder!  Take a look at the source and let me know if you have any improvements.</p>
<p>Max: That would be sweet!  I&#8217;d love to have some way to display the history.</p>
<p>Also, if you don&#8217;t mind, I was getting some inconsistencies checking the ifModified header; any ideas on that?  That could have been some passing bug in my code but it seemed like bugzilla was not updating the ifModified flag so I always had to grab the XML.  (i commented out the ifModified section in the source <a href="http://userscripts.org/jetpacks/27/source" rel="nofollow">http://userscripts.org/jetpacks/27/source</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Kanat-Alexander</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6651</link>
		<dc:creator>Max Kanat-Alexander</dc:creator>
		<pubDate>Sat, 13 Jun 2009 22:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6651</guid>
		<description>Pretty cool! FWIW, Bugzilla 3.4 will have a Bug.get_history XML-RPC API that will allow you to figure out what has changed.

-Max</description>
		<content:encoded><![CDATA[<p>Pretty cool! FWIW, Bugzilla 3.4 will have a Bug.get_history XML-RPC API that will allow you to figure out what has changed.</p>
<p>-Max</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crowder</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6649</link>
		<dc:creator>crowder</dc:creator>
		<pubDate>Fri, 12 Jun 2009 19:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6649</guid>
		<description>Nice hack.  This&#039;ll have me installing JetPack.</description>
		<content:encoded><![CDATA[<p>Nice hack.  This&#8217;ll have me installing JetPack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6645</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Fri, 12 Jun 2009 10:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6645</guid>
		<description>Uhm, just pressing CMD+R works for me in order to update the bug if it was changed in the mean time. The changes I made to the form fields will not go away.</description>
		<content:encoded><![CDATA[<p>Uhm, just pressing CMD+R works for me in order to update the bug if it was changed in the mean time. The changes I made to the form fields will not go away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6639</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Wed, 10 Jun 2009 20:20:06 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6639</guid>
		<description>Test ...

If this works, it works.</description>
		<content:encoded><![CDATA[<p>Test &#8230;</p>
<p>If this works, it works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6638</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Wed, 10 Jun 2009 18:19:55 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6638</guid>
		<description>Yeah copy/paste is about the only way to save it.  There is a firefox pref that is off by default which saves form fields on SSL connections.  With that turned on you can just reload, but right now it will lose your comment and anything else you changed.

The change detection is possible at the level of this Jetpack.  On the first request you could ask bugzilla for all the fields.  Then on subsequent requests you&#039;d only need to ask for the delta.  Once you detect a change you could ask for all fields again and determine what changed.  The code for this wouldn&#039;t be that hard and you could display the change in some fashion that replaces the current notification.  However the next part is hard.

Once you&#039;ve figured out what changed likely the next step would be to try to merge those changes so a reload isn&#039;t required.  And this is where it gets near impossible.  I tried for a while to insert new comments in order to allow myself to just post my comment but bugzilla holds some unnecessary state information in the form that makes this hard.  I suppose with some real investigation this would be possible, but I suspect very fragile.

PS: I think I fixed the error, the structured blogging plugin was broken.</description>
		<content:encoded><![CDATA[<p>Yeah copy/paste is about the only way to save it.  There is a firefox pref that is off by default which saves form fields on SSL connections.  With that turned on you can just reload, but right now it will lose your comment and anything else you changed.</p>
<p>The change detection is possible at the level of this Jetpack.  On the first request you could ask bugzilla for all the fields.  Then on subsequent requests you&#8217;d only need to ask for the delta.  Once you detect a change you could ask for all fields again and determine what changed.  The code for this wouldn&#8217;t be that hard and you could display the change in some fashion that replaces the current notification.  However the next part is hard.</p>
<p>Once you&#8217;ve figured out what changed likely the next step would be to try to merge those changes so a reload isn&#8217;t required.  And this is where it gets near impossible.  I tried for a while to insert new comments in order to allow myself to just post my comment but bugzilla holds some unnecessary state information in the form that makes this hard.  I suppose with some real investigation this would be possible, but I suspect very fragile.</p>
<p>PS: I think I fixed the error, the structured blogging plugin was broken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maciej Piechotka</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6637</link>
		<dc:creator>Maciej Piechotka</dc:creator>
		<pubDate>Wed, 10 Jun 2009 18:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6637</guid>
		<description>&gt; Change detection? Isn’t there a change summary, that also gets sent by e-mail to subscribers?

But it does not need to save a state on server. E-mail can be send by a hook.</description>
		<content:encoded><![CDATA[<p>&gt; Change detection? Isn’t there a change summary, that also gets sent by e-mail to subscribers?</p>
<p>But it does not need to save a state on server. E-mail can be send by a hook.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6636</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Wed, 10 Jun 2009 18:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6636</guid>
		<description>Well, what do you mean by &quot;save&quot;? Copy the comment to the clipboard, ok ...

Change detection? Isn&#039;t there a change summary, that also gets sent by e-mail to subscribers?

P.S.: The exact error is:

Fatal error: Call to undefined function add_submenu_page() in /home/.peeper/clarkbw/clarkbw.net/blog/wp-content/plugins/structuredblogging.php on line 322</description>
		<content:encoded><![CDATA[<p>Well, what do you mean by &#8220;save&#8221;? Copy the comment to the clipboard, ok &#8230;</p>
<p>Change detection? Isn&#8217;t there a change summary, that also gets sent by e-mail to subscribers?</p>
<p>P.S.: The exact error is:</p>
<p>Fatal error: Call to undefined function add_submenu_page() in /home/.peeper/clarkbw/clarkbw.net/blog/wp-content/plugins/structuredblogging.php on line 322</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6635</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Wed, 10 Jun 2009 18:00:53 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6635</guid>
		<description>Jens: I suppose that part could be clearer.  Usually you have to save your comment if you made one and anything else that you might have changed in the form.  It&#039;s possible to figure out what changed however it&#039;s a bit of work.  It might be easy to start out with some simple change detection wrt the CC list or new comments and work from there.

I&#039;ll try to look into the OpenID issue</description>
		<content:encoded><![CDATA[<p>Jens: I suppose that part could be clearer.  Usually you have to save your comment if you made one and anything else that you might have changed in the form.  It&#8217;s possible to figure out what changed however it&#8217;s a bit of work.  It might be easy to start out with some simple change detection wrt the CC list or new comments and work from there.</p>
<p>I&#8217;ll try to look into the OpenID issue</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6634</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Wed, 10 Jun 2009 13:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6634</guid>
		<description>Btw, entering a website (OpenID enabled!) gives strange errors for me.</description>
		<content:encoded><![CDATA[<p>Btw, entering a website (OpenID enabled!) gives strange errors for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6633</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Wed, 10 Jun 2009 13:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6633</guid>
		<description>&quot;Save and reload&quot;? Save what? And after the reload? How to know what has changed?</description>
		<content:encoded><![CDATA[<p>&#8220;Save and reload&#8221;? Save what? And after the reload? How to know what has changed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6627</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Mon, 08 Jun 2009 18:16:49 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6627</guid>
		<description>Andreas: haha, I know how you feel.  Each time I get one I think for a second &quot;Did I just break something?&quot;... &quot;Things collided!&quot;

Maciej: You could pull in the latest comments but it&#039;s extremely difficult to do much more.  If someone modified a flag on the bug that will trigger a mid-air collision as well and it would be really hard to work out the conflicting flag.  So really people have to reload no matter what.

I really wanted to do a lot more with this extension but Bugzilla is very old technology (web 0.2, not web 2.0).  If you take a look at the HTML code you&#039;ll see how broken it is, to work around it would take a substantial effort.</description>
		<content:encoded><![CDATA[<p>Andreas: haha, I know how you feel.  Each time I get one I think for a second &#8220;Did I just break something?&#8221;&#8230; &#8220;Things collided!&#8221;</p>
<p>Maciej: You could pull in the latest comments but it&#8217;s extremely difficult to do much more.  If someone modified a flag on the bug that will trigger a mid-air collision as well and it would be really hard to work out the conflicting flag.  So really people have to reload no matter what.</p>
<p>I really wanted to do a lot more with this extension but Bugzilla is very old technology (web 0.2, not web 2.0).  If you take a look at the HTML code you&#8217;ll see how broken it is, to work around it would take a substantial effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maciej Piechotka</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6626</link>
		<dc:creator>Maciej Piechotka</dc:creator>
		<pubDate>Mon, 08 Jun 2009 17:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6626</guid>
		<description>Wouldn&#039;t be better to update comments display by AJAX marking it on red or doing other visual effect?</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t be better to update comments display by AJAX marking it on red or doing other visual effect?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Nilsson</title>
		<link>http://clarkbw.net/blog/2009/06/08/the-pattern-is-not-full/comment-page-1/#comment-6625</link>
		<dc:creator>Andreas Nilsson</dc:creator>
		<pubDate>Mon, 08 Jun 2009 16:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/?p=668#comment-6625</guid>
		<description>Yay! This message always scared the hell out of me.
It could just as well have said: THE PLANE IS GOING DOWN, AND IT&#039;S YOUR FAULT!</description>
		<content:encoded><![CDATA[<p>Yay! This message always scared the hell out of me.<br />
It could just as well have said: THE PLANE IS GOING DOWN, AND IT&#8217;S YOUR FAULT!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.900 seconds -->

