<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Improve listing of (table) styles to reflect that newly created styles are in the document only (not available elsewhere)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130953#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Improve listing of (table) styles to reflect that newly created styles are in the document only (not available elsewhere)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130953">bug 130953</a> from <a class="email" href="mailto:momonasmon@gmail.com" title="Maxim Monastirsky <momonasmon@gmail.com>"> Maxim Monastirsky</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=130953#c6">comment #6</a>) > However, since table > styles might be installed per extension (see also <a class="bz_bug_link bz_status_NEW " title="NEW - Make table styles extensionizable" href="show_bug.cgi?id=124046">bug 124046</a>) the situation > is less clear Why less clear? I would assume that styles from extensions will be visible in all documents (as long as the extension is installed), so where is the problem? > Simple solution to distinguish system from user styles is to show the latter > on the bottom after a horizontal ruler. Why is there any need to distinguish system styles from user styles? From a user perspective of applying styles to tables, there is really no difference between system and user styles, as they work the same. Also, once a system style is applied, it's exported into odf, and from now on whatever is stored there is used, and actually overrides the system style of the same name. Which means that putting user styles under a horizontal ruler would just move there all used styles in existing documents. Of course, we might not put under the ruler user styles with the same names as the system ones. But then it even less clear why this kind of separation is useful, as styles can also be modified, and so styles with the same name might be actually different in different documents. If anything, an icon near a system style might be a better option, but again, I don't see any point in doing this either. This also can't be an alternative to removing the autoformat dialog. It indeed might be less confusing in the scenario of newly created user styles, but what about manipulation of existing styles? Using the dialog, styles can be removed or renamed, but this isn't reflected in the sidebar of the current document. Also the other way, existing styles can be updated from selection with the sidebar, but this isn't reflected in the dialog (e.g. the preview will be based on system data instead). Technically, system styles are appended to the document styles once the sidebar is opened for the first time. From that point, they are document styles by any mean. That's why any changes made to the system storage afterwards are not reflected there, as those two lists already diverged at this point. All of this won't be of a concern once the autoformat dialog is removed, as that would mean that users will no longer have a way to modify the system styles (much like they can't modify paragraph system styles).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>