<div dir="ltr">Hi Martin and all<div><br></div><div>I am afraid I want to disagree and that's exactly why Jolla UI guidelines voice would be very welcome here. If common guideline would be to expose file system to the user Windows style, I'll be the first one to do it :)</div>
<div><br></div><div>As for my current person and arguably humble opinion, iOS is doing just great without the file dialog. It does force/encourage all the apps use own sandbox only (and own file-like selection dialogs then) and calls for workarounds when you actually want apps to interoperate, but.. the simplicity benefits you get to user by hiding the file level are great. </div>
<div><br></div><div>Whether it's useful enough for Sailfish to follow the same concept or whether there could be some useful enough half-way compromises, I don't know. I'd love to have somebody from Jolla UX have a serious thought about it. Just tell us how a typical file editor and pdf viewer should look like :)</div>
<div><br></div><div>Best regards,</div><div>Artem.</div><div><br></div><div>P.S.</div><div>The next question developers me included are going to ask is how to choose photos/pdfs/whatever coming from main phone storage, SD card, dropbox, app-specific source (a'la Android) or whatever else. Android solution is super flexible, but not simple at all and forces user think, iOS solution is forcing simplicity at a cost of features (particularly I believe it's one of the reasons why there is no SD card in iOS - too UX-heavy to expose SD peculiarities when choosing photos/videos).</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 4, 2013 at 11:28 AM, Martin Kolman <span dir="ltr"><<a href="mailto:martin.kolman@gmail.com" target="_blank">martin.kolman@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>4.11.2013 02:10, Artem Marchenko:<br>
</div><div class="im">
<blockquote type="cite">
<div dir="ltr">I'd appreciate some UI guidelines voice from Jolla
here (I can understands they might have not thought of this use
case before, well, it's time for it then :)).
<div><br>
</div>
<div>Looking at iOS and Android, it might be not a bad idea to
have a phone UI without an explicit file interface at all.
Hackers won't appreciate it, but they have terminal anyway
and, well, for them you can create a custom File Open dialog. </div>
<div><br>
</div>
<div>Regular users might appreciate a photo choosing dialog
guaranteed to include all device photos more.</div>
</div>
</blockquote></div>
Yeah, I think those two are not mutually exclusive & doable.
IIRC there should be Tracker, so it should be possible to get all
photos or any other categories of files Tracker can discern (all
audio files, all txt files, all PDFs). <br>
But on the other hand, some applications just won't do without a
standard file-chooser, like a text editor, offline comic book
reader, an image editor. At least without getting and putting the
files on a global file heap, making finding stuff difficult.<br>
Of course a lot can be done with tags and semantic stuff (where did
the file come from, what app made it), but as shown by the KDE &
GNOME projects (Nepomuk, Akonadi, Tracker, etc.) it is not easy to
get right. Just having a simple time-proven file open dialog is IMHO
a much simpler, easier & safer solution.<br>
<br>
BTW, Android and to a lesser degree Harmattan could be used as a bad
example of what happens if there is no default file dialog - every
app that needs it would implement their own, all looking different
(and not native) and every one of them with their own set of
drawbacks. <br><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Cheers,</div>
<div>Artem.</div>
<div><br>
</div>
</div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Sun, Nov 3, 2013 at 11:02 PM, Martin
Kolman <span dir="ltr"><<a href="mailto:martin.kolman@gmail.com" target="_blank">martin.kolman@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>1.11.2013 22:16, Janne Pulkkinen:<br>
</div>
<div>
<div>
<blockquote type="cite">
<div dir="ltr">Sailfish would benefit from having a
default file/directory chooser instead of having
different implementations made by different
developers which would only make the OS appear
inconsistent for the average user.
<div> <br>
</div>
<div>Just putting this out there, because I would
really like to see this implemented in the SDK.<br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2013/11/1 Damien
Caliste <span dir="ltr"><<a href="mailto:dcaliste@free.fr" target="_blank">dcaliste@free.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<div><br>
On Fri Nov 1 08:54:03 2013 <a href="mailto:khertan@khertan.net" target="_blank">khertan@khertan.net</a>
wrote:<br>
> For the file selector, it should
not be difficult to make one with a<br>
> SilicaListView, and the qmldir
extension.<br>
</div>
Ok, I'm new to QML, I didn't know about
qmldir. I'll give a look. But I was
hopping something common to avoid
discrepency on the platform. Thanks for
the info.<br>
<div><br>
> For notification, i ve made a
something similar but more simple to the<br>
> Harmattan InfoBanner for ownNotes :<br>
> <a href="http://khertan.net/blog/silica_infobanner" target="_blank">http://khertan.net/blog/silica_infobanner</a><br>
</div>
Great. I'll give a look also waiting for
something from Jolla if any. Thanks.<br>
<div>
<div><br>
Regards,<br>
<br>
Damien.<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SailfishOS.org Devel mailing list</pre>
</blockquote>
</div>
</div>
What about the FileDialog component[1] introduced in Qt
5.1 ?<br>
The documentation says that it will use a native platform
file-open dialog if available,<br>
so maybe just make a silica themed file open dialog and
show it once the FileDialog component is used ?<br>
<br>
[1]
<a href="http://qt-project.org/doc/qt-5.1/qtquickdialogs/qml-qtquick-dialogs1-filedialog.html" target="_blank">http://qt-project.org/doc/qt-5.1/qtquickdialogs/qml-qtquick-dialogs1-filedialog.html</a><br>
</div>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
Artem Marchenko<br>
<a href="http://agilesoftwaredevelopment.com" target="_blank">http://agilesoftwaredevelopment.com</a><br>
<a href="http://twitter.com/AgileArtem" target="_blank">http://twitter.com/AgileArtem</a>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Artem Marchenko<br><a href="http://agilesoftwaredevelopment.com" target="_blank">http://agilesoftwaredevelopment.com</a><br><a href="http://twitter.com/AgileArtem" target="_blank">http://twitter.com/AgileArtem</a>
</div>