<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: All your permissions are belong to us</title>
	<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/</link>
	<description>Just another GNOME Blogs weblog</description>
	<pubDate>Sat, 30 Aug 2008 16:56:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Bastien Nocera</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-96</link>
		<dc:creator>Bastien Nocera</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-96</guid>
		<description>The whole of the dialogue is showing the current state of the permissions for that file...&lt;p/&gt;Except the "chmod" part, which launches a command for which you wouldn't see the output, or whether it's worked at all. &lt;p/&gt;Also, when would it be applied? There's no button to apply it, and changing it when unfocusing the text widget looks a recipe for disaster.&lt;p/&gt;Being able to run arbitrary commands on the file itself, and the subdirectories would be a better idea, IMO.</description>
		<content:encoded><![CDATA[<p>The whole of the dialogue is showing the current state of the permissions for that file&#8230;
<p />Except the &#8220;chmod&#8221; part, which launches a command for which you wouldn&#8217;t see the output, or whether it&#8217;s worked at all.
<p />Also, when would it be applied? There&#8217;s no button to apply it, and changing it when unfocusing the text widget looks a recipe for disaster.
<p />Being able to run arbitrary commands on the file itself, and the subdirectories would be a better idea, IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Betts</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-97</link>
		<dc:creator>Paul Betts</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-97</guid>
		<description>Just a thought, but I suspect the word "recursive" may have most non-CS people shaking their heads. Maybe "Apply changes to everything in this folder?", while somewhat less clear to you and me, would be infinitely more clear to someone who didn't understand recursion</description>
		<content:encoded><![CDATA[<p>Just a thought, but I suspect the word &#8220;recursive&#8221; may have most non-CS people shaking their heads. Maybe &#8220;Apply changes to everything in this folder?&#8221;, while somewhat less clear to you and me, would be infinitely more clear to someone who didn&#8217;t understand recursion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Florin</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-98</link>
		<dc:creator>Florin</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-98</guid>
		<description>The recursive application lacks "discoverability". I certainly don't want to poke around with something that dangerous (I can lock myself out of my files) which has "instant apply", just to find out how to do it recursively.&lt;p/&gt;And what about the "ooops" button on you "prompt for recursivitiy" dialog? You acknowledge that the user cannot reverse easily, but you don't offer a easy way out.&lt;p/&gt;I suggest highlighting the original values with some special color/outline, so users can feel safer in changing the permissions.</description>
		<content:encoded><![CDATA[<p>The recursive application lacks &#8220;discoverability&#8221;. I certainly don&#8217;t want to poke around with something that dangerous (I can lock myself out of my files) which has &#8220;instant apply&#8221;, just to find out how to do it recursively.
<p />And what about the &#8220;ooops&#8221; button on you &#8220;prompt for recursivitiy&#8221; dialog? You acknowledge that the user cannot reverse easily, but you don&#8217;t offer a easy way out.
<p />I suggest highlighting the original values with some special color/outline, so users can feel safer in changing the permissions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Neumair</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-99</link>
		<dc:creator>Christian Neumair</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-99</guid>
		<description>Bastien:&lt;p/&gt;&gt; The whole of the dialogue is showing the current state of the permissions for that file...&lt;br/&gt;&gt; Except the "chmod" part, which launches a command for which you wouldn't see the output, or whether it's worked at all. &lt;p/&gt;The "chmod" part doesn't launch a command. We parse the string using code from the GNU coreutils, convert it into a GnomeVFSFilePermissions mask and apply it ourselves. How else could I have stated that this also works for remote shares? You will at least be notified that it is applying your changes with a watch cursor, and you will be notified by an error dialog about failed changes.&lt;p/&gt;&gt; Also, when would it be applied? There's no button to apply it, and changing it when unfocusing the text widget looks a recipe for disaster.&lt;p/&gt;You have to press enter when the entry is focused. That's IMHO how people who use shells denote "I'm fine with my command, now run it!".&lt;p/&gt;Paul:&lt;p/&gt;&gt; Just a thought, but I suspect the word "recursive" may have most non-CS people shaking their heads.&lt;p/&gt;Did you note that I'm presenting two different dialogs, depending on whether the entry resembling chmod was used or not?</description>
		<content:encoded><![CDATA[<p>Bastien:
<p />> The whole of the dialogue is showing the current state of the permissions for that file&#8230;<br />> Except the &#8220;chmod&#8221; part, which launches a command for which you wouldn&#8217;t see the output, or whether it&#8217;s worked at all.
<p />The &#8220;chmod&#8221; part doesn&#8217;t launch a command. We parse the string using code from the GNU coreutils, convert it into a GnomeVFSFilePermissions mask and apply it ourselves. How else could I have stated that this also works for remote shares? You will at least be notified that it is applying your changes with a watch cursor, and you will be notified by an error dialog about failed changes.
<p />> Also, when would it be applied? There&#8217;s no button to apply it, and changing it when unfocusing the text widget looks a recipe for disaster.
<p />You have to press enter when the entry is focused. That&#8217;s IMHO how people who use shells denote &#8220;I&#8217;m fine with my command, now run it!&#8221;.
<p />Paul:
<p />> Just a thought, but I suspect the word &#8220;recursive&#8221; may have most non-CS people shaking their heads.
<p />Did you note that I&#8217;m presenting two different dialogs, depending on whether the entry resembling chmod was used or not?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Neumair</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-100</link>
		<dc:creator>Christian Neumair</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-100</guid>
		<description>Florin:&lt;p/&gt;&gt; The recursive application lacks "discoverability".&lt;p/&gt;Maybe you could explain why?&lt;p/&gt;&gt; I certainly don't want to poke around with something that&lt;br/&gt;&gt; dangerous (I can lock myself out of my files) which has &lt;br/&gt;&gt; "instant apply", just to find out how to do it recursively.&lt;p/&gt;Well, you can't lock yourself out of your files, at least not using the drop down entries. The "None" entry is not available in user's "Access" dropdown.&lt;p/&gt;&gt; And what about the "ooops" button on you "prompt for&lt;br/&gt;&gt; recursivitiy" dialog? You acknowledge that the user cannot&lt;br/&gt;&gt; reverse easily, but you don't offer a easy way out.&lt;p/&gt;I assume that the user wants to change permissions of the folder, so I can assume that he wants Nautilus to modify at least the permissions of the folder itself.&lt;p/&gt;&gt; I suggest highlighting the original values with some&lt;br/&gt;&gt; special color/outline, so users can feel safer in changing&lt;br/&gt;&gt; the permissions.&lt;p/&gt;What original values? The original values are preselected in the drop-downs.</description>
		<content:encoded><![CDATA[<p>Florin:
<p />> The recursive application lacks &#8220;discoverability&#8221;.
<p />Maybe you could explain why?
<p />> I certainly don&#8217;t want to poke around with something that<br />> dangerous (I can lock myself out of my files) which has <br />> &#8220;instant apply&#8221;, just to find out how to do it recursively.
<p />Well, you can&#8217;t lock yourself out of your files, at least not using the drop down entries. The &#8220;None&#8221; entry is not available in user&#8217;s &#8220;Access&#8221; dropdown.
<p />> And what about the &#8220;ooops&#8221; button on you &#8220;prompt for<br />> recursivitiy&#8221; dialog? You acknowledge that the user cannot<br />> reverse easily, but you don&#8217;t offer a easy way out.
<p />I assume that the user wants to change permissions of the folder, so I can assume that he wants Nautilus to modify at least the permissions of the folder itself.
<p />> I suggest highlighting the original values with some<br />> special color/outline, so users can feel safer in changing<br />> the permissions.
<p />What original values? The original values are preselected in the drop-downs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emmanuel</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-101</link>
		<dc:creator>emmanuel</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-101</guid>
		<description>i think you've pretty much nailed it. very good!&lt;p/&gt;just two comments:&lt;br/&gt;1. i would change the label "chmod" to "chmod (enter to apply)"&lt;br/&gt;2. i woulnd't have two different dialogs to ask if the user wants recursive or not recursive action. i would only keep the "simple" version.&lt;br/&gt;3. i'm not certain separating "execute" rights for owner/group/other is needed, but why not. some might object because of clutter but ok it gives power without forcing going to the command-line. and avoids a regression from gnome 2.12.&lt;p/&gt;this version is unbelievably better than you version #2. i didn't think it's possible to make a so good one.</description>
		<content:encoded><![CDATA[<p>i think you&#8217;ve pretty much nailed it. very good!
<p />just two comments:<br />1. i would change the label &#8220;chmod&#8221; to &#8220;chmod (enter to apply)&#8221;<br />2. i woulnd&#8217;t have two different dialogs to ask if the user wants recursive or not recursive action. i would only keep the &#8220;simple&#8221; version.<br />3. i&#8217;m not certain separating &#8220;execute&#8221; rights for owner/group/other is needed, but why not. some might object because of clutter but ok it gives power without forcing going to the command-line. and avoids a regression from gnome 2.12.
<p />this version is unbelievably better than you version #2. i didn&#8217;t think it&#8217;s possible to make a so good one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emmanuel</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-102</link>
		<dc:creator>emmanuel</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-102</guid>
		<description>btw by the "simple" version i meant the version for non-UNIX experts. the one that doesn't mention "recursive". experts will understand both versions. so there's no need for an expert version IMHO.</description>
		<content:encoded><![CDATA[<p>btw by the &#8220;simple&#8221; version i meant the version for non-UNIX experts. the one that doesn&#8217;t mention &#8220;recursive&#8221;. experts will understand both versions. so there&#8217;s no need for an expert version IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-103</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-103</guid>
		<description>Some distributions use seperate groups for each user. How would the group drop-down work in a system with 100 or 1000 groups? Is there a threshold where the drop-down becomes a text-field?&lt;br/&gt;I also agree that looking at the dialog doesn't clue you in on how to change permissions recursively, I recon a user looking to do this can do a fair amount of looking around before realising it's worked into the close button (I don't believe users read manuals or help files generally). At the same time, if you're not looking to recursively change permissions, you would still get that question each time you want to change permission for a file.&lt;br/&gt;These changes are looking nice otherways.</description>
		<content:encoded><![CDATA[<p>Some distributions use seperate groups for each user. How would the group drop-down work in a system with 100 or 1000 groups? Is there a threshold where the drop-down becomes a text-field?<br />I also agree that looking at the dialog doesn&#8217;t clue you in on how to change permissions recursively, I recon a user looking to do this can do a fair amount of looking around before realising it&#8217;s worked into the close button (I don&#8217;t believe users read manuals or help files generally). At the same time, if you&#8217;re not looking to recursively change permissions, you would still get that question each time you want to change permission for a file.<br />These changes are looking nice otherways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emmanuel</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-104</link>
		<dc:creator>emmanuel</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-104</guid>
		<description>&gt;At the same time, if you're not looking to recursively change &gt;permissions, you would still get that question each time you &gt;want to change permission for a file.&lt;p/&gt;no, everytime you change permission for a directory, or a selection containing a directory: so it's quite OK, it makes sense in the end.</description>
		<content:encoded><![CDATA[<p>>At the same time, if you&#8217;re not looking to recursively change >permissions, you would still get that question each time you >want to change permission for a file.
<p />no, everytime you change permission for a directory, or a selection containing a directory: so it&#8217;s quite OK, it makes sense in the end.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Hofstetter</title>
		<link>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-105</link>
		<dc:creator>Philip Hofstetter</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/cneumair/2006/03/06/all-your-permissions-are-belong-to-us/#comment-105</guid>
		<description>Hi,&lt;p/&gt;while the recursive-thingie does lack discoverability in the advanced mode, I think it's fine in the dropdown-mode of the dialog.&lt;p/&gt;Why?&lt;p/&gt;Because non-professional users don't open that dialog with the idea to recusively change permissions - mostly because it does not occur to them that there are two possible outcomes of their changing permission.&lt;p/&gt;They just visit the dialog, make the changes and then, when that question pops up, learn that there are two possiblities and THEN decide.&lt;p/&gt;Questions:&lt;p/&gt;1) What happens if I close the recursive-question-dialog with the X? Yeah. nothing in the file system is changed, but what happens? Is the dialog closed? Does the dialog stay open but nothing changes? How to close then?&lt;p/&gt;2) IMHO, that permissions thing is more of a nuiscance than anything else for the casual user. I friend of mine is using Mac OS X and the only time he comes across the permission stuff is when he's using that "fix permissions"-feature of the disk utility. Maybe this functionality can even removed?&lt;p/&gt;Other than that, I really, really like the dialog design here.&lt;p/&gt;Philip</description>
		<content:encoded><![CDATA[<p>Hi,
<p />while the recursive-thingie does lack discoverability in the advanced mode, I think it&#8217;s fine in the dropdown-mode of the dialog.
<p />Why?
<p />Because non-professional users don&#8217;t open that dialog with the idea to recusively change permissions - mostly because it does not occur to them that there are two possible outcomes of their changing permission.
<p />They just visit the dialog, make the changes and then, when that question pops up, learn that there are two possiblities and THEN decide.
<p />Questions:
<p />1) What happens if I close the recursive-question-dialog with the X? Yeah. nothing in the file system is changed, but what happens? Is the dialog closed? Does the dialog stay open but nothing changes? How to close then?
<p />2) IMHO, that permissions thing is more of a nuiscance than anything else for the casual user. I friend of mine is using Mac OS X and the only time he comes across the permission stuff is when he&#8217;s using that &#8220;fix permissions&#8221;-feature of the disk utility. Maybe this functionality can even removed?
<p />Other than that, I really, really like the dialog design here.
<p />Philip</p>
]]></content:encoded>
	</item>
</channel>
</rss>
