--047d7b343ecaabdefe04e6bcbc38 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Sep 19, 2013 at 10:42 AM, Todd wrote: > > On Sep 18, 2013 11:51 PM, "David Faure" wrote: > > > > On Tuesday 17 September 2013 13:58:25 Todd wrote: > > > Do we need the UID and GID? Can we just store whether the file is > > > readable, writable, and executable? That would be three bools rather > than > > > two ints. > > > > See the property dialog, this info appears there for instance. > > I assume it can also be shown as an extra column in dolphin? > > Use lxr.kde.org to find all other users, if any. > > > > If it's just the props dialog then we could imagine returning that in > stat and > > not in listDir though. And then stating from the props dialog (it > currently > > gets it from the directory listing, when created with a kfileitem from > there). > > Yes, it can be shown in the file properties and info panel, but those > aren't needed during the directory loading. It can also be shown in > details view and below the file in icon view, but that can be lazy loaded. > > In terms of low-level stuff needed during directory loading, I think the > permissions should be enough. > I'm not sure, but the device id is an int right now, right? In that case i doubt that a device id will ever be as big as an int: 2147483647 Can't we just steal 3 bits there and use it for read, write and executable? -- i haven't looked anything up in this area! -- --047d7b343ecaabdefe04e6bcbc38 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Sep 19, 2013 at 10:42 AM, Todd &= lt;toddrjen@gmail.c= om> wrote:


On Sep 18, 2013 11:51 PM, "David Faure" <faure@kde.org> wrote:
>
> On Tuesday 17 September 2013 13:58:25 Todd wrote:
> > Do we need the UID and GID? =A0Can we just store whether the file= is
> > readable, writable, and executable? That would be three bools rat= her than
> > two ints.
>
> See the property dialog, this info appears there for instance.
> I assume it can also be shown as an extra column in dolphin?
> Use lxr.kde.org t= o find all other users, if any.
>
> If it's just the props dialog then we could imagine returning that= in stat and
> not in listDir though. And then stating from the props dialog (it curr= ently
> gets it from the directory listing, when created with a kfileitem from= there).

Yes, it can be shown in the file properties and info p= anel, but those aren't needed during the directory loading.=A0=A0 It ca= n also be shown in details view and below the file in icon view, but that c= an be lazy loaded.=A0

In terms of low-level stuff needed during directory loading,= I think the permissions should be enough.

I'm not sure, but the device id is an int right now,= right? In that case i doubt that a device id will ever be as big as an int= :=A02147483647
Can't we just steal 3 bi= ts there and use it for read, write and executable?

-- i haven't looked anything up in this area! --
--047d7b343ecaabdefe04e6bcbc38--