Mantis Issue Tracking for Scribus
· Hosting provided by Anduin.net / Øverby Consulting ·

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001132ScribusStylespublic04-Sep-21 05:2311-Sep-15 12:37
Reporterblazej 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSMandrakeOS Version9.2
Product Version1.2 
Target VersionFixed in Version 
Summary0001132: Styles should be separate from documents
DescriptionI would *love* to see the following feature in Scribus.

Currently, styles are attached to documents (and templates). If your project consists of multiple files, there is no easy way of making a change to a particular style that all pages use.

To deal with such problems, many applications define the concept of "projects". This way you have a single "project" file with all your styles in it. All your documents refer to this file as source of styles. I believe this would greatly simplify working with styles and the propagation of style modification between documents.

Another great idea is to have cascading styles, like in HTML...
TagsNo tags attached.
Attached Files

- Relationships
related to 0000363acknowledged differential paragraph styles 
related to 0001322acknowledged unify Styles and Templates, make them hierarchical (add inheritance) 
related to 0001791acknowledged Linking to external text 
related to 0002107acknowledged Master documents 
related to 0002098assigned Metabug: New File Format 
related to 0002793feedback Master Pages should be (optionally) separate from the Document 
related to 0003821acknowledged Metabug: Usability 

-  Notes
(0002446)
blazej (reporter)
04-Sep-21 05:26

Having styles stored separately from documents (by default or as an option) would greatly increase re-usability of styles, allow for creation of style libraries that multiple people can use etc. Such a feature is absolutely necessary if more than one person works on a project. BTW, you could still keep document-level styles.
(0002449)
louisdesjardins (developer)
04-Sep-21 13:04

Say for instance styles would work the same way as a library, one could have a basic library of styles he could pick styles from and use in any document. Would the Style menu then be only a view menu of the styles used in that particular document (much like a font and image tracker)? Working this way would be like having a *Style Server* handy. I don't think many programs offer a feature like this.

The *append style* command has its limit since you must first know in what document is which style, then import it... On the other hand, working with such a *style server* has at least one drawback: a change in a style would reflect on all documents using this style... An unaware user could face a big problem. Maybe a *synchronize styles* option would save the situation?

I like the idea which I find very refreshing and innovative! I think this is making good use of computing capabilities and could be very efficient in lots of production and creative environment.
(0002450)
cbradney (administrator)
04-Sep-21 22:17

We will have cascading styles in 1.3. The other idea is a good one. We can see how to implement in 1.3.
(0005569)
christoph_s (administrator)
05-Jul-13 22:23

Maybe it would be useful to have at least three different types of external style sets available:

1. A project file as suggested by blazej. Such project files could be synchronised, so a change in the original file would affect all connected files.

2. A set of styles from a single document could be saved separately for reuse in other documents. This library would not synchronise, but instead save the time of creating the same style for similar publications over and over again.

3. A third option might be like the one in OpenOffice.org, where you can import styles from existing documents. An option to select the styles to be imported instead of importing the style set as a whole would be even better. Later on in development, this feature might also be applied to the OO.o import plugin.


In any case, it would of course be necessary to have a security mechanism in place to prevent the deleting of existing styles, i.e. if "paragraph_style" exists in both files, it would have to be added as "paragraph_style(1)" or something like that.
(0005573)
ringerc (administrator)
05-Jul-14 02:28

christoph_s , you can already import styles from another document.

I agree that externally linked styles would be useful. Not worth thinking about until the new file format is in, but I think it might be relatively easy then.
(0026874)
JLuc (reporter)
11-Sep-15 12:37

Exporting (without renaming them !) the currently selected styles to a bunch of currently selected SLA files would help multiple files single project editing too.

- Issue History
Date Modified Username Field Change
04-Sep-21 05:23 blazej New Issue
04-Sep-21 05:26 blazej Note Added: 0002446
04-Sep-21 13:04 louisdesjardins Note Added: 0002449
04-Sep-21 22:17 cbradney Note Added: 0002450
05-Jul-13 22:23 christoph_s Note Added: 0005569
05-Jul-14 02:28 ringerc Note Added: 0005573
05-Jul-14 02:28 ringerc Status new => acknowledged
05-Jul-14 02:29 ringerc Relationship added related to 0000363
05-Jul-14 02:29 ringerc Relationship added related to 0001322
05-Jul-14 02:30 ringerc Relationship added related to 0001791
05-Jul-14 02:31 ringerc Relationship added related to 0002107
05-Jul-14 02:31 ringerc Relationship added related to 0002098
05-Nov-05 05:16 ringerc Relationship added related to 0002793
06-May-15 20:18 christoph_s Relationship added related to 0003821
11-Sep-15 12:37 JLuc Note Added: 0026874



Copyright © 2000 - 2013 MantisBT Team
Powered by Mantis Bugtracker