Development > User Interface

Scribus UI/UX and Styles

(1/2) > >>

The previous thread died, so I will start a new thread, as the forum advised.

I currently teach design, using the industry standard Adobe InDesign. However, I have no wish to exclusively promote commercial software, and so (re)turned to Scribus to see what changes had occurred in the last while. This is my first forum post, since I am actively concerned at this point. I had thought that after 15 years of development Scribus might be in a better state.

I have many issues with Scribus but will start with workflow, since this is the most important aspect. Yes, the features must be there, but unless the software is efficient to use, it will not be taken up.

I have read and commented on Martin Reininger's slideshow that proposes some excellent changes to the panels.

The biggest problem currently in the workflow is the character and paragraph formatting. These properties should be assigned through styles. Doing otherwise is the hack "word processor" approach, which Scribus should not be promoting.

However, given that some users may still want to work the ad hoc way, direct property editing cannot be forbidden. But the current workflow makes it the high priority approach, erecting barriers to the proper workflow.

In particular, there is no way to edit a style from the Text Properties panel. I must open a separate Style Manager dialogue, which is not a dockable panel. Once a style is defined, I must return to the Text Properties panel to apply it. This is a terrible workflow.

I recommend that the Text Properties panel be redesigned as a style panel. The Style Manager can then be removed as superfluous. In fact, any dialogues one may need to work with regularly should be replaced by panels.

To accommodate those not using styles, there can be one default style for each type (character, paragraph, etc.) that applies anywhere an actual style has not been explicitly defined. The workflow will then be identical in all cases:

First, select an existing style or create a new once. Second, alter its properties, which would be displayed directly underneath the style name. If the "default" style is selected, the current text would be directly updated.

This method would be superior even to InDesign, because the large character/paragraph toolbar in that program encourages users to make modification in the context area, even though this is usually the incorrect approach.

I hope this explanation suffices. I short, I am proposing two things. First, a more fluid and customisable panel system, as Martin suggests. Second, a styles system that is much easier to use.

I am a fairly recent user and observer of Scribus which I now recognise to be the only route to open source publishing on my Ubuntu platform.  Alternative proprietary tools are too costly. And I prefer Ubuntu to Windows.

My interest is in integrating Scribus into my development framework where content can be rapidly generated and customised and indeed personalised on the fly, and as a bonus allowing the same content to also flow to an online publication channel (website).  Scribus of course is a print only layout engine and different colour profiles are required in these two modes.

I am not sure of your workflow environment. Windows/Linux/Mac? And version of Scribus you are exploring.

Have you considered importing default styles from pre-prepared Scribus templates?

Have you explored what Scribus scripting can offer to extend Scribus? ... ... is another ingenious script.

Follow this video ...

You can setup your Scribus documents using csv file containing your variables (object properties) to be applied (including styles).  In that video (at around 13 minutes in) is a reference to using xpath (see further below).  Look at the ScribusGenerator download master and you will see example *.sla socument templates going beyond simple business cards.


I have followed the slideshow you linked to but in my view the alternative proposed UI panel layout is just as confusing.  Only the necessary UI controls should be shown to the user.

My approach is to build a leaner UI above and mapped to the lower Scribus UI layer.  Scribus scripts in fact target the Scribus API. A customised UI can be built in web browser to “drive” Scribus XML document model.  Scribus elements can in fact be targetted using xpath queries, avoiding panels.

In summary, take the UI design into your own hands and regard Scribus as a very useful layout engine embedded in your custom framework.

The Scribus *.sla file is an XML file.  I have applied xquery to change properties of Scribus objects.

 Examine the structure of any *.sla file in XMLCopyEditor ...
 Look at the xpath of elements (and recollect where xpath is used in ScribusGenerator).
 The advantage of using xpath to target Scribus as an XML document is that Scribus documents can be processed in the cloud, opening up possibility of collaborative layout (rather like InDesign).


There are other approaches I have tried, such as using automation scripts to “drive” Scribus GUI objects and menus, but to avoid confusion the above is enough for starters.

yes, i agree with you that creating and updating styles from the text palette (TP) should be possible (and the preferred way to do it!)

in the past i've made similar proposals:

- remove the "no style" thing: every bit of text *must* have a style
- separate the style manager (which shows the list of styles and allows to create / delete / import styles) from the dialog that defines the styles.
- add buttons in the PP for creating (new or from selection) and edit (optionally updating from selection) styles.

i wonder if you would welcome such changes.
they would not be that hard to program...

you're proposal seems to be even more radical...
but i'm not sure i understood it correctly.

can you give more details on the part where you say that the styles would be almost mandatory?

@rparmar, can i ask you what's your goal for this thread?

the topic is interesting, now i wonder what would be the next steps...

Pexim SLani:
Scribus is the future, I believe  8)

I had a very difficult time to learn the basics in Scribus, cos I'm not a pro. I want to use Free Software apps cos of my beliefs. I was Indesign user, but not any more, cos I switched to Linux, for good.

Before 1,5 year, I've discovered Viva Designer 9.5 and tried it on my Ubuntu 16.04. I was super surprised how simple UI is and how intuitive software Viva Designer is. I had 0 problems to learn it.

I think that Scribus Devs have to investigate UI of Viva Designer.

I'm not promoting proprietary software, I'm just saying that we don't need to "invent hot water". 


[0] Message Index

[#] Next page

Go to full version