<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Userscripts.org &#8230; Opensource!</title>
	<atom:link href="http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/feed/" rel="self" type="application/rss+xml" />
	<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/</link>
	<description>lukewarmtapioca.com</description>
	<lastBuildDate>Thu, 11 Mar 2010 18:27:42 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Vintage Tractors for Sale</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-157</link>
		<dc:creator>Vintage Tractors for Sale</dc:creator>
		<pubDate>Thu, 07 May 2009 06:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-157</guid>
		<description>Did you design this template?</description>
		<content:encoded><![CDATA[<p>Did you design this template?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lior</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-26</link>
		<dc:creator>Lior</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-26</guid>
		<description>A quick question: you write &quot;We got a bit excited and made the common mistake of using Ajax in a few places where it simply doesn’t belong. A perfect example of this was the login system.&quot;
May I ask why was it a mistake? What did you find wrong in using AJAX? Was it hard to maintain? Was it incompatible? Did it alienate users? I want to understand this design decision, and it escapes me...
Thanks.</description>
		<content:encoded><![CDATA[<p>A quick question: you write &quot;We got a bit excited and made the common mistake of using Ajax in a few places where it simply doesn’t belong. A perfect example of this was the login system.&quot;<br />
May I ask why was it a mistake? What did you find wrong in using AJAX? Was it hard to maintain? Was it incompatible? Did it alienate users? I want to understand this design decision, and it escapes me&#8230;<br />
Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan Sundström</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-27</link>
		<dc:creator>Johan Sundström</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-27</guid>
		<description>Congratulations on getting to the public release stage! :-)

Lior: Perhaps most pressingly, the login widget would not interact well with Firefox&#039;s password manager, forcing all to use it manually (or with custom crafted user scripts...), even if they would have preferred using their browser&#039;s aids there.</description>
		<content:encoded><![CDATA[<p>Congratulations on getting to the public release stage! <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Lior: Perhaps most pressingly, the login widget would not interact well with Firefox&#8217;s password manager, forcing all to use it manually (or with custom crafted user scripts&#8230;), even if they would have preferred using their browser&#8217;s aids there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Britt</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-28</link>
		<dc:creator>Britt</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-28</guid>
		<description>Loir,

AJAX, like anything has places where it makes sense and areas where it doesn&#039;t. There have been several articles about the caveats of the overuse of AJAX (http://aranea.zuavra.net/index.php/30/ for example).

In userscripts specifically, several areas were broken:
 * As Johan mentioned, the login system broke browser&#039;s password managers.
 * Searching for a script is one of the primary way&#039;s to find what you need, and the &quot;Live Search&quot; on the front of the page provided a cramped space for much needed information about your results.
 * While not AJAX specifically, we tended to overuse javascript effects to show/hide elements within pages when there were often more simple ways to get the info to the users.

So will we still be using AJAX for easily updating of content within the site? Yes. It&#039;s just important to make sure you have a glove that fits.</description>
		<content:encoded><![CDATA[<p>Loir,</p>
<p>AJAX, like anything has places where it makes sense and areas where it doesn&#8217;t. There have been several articles about the caveats of the overuse of AJAX (<a href="http://aranea.zuavra.net/index.php/30/" rel="nofollow">http://aranea.zuavra.net/index.php/30/</a> for example).</p>
<p>In userscripts specifically, several areas were broken:<br />
 * As Johan mentioned, the login system broke browser&#8217;s password managers.<br />
 * Searching for a script is one of the primary way&#8217;s to find what you need, and the &quot;Live Search&quot; on the front of the page provided a cramped space for much needed information about your results.<br />
 * While not AJAX specifically, we tended to overuse javascript effects to show/hide elements within pages when there were often more simple ways to get the info to the users.</p>
<p>So will we still be using AJAX for easily updating of content within the site? Yes. It&#8217;s just important to make sure you have a glove that fits.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Irish</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-29</link>
		<dc:creator>Paul Irish</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-29</guid>
		<description>This is great news! thank you!</description>
		<content:encoded><![CDATA[<p>This is great news! thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederick</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-30</link>
		<dc:creator>Frederick</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-30</guid>
		<description>Here&#039;s a design prototype I&#039;m kind of working on. Take a look and tell me what you think. http://filer.brnm.se/i/userscripts.002.png</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a design prototype I&#8217;m kind of working on. Take a look and tell me what you think. <a href="http://filer.brnm.se/i/userscripts.002.png" rel="nofollow">http://filer.brnm.se/i/userscripts.002.png</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan Sundström</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-31</link>
		<dc:creator>Johan Sundström</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-31</guid>
		<description>While my opinion is just that of an innocent bystander, I&#039;m strongly in favour of it, Frederick. A clean and not very busy look. It&#039;s probably worth doing a few of the more complicated views with data in them before it&#039;s possible to really deem whether it would work better than the present layout, though.</description>
		<content:encoded><![CDATA[<p>While my opinion is just that of an innocent bystander, I&#8217;m strongly in favour of it, Frederick. A clean and not very busy look. It&#8217;s probably worth doing a few of the more complicated views with data in them before it&#8217;s possible to really deem whether it would work better than the present layout, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Britt</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-32</link>
		<dc:creator>Britt</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-32</guid>
		<description>Frederick, I like the style very much, especially the logo. As soon as you posted that I went to the wiki to create a page for various prototypes and contributions.

If we come up with a variety of styles and ideas, we can have community discussion on how best to implement the new design.

My first comment would be on removing some of the unused space at the top, as to not hide page content.

Could you prototype how you&#039;d envision content below the header, for example a script&#039;s page?  Thanks for your already great contribution!</description>
		<content:encoded><![CDATA[<p>Frederick, I like the style very much, especially the logo. As soon as you posted that I went to the wiki to create a page for various prototypes and contributions.</p>
<p>If we come up with a variety of styles and ideas, we can have community discussion on how best to implement the new design.</p>
<p>My first comment would be on removing some of the unused space at the top, as to not hide page content.</p>
<p>Could you prototype how you&#8217;d envision content below the header, for example a script&#8217;s page?  Thanks for your already great contribution!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederick</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-33</link>
		<dc:creator>Frederick</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-33</guid>
		<description>Thanks for your opinion guys, that positive and constructive feedback is encouraging. I&#039;ll see how I can develop this further, and I&#039;ll continue coming here and on the wiki.</description>
		<content:encoded><![CDATA[<p>Thanks for your opinion guys, that positive and constructive feedback is encouraging. I&#8217;ll see how I can develop this further, and I&#8217;ll continue coming here and on the wiki.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tractor</title>
		<link>http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource/#comment-34</link>
		<dc:creator>tractor</dc:creator>
		<pubDate>Wed, 03 Jan 2007 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://lukewarmtapioca.com/2007/01/03/userscripts-org-opensource#comment-34</guid>
		<description>A wild and random idea:

 * throw away the whole code base
 * setup a trac [http://trac.edgewall.org/] with user registration and subversion integration
 * write a site from scratch for categorization, scripts voting and such things

The basic idea is that every registered user can commit to the SVN repo (in its own directory, just like CPAN) and has write access to the wiki.

Every user can read the whole thing and report bugs and improvements.

Benefits:
 * Use a mature and stable product for &quot;commodity&quot; things like storing code (subversion), writing a simple page for each script (trac embedded wiki) report bugs (trac issue tracker)
 * Focus on adding new value on top of that  like tagging scripts, writing a good search engine (in a semantic way) for the scripts, providing alerts and RSS feeds, etc.

my 2c</description>
		<content:encoded><![CDATA[<p>A wild and random idea:</p>
<p> * throw away the whole code base<br />
 * setup a trac [http://trac.edgewall.org/] with user registration and subversion integration<br />
 * write a site from scratch for categorization, scripts voting and such things</p>
<p>The basic idea is that every registered user can commit to the SVN repo (in its own directory, just like CPAN) and has write access to the wiki.</p>
<p>Every user can read the whole thing and report bugs and improvements.</p>
<p>Benefits:<br />
 * Use a mature and stable product for &quot;commodity&quot; things like storing code (subversion), writing a simple page for each script (trac embedded wiki) report bugs (trac issue tracker)<br />
 * Focus on adding new value on top of that  like tagging scripts, writing a good search engine (in a semantic way) for the scripts, providing alerts and RSS feeds, etc.</p>
<p>my 2c</p>
]]></content:encoded>
	</item>
</channel>
</rss>
