<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - UI Window: LibreOffice should use macOS design language and components for drawing window frame"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=83700#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - UI Window: LibreOffice should use macOS design language and components for drawing window frame"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=83700">bug 83700</a>
from <span class="vcard"><a class="email" href="mailto:sierkb@gmx.de" title="Sierk Bornemann <sierkb@gmx.de>"> <span class="fn">Sierk Bornemann</span></a>
</span></b>
<pre>(In reply to Emir Sarı (away) from <a href="show_bug.cgi?id=83700#c13">comment #13</a>)
<span class="quote">> This requires a near-total rewrite of whole Libreoffice macOS UI code, no? I
> wonder how much would it cost if to crowd-source this.</span >
Idea/Proposal:
If so extensive, too extensive for one developer to fix alone and in between –
maybe worth to be a topic for the next GSoC (GSoC 2018 just seems to be over)?
Document Foundation’s wiki: LibreOffice Google Summer of Code
<a href="https://wiki.documentfoundation.org/Development/GSoC">https://wiki.documentfoundation.org/Development/GSoC</a>
Document Foundation’s wiki: GSoC Ideas
<a href="https://wiki.documentfoundation.org/Development/GSoC/Ideas">https://wiki.documentfoundation.org/Development/GSoC/Ideas</a>
Document Foundation’s wiki: Development/GSoC/2018
<a href="https://wiki.documentfoundation.org/Development/GSoC/2018">https://wiki.documentfoundation.org/Development/GSoC/2018</a>
Maybe worth to think about to fix also several other Mac related bugs on the
(meanwhile long) list of meta-<a class="bz_bug_link
bz_status_NEW "
title="NEW - [META] Make LibreOffice shine and glow on OS X"
href="show_bug.cgi?id=42082">bug #42082</a> (MacOS-Wishlist) in a bunch of one or
two or three concerted actions in the context of such an event and with higher
priority and higher available developer ressources to get rid of them once and
for all instead of leaving them unfixed for years (also because of lacking
developer ressources to concrete fix them, which maybe could be addressed
within GSoC or similar)?
What about this idea?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>