On Fri, 01 Jul 2011 14:16:39 +0100 Martyn Russell <mar...@lanedo.com> wrote:
> On 01/07/11 13:44, Dan Leinir Turthra Jensen wrote: > > On Friday 01 Jul 2011 11:36:58 Martyn Russell wrote: > >> On 01/07/11 10:45, Éric Seigne wrote: > >>> Hello all, > >> > >> Hello, > >> > >>> i'm working on tablet edition. I've not found a file manager or > >>> any use of (for example) usb keys ... is there something planned > >>> about that ? > >>> > >>> if not, i'm okay to develop it. > >> > >> What do you plan to use the file manager for? > > > > The obtuse answer here is "To access the file system"... a less > > obtuse answer is "Because I want to" ;) > > From a geek stand point, I completely understand. From a non-geek > stand point, I would ask, why does the user need to access the file > system? A lot of modern day smart phones work with files but never > expose the file system in a way that a conventional file manager does. > > >> Ideally, you shouldn't need a file manager at all on the platform, > >> applications should manage the files you use properly for you. > > > > This is all well and good for the majority of people... right > > until you run into the programs which don't play by the rules ;) > > And we all know how many app devs are out there who don't like the > > rules (for whatever misguided reason there might be for it, they > > exist, and we have to deal with them). > > That's still not a reason to need a file manager. :) > > One reason is really just to cater for 3rd party apps with file types > unsupported as standard by the system (for example). > > A lot of the concepts of a file manager don't make sense to me on a > device like a tablet. Users seldom care *where* their files are, Yes, seldom. But occasionally they do. > rather what they're called and that they can find them. Again that's > the realm of the applications IMO. > > Understand, I am playing devil's advocate a little here ;) Indeed, and this is an example of a common design principle in use today. Things are set up to maximize ease of use, and all the technical details are hidden. That is fine for the cases where things work smoothly. But it is not fine for cases where they don't work as expected *at design time*. Then when (not if) unexpected conditions occur, the user typically has no way of even analyzing the problem. Let's not try to prevent people from providing reasonable tools, please. -- Bernd Stramm bernd.str...@gmail.com _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
