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
0000363ScribusStylespublic2004-03-25 17:282013-11-01 14:21
Reporterale 
Assigned To 
PrioritylowSeverityfeatureReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000363: differential paragraph styles
Descriptionit would be really really really cool if paragraph styles' definition could be separated into

- normal (by default)

- first n lines

- last m lines

per default, m=n=0

a combo box on the dialog could let the user switch between the sub-styles...
Additional Information-> it's a long term feature request...
TagsNo tags attached.
Patch
Attached Files

- Relationships
related to 0001322acknowledged unify Styles and Templates, make them hierarchical (add inheritance) 
related to 0001546acknowledged style import/link ideas 
has duplicate 0003410closedcbradney depending paragraph styles 
has duplicate 0004578closedavox Typographic enhancement: First line of paragraph 
related to 0000204acknowledged Drop Cap only for the first paragraph 
related to 0001132acknowledged Styles should be separate from documents 
related to 0001076acknowledged New (Sub) Style definition for Boldface, Italics and Plain 

-  Notes
(0002309)
ringerc (administrator)
2004-09-05 21:51

First paragraph, first n chars, and first n words would also be extremely handy.

This would go nicely with style inheritance.
(0007297)
avox (administrator)
2005-11-01 16:47

What about programmable paragraph styles, ie. small Python programs which format the paragraph according to your need? When the Python interface is decent enough, you could just request the first n lines yourself and apply any charstyle to it.
(0007307)
ringerc (administrator)
2005-11-02 04:51

That'd work, and if PageItems gain the ability to signal that they've been altered you could have a Python snippet trigger on that signal to apply the formatting.

Honestly, though, I suspect it's better done in the core app. Most people won't want to have to (or know how to) program their paragraph styles.

The other problem is that if you want documents to carry the code around (ensuring the doc is portable) that'd be a horrific security risk. Python is poorly suited to that sort of in-program scripting and automation, as it provides no way to restrict programs' access to the full system APIs. You can read and write files, dlopen(...) libraries, write to the process's memory, execute other programs, and so on. While this is all very useful and powerful when using Python for many embedding tasks, especially with external data or control sources, networking, and so on, it does make it unsuitable for anything that might have to be embedded in a document. It's language is also not really forward compatible enough - it's way too easy for a Python 2.4 user to write code a Python 2.3 user can't run.

Lua and JavaScript are both much better choices for that sort of thing. Since Qt provides a JavaScript interface library (Qt Script for Applications, ie QSA) already, that would seem the natural way to go if a locked-down script language for simple automation and other tasks, one that's perhaps safe-ish to bundle in documents.

Honestly, though, I just don't like the idea of ever having scripts bundled in documents as would be required for this idea. Sure, you can ask the user if they want to run them, but most people won't really understand what that means, and I don't think it's really a good idea to rely on that for things that might be central to the document's function. I know I sure wouldn't want to be responsible for ensuring nothing was available to scripts that could be directly or indirectly exploited to make a macro virus.

Overall, I really think this is best done in the core app if possible.
(0013444)
mkoren (reporter)
2006-11-18 03:32

How about different styles for each tab field defined in a paragraph style? To automatically format tab-defined columns (right hand column right aligned and italic or something). Based on a mailing list question.

- Issue History
Date Modified Username Field Change
2004-03-25 17:28 ale New Issue
2004-09-05 21:51 ringerc Note Added: 0002309
2004-09-27 08:38 ringerc Relationship added related to 0000204
2004-12-17 03:57 ringerc Relationship added related to 0001322
2005-07-12 06:25 ringerc Status new => acknowledged
2005-07-14 02:29 ringerc Relationship added related to 0001132
2005-09-16 08:47 ringerc Relationship added related to 0001076
2005-11-01 16:47 avox Note Added: 0007297
2005-11-02 04:51 ringerc Note Added: 0007307
2006-02-27 01:57 avox Relationship added related to 0002228
2006-03-14 13:38 cbradney Relationship added has duplicate 0003410
2006-04-13 00:43 mhanski Relationship added related to 0001546
2006-05-16 20:22 mhanski Note Added: 0011331
2006-05-16 20:22 mhanski Note Deleted: 0011331
2006-05-16 20:29 christoph_s Note Added: 0011334
2006-05-16 20:29 christoph_s Note Deleted: 0011334
2006-11-18 03:32 mkoren Note Added: 0013444
2006-12-05 09:52 louisdesjardins Relationship added has duplicate 0004578



Copyright © 2000 - 2014 MantisBT Team
Powered by Mantis Bugtracker