I thought eventually LO would migrate to GTK3 so Glade would be used by
default?
On Wed, Mar 21, 2018 at 1:26 PM, kainz.a <kainz.a@gmail.com> wrote:
Hi Pedro,
thanks for the Notebookbar buglist. We have a GSOC Student how will work
on notebookbar so it's also my dream that notebookbar will be awaiy from
experimental. My dream would be also 6.1 but I hope it will happen at least
with 6.2.
As the notebookbar is different implemented then the default and sidebar
layout I don't think it should be default in the near future. Bigest
problem is that when the NB bugs are fixed the NB isn't configurable by the
LO UI.
But I hopen NB will be ready for use in the near future for the people how
will like it.
I know zereo about coding, but I did the Groupedbar full/compact and
tabbedbar compact. So you don't need ANY coding experience to join the LO
design group on telegram or anywhere else. You can make notebookbars
without coding with the gnome glade app which is a GUI to make the
notebookbar.
Cheers
Andreas_K
--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-design] Agenda for the design meeting 2018 Mar/21 (continued)
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.