The first week Google Summer of Code passed, so I will present what i
managed to do during this time.
* I added the "Open Remote File" button to the Start Center.
* Created .ui file and wrote new class for this window (I called it
RemoteFilesDialog), which I
placed in svtools module. To define if is used 'open' or 'save' mode
I used WinBits and previously defined WB_OPEN and WB_SAVEAS flags, which
are used in standard fpicker dialog.
* Now, my dialog contains only „services listbox” and „add service”
split button.
* Actually existing (bookmarked) places are filtered and only remote
services are pushed into listbox.
* I added options of editing and deleting services, which are accessible
from the dropdown menu of the „Add service” button. Bookmarks are saved
only when one of it was modified or deleted.
* I also started to reworking of the old dialog used to creating
connections: I moved all CMIS service subtypes to the main service type
listbox.
To do next:
* Now I don't recognize CMIS subtypes, and when I'm editing one of it,
the type listbox is filled with the wrong service name.
* Reorder service types. Should be sorted in groups: apps (Google Drive,
OneDrive, ...) – connections (alfresco, Share Point, ...) - protocols
(FTP, WebDAV, SSH, ...)
* Show and hide controls depending on a service type.
* Add to the dialog rest of controls which will be used in future
Regards,
Szymon
Context
- [GSoC] Improve user experience with CMIS – Weekly report #1 · Szymon Kłos
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.