Alexander Thurgood wrote on 27-07-16 16:46:
Indeed, to second Regina's point, most businesses working in a Windows
(and even on a Linux CIFS share in businesses where I've worked
previously) network environment have their templates stored in multiple
different folders for the various "activities" or "departments" of that
business, and not necessarily all on the same fileshare mountpoint. How
will the new template manager layout deal with such a business workflow
? And how will the Sales department know the difference from a
ReminderLetter template to that of the same name used by the Accounts
department ?
I think by creating a "category" with <any> name for <any> department or
group or use case.
Apart from that: if that solution fails, it would be _most_ _helpful_ if
people with different needs jump in _early_ when all work is discussed.
Not with RC3 :)
Ciao - Cor
--
Cor Nouws
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6
- vrijwilliger http://nl.libreoffice.org
- volunteer http://www.libreoffice.org
- The Document Foundation Membership Committee Member
--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted
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.