![]() ![]() I recall, perhaps a decade or more past, watching some sales video guides for a different product that offered a huge number of styles. It seems to me that the Built-in and Paid-for packs would need to be offered just as they are and it should be left to the user to turn them into User Styles and Presets, sitting alongside their own Styles, in order to manage how they are grouped (and, as now, permit multiple copies of the same Style or Preset to make grouping in preferred "sets" simpler? Also to provide consistent use of the Keyboard Shortcut feature.) (I am not sure as I do not have any paid for Packs.) The same goes for Style Packs with the difference that, potentially, they would bot be automatically updates with each update or version upgrade. (There may be some issues about managing those styles and who has the rights to modify them if working in a Multi-User environment but that probably goes beyond the scope being discussed here.)įor Built in styles that are not copied to be User styles one can still modify the structure (i.e the Style Sets groups) used for delivery as part of the application installation BUT as the next new installation the styles and presets will be re-installed (potentially with some updates for functional compatibility reasons). However, as a thought challenge for how to work with a development design, there are certain considerations.įor User Styles (including copies of Built in styles and presets, as Okular has previously described) there is already the possibility to create and save a folder structure containing the required styles. I'm not a great Styles user so this does not really concern me much.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |