Activity log for bug #887916

Date Who What changed Old value New value Message
2011-11-09 08:22:43 Mikkel Kamstrup Erlandsen bug added bug
2011-11-09 08:23:22 Mikkel Kamstrup Erlandsen dee: status New Confirmed
2011-11-09 08:36:36 Mikkel Kamstrup Erlandsen description It would be nice to have a DeeModel implementation that was automagically populated (and updated) reflecting the contents of a designated directory. The columns of the model would be implicitly set by specifying a set of GIO file attributes to look up on the files in the directory. Combined with a DeeTreeIndex this would make the Downloads section of the files lens trivial - and in fact if someone wanted to write a whole file browsing lens then that would be really easy as well. It would be nice to have a DeeModel implementation that was automagically populated (and updated) reflecting the contents of a designated directory. The columns of the model would be implicitly set by specifying a set of GIO file attributes to look up on the files in the directory. I am thinking two constructors: /* varargs is a list of 'const gchar*' with gfile attributes */ dee_directory_model_new (GFile *directory, ...); /* attribs is a NULL terminated array of strings with GFile attributes*/ dee_directory_model_new_for_attribs (GFile *directory, const gchar **attribs) FIXME: This may all break down if there's no generic way to look up the GFileAttributeType of some file attribute Combined with a DeeTreeIndex this would make the Downloads section of the files lens trivial - and in fact if someone wanted to write a whole file browsing lens then that would be really easy as well.
2011-11-22 12:44:49 Didier Roche unity: status New Confirmed
2011-11-22 12:44:51 Didier Roche dee (Ubuntu): status New Confirmed
2014-07-24 21:16:43 Marco Trevisan (TreviƱo) unity (Ubuntu): status New Confirmed