Re: [Nautilus-list] bug 75214: preferences:/// etc. should be read-only
- From: Dave Bordoley <bordoley msu edu>
- To: Diego González <diego pemas net>
- Cc: Nautilus List <nautilus-list lists eazel com>, George <jirka 5z com>
- Subject: Re: [Nautilus-list] bug 75214: preferences:/// etc. should be read-only
- Date: 25 Apr 2002 17:41:16 -0400
Well from my limited knowledge i would think the gnome-vfs way would be
better in general, since theoretically at least other programs could use
these directories.
dave
On Thu, 2002-04-25 at 18:24, Diego González wrote:
> hi
>
> i've been looking at this bug, and would like to share some thoughts
> that i have about it. This bug can be solved (as i see it) at two
> diferent levels:
>
> 1) at gnome-vfs level
> 2) at nautilus level
>
> i think it would be better to solve it at the at the gnome-vfs level,
> the reason why we can edit preferences:/// and applications:/// is that
> the vfolder-desktop method does not support file permissions, as it
> stores the modifications that a user does in his home directory. So to
> solve i think it would be needed to implement the permission bits at
> least for the preferences:/// uris.
>
> So far i have put some code on the do_read_directory and on the
> do_get_file_info methods on the vfolder-desktop method, so that one the
> uri starts with preferences:/// its permission bits are automatically
> set to non writeable.
>
> The ugly thing is that nautilus put an emblem to show the non writeable
> nature of the folders, which is ugly.
>
> What do you think about this way of addressing the bug?
>
> regards,
> Diego
>
>
>
> _______________________________________________
> nautilus-list mailing list
> nautilus-list lists eazel com
> http://lists.eazel.com/mailman/listinfo/nautilus-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]