Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


On Fri, 2015-07-03 at 20:00 +0200, Szymon Kłos wrote:
My work this week:
* I integrated my dialog with FileDialogHelper. Now RemoteFilesDialog
could be executed using the same command like normal file picker,
filters are added depending on context.
* bug 84190 - user wasn't able to change password after failed
authorization.
* bug 83089 - Cannot select location in properties dialogue
* I added support of opening multiple files
* some small improvements

Now I'm working on async operations. In this dialog it could be useful
to cancel current action, because sometimes opening remote directory is
very slow (connection to the cmis.alfresco.com/cmisatom takes > 30s,
which is default timeout in async mode). User should have possibility to
stop this process, for example after selecting any service by mistake
without waiting. Timeout also shouldn't be too short, because it may be
insufficient (like 30s for alfresco example).

To do:
* async operations

To get full async support you'll need to implement async API functions
in libcmis, which may be quite a big project. This could be something to
keep for the end of GSoC if you have some time left for it: better get
the dialog working and be slow rather than having nothing ready at the
end of the term.

--
Cedric

* implement support of context bits
* open/save remote buttons on toolbars

Regards,
Szymon




Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.