Minutes of the Design Hangout: 2016-Jun-17

    + Cor, Kendy, Bubli, Samuel, Jay, Heiko, Akshay, Sushobhan

Confirmed easy hacks
    + https://bugs.documentfoundation.org/show_bug.cgi?id=92152 (half arrow head; skill: svg/design)
      + Blog post: https://docs.google.com/document/d/1lgAD-aE54IswyAwg6yJ6MeTstCjznPvQR1nV_R95OXs/edit#
      + like the idea, comunication with Jan is necessary (and was done over the ML) (kendy)
      + consider that credits/copyrigths will not be given to the designer if the code is commited by someone else (Bubli)
      + publish (all)

  * Template Manager (Akshay)
        + Patches are merged, qa/documentation is to be done now
  * Progress of Area Fill project (Rishabh)
      + Pattern/bitmap split will be finshed today
      + Creating the new bitmap tab is planned for next week
  * Progress of Sidebar Improvements (Susobhan)
      + Styles Panel patch finished, up for review - https://gerrit.libreoffice.org/#/c/26020/
      + Merged Page Background Panel to master (from Impress to Draw), should be in 5.2
      + Working on existing issues and enhancements for Area Content Panel - https://bugs.documentfoundation.org/show_bug.cgi?id=90078#c4
      + Start with Shapes Tab next week after Area Content Panel enhancements
   * Notebokbar (kendy)
     + Rework of code is ongoing
   * Table Styles (kendy)
     + Focus on core work; import/export to odf
     + Table style is Writer specific and not relevant for Draw/Impress and Calc

Enhancements and proposals
    + Push extensions (Heiko)
      + e.g. tdf#71176, tdf#91874, or color replacer, or overall paragraph changer etc.
      + Extensions keep the main UI clean and simple but allows to enhance the app for special use cases
      + Suggestion is to have a separate component/keyword in the bugtracker for tasks that can be enhancements
      + Find users/coders to work on extensions
      + We have a component extension (kendy), qa team should make clear what it is used for (Jay)
      + Would need some needDevEval before moving a bug to this component (Jay)
      + Will bring it up to ESC for pushing it to the community
    + Disable automatic linking of urls by default (Samuel)
      + https://bugs.documentfoundation.org/show_bug.cgi?id=100424
      + Sticking with common behavior is preferrable (Jay)
      + Fixing all the bugs has first priority
      + Bug closed as WONTFIX
    + Results from poll about bookmarks on root level
      + https://plus.google.com/107566594492891737454/posts/FA4RgWeUDmT
      + 35% for simplicity, 65% for functionality (bookmark and cross-reference at the root level) (48 votes)
      + Reversed and placed at root level - https://gerrit.libreoffice.org/26418

Just to clarify: You're talking about .oxt extensions here?

If you want so, yes. Whether binary code or python script, extensions should be utilized in a similar ways as for Mozilla's software. I'm aware of the problems, beginning with the increased effort to enable external access rather than code directly.

Both binary code and Python scripts (and many other things) can be included in (.oxt) extensions. In short, everything that is managed via "Tools - Extension Manager..." and everything available at <http://extensions.libreoffice.org/extension-center> is such an extension.

I just asked because sometimes "extension" is used with different meanings.