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


* Present: Heiko, Samuel, Tomaz, Kendy

* GSoC

    + https://summerofcode.withgoogle.com/dashboard/

    + Approved UI projects:
        + Improve user experience with Table Styles (mentors: dev - kendy/miklos, ui - jay/heiko)
        + Review of the Area Fill dialog (mentors: dev Bubli , ui - jay/heiko)
        + Redesigning the Template Manager (mentors: dev - samuel, ui - jay)
        + Review of Sidebar and it's functionality (mentors: dev Bubli , ui - jay)
        + Infrastructure for defining toolbars via .ui (Glade) files (mentors: dev - kendy/samuel, 
ui - heiko)

    + Started a weekly update meeting with Rishabh (Area Fill project) and Bubli like in SCRUM 
        + what has been done, what is planned, where are the bottlenecks
        + sounds great (Kendy)
        + encourage your students to hack already, bonding by producing code is best :-) (Kendy)

* Draw (Heiko)

    + Started to create metabugs for better organization (tdf#99563, tdf#99525)

* Sidebar survey (Heiko)

    + No complaints about the proposed guidelines
    + Added to the HIG at the wiki

* Help content (Jay / Kendy)

    + http://vm173.documentfoundation.org/

    + Olivier updated the xslt so that it produces a list of keywords now (Kendy)
        + see eg. http://vm173.documentfoundation.org/text/swriter/main0000.xhp
        + not sorted yet, but a good direction of developments I think :-) (Kendy)

* needsUXEval (Heiko / Kendy)

    + now it is not necessary to use the 'ux-advise' component any more
    + instead, add the 'needsUXEval' keyword, and the ux-advice@ ML will be CC'd
    
    + should we kill the 'ux-advise' component? (Samuel)
        + probably not yet, as it shows which bugs are untriaged (Kendy)
        + but when we move them to the neesUXEval keyword, then yes (Kendy)

* Tabs etc

    + https://bugs.documentfoundation.org/show_bug.cgi?id=99528
    + http://i.imgur.com/aLP247v.png
    + Three options for navigation right now: tabs (e.g. paragraph style), tree (options), and icon 
view (hyperlink)
    + We should have one way of presentation (Heiko)

* Calc Default Header (Samuel)

    + https://bugs.documentfoundation.org/show_bug.cgi?id=99296
    + Clearing the text (Table1/Page1) doesn't solve the issue since empty space remains
    + Disabling the header/footer by default is better (Tomaz, Samuel, Heiko)
    + Worries that people can find the setting (Samuel)
    + Excel has no header/footer, let's do the same (Kendy)
    + Will research a bit more, so that there is one place to set this (Samuel)

* "Custom Animation" probably should be called just "Animation" (Samuel)

    + https://bugs.documentfoundation.org/show_bug.cgi?id=95387
    + agreed to change (all)

* Drop the term "Manager" (Samuel)

    + Template Manager -> Templates
    + Extension Manager -> Extensions
    + Are there more?
    + agree (all)
    + Problem with "Extensions" and "Add-Ons" in the same menu then, postpone this

* Add-Ons vs Extensions (Samuel)

    + Term "Add-Ons" used once: http://i.imgur.com/qpK5AsK.png
    + Rename Add-ons to Extensions and move Extensions Manager into this submenu + rename to 
Organize Extensions (like for Makro) (Heiko)
    + Drawback is a submenu with only one item by default (Samuel)

* Shortcut for Extension Manager (Jay)

    + Is Ctrl + Alt + E a good shortcut?
      https://gerrit.libreoffice.org/#/c/23376/
    + no objections on the ML, so pushed that (Samuel)


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.