View Issue Details

IDProjectCategoryView StatusLast Update
0014153Scribus-public2016-07-27 09:17
Reporterale Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Product Version1.5.3.svn 
Summary0014153: remove the properties based table of contents
Descriptionit's a pain having to tell new users that scribus has a table of contents generator but

- nobody is using it,
- you're faster by typing the full table of contents,
- so don't use it.

indeed, i'm not aware that anybody has ever used the feature and i suggest to remove it from scribus.

if by chance a document has a table of contents defined, scribus should simply ignore it.

if the assumption is true that basically nobody has ever used it in production, people who eventually have used it will have to stick with an old version of scribus or redo their table of contents with styles.
Additional Informationcezary has a styles based TOC in scribus-ece.

having had a look at his code, it seems easy to add a stripped down implementation as a plugin.
TagsNo tags attached.
PatchNo

Activities

ale

2016-06-16 09:50

manager   ~0041664

of course, if somebody comes up with real use cases for a property based table of contents, we will have to keep it / re-implement it in a new table of contents engine.

please, write down such use cases if you know of any.

ale

2016-06-16 09:56

manager   ~0041665

yesterday evening, i've managed to create a stripped down plugin that collects all paragraphs with the styles "h1".."h3" and creates a table of contents with the page numbers.

it's missing an UI and it's not inserting the TOC in a text frame yet, but it works and it's less than 200LOC.

i'll publish it as soon as it can write the TOC in a text frame. (probably next friday)

despite being really minimal, i consider it (even with hardcoded style names) superior to the properties based TOC.

cbradney

2016-06-16 17:37

administrator   ~0041667

Properties based TOC is useful for items that do not use styles, remember, styles should not be mandatory.

The code that do we have now should not be thrown away. It will be useful for indexing, generating lists and other things based on properties.

ale

2016-06-16 20:26

manager   ~0041668

Last edited: 2016-06-16 20:30

expecting the use of styles for the table of contents (or the table of figures) is something that every software nowadays does.

concerning the use of frame's properties, i agree that in theory they are an interesting feature.

but i still fail to see any practical use case for it.

still, i would be delighted if somebody could show good uses for them!

cbradney

2016-06-16 21:08

administrator   ~0041669

Well I used them for my magazines when I was using Scribus for magazines.

ale

2016-06-19 16:30

manager   ~0041689

Last edited: 2016-06-19 16:31

i've created a very basic plugin, based on cezary's work:

https://github.com/aoloe/scribus-plugin-tableofcontents

for the short term i plan to

- test some corner cases,
- add a simple dialog for picking the h and toc styles for each level.

(currently, you have to define and use the h1..h3 and toc1..toc3 styles)

JLuc

2016-06-19 19:38

developer   ~0041691

MrB what do you mean with "Styles should not be mandatory" ? Why more than today properties ? If styles were the way to create a TOC, instead of properties, why not use them ?

Michael R.

2016-07-26 10:58

reporter   ~0041847

This function is also needed and also a function to generate in a easy way a toc from paragraph style or the headers from a long Text (like in LibreOffice). The possibility to do it now (scribus 1.4.6) is not realy usable. To create TOC for a book with a lot of chapters and title and subtitles is not possible.
Please Developer, if it's possible, make Scribus also usable for long textdocuments with a TOC and also to numbering images, table and diagrams automaticly (like in LibreOffice). A lot of people i know, would use Scribus more, if there is a better way to create TOCs and stuff you needed for scientific documents and books. Thanks a Lot
I will try the plugin above, but i ill be nice to have a easier way in a stable version of scribus, mayby version 1.6.

ale

2016-07-26 21:04

manager   ~0041849

michael, the plugin will be in 1.6.
promised.

this ticket is about removing the current way of doing the TOC. which you confirm is not really usable.

Michael R.

2016-07-27 09:17

reporter   ~0041853

So, thanks for the answer. I'm looking forward to test 1.6. Best regards from Thuringia/Germany

Issue History

Date Modified Username Field Change
2016-06-16 09:49 ale New Issue
2016-06-16 09:50 ale Note Added: 0041664
2016-06-16 09:56 ale Note Added: 0041665
2016-06-16 11:57 ale Description Updated
2016-06-16 17:37 cbradney Note Added: 0041667
2016-06-16 20:26 ale Note Added: 0041668
2016-06-16 20:30 ale Note Edited: 0041668
2016-06-16 21:08 cbradney Note Added: 0041669
2016-06-19 16:30 ale Note Added: 0041689
2016-06-19 16:30 ale Note Edited: 0041689
2016-06-19 16:31 ale Note Edited: 0041689
2016-06-19 19:38 JLuc Note Added: 0041691
2016-07-26 10:58 Michael R. Note Added: 0041847
2016-07-26 21:04 ale Note Added: 0041849
2016-07-27 09:17 Michael R. Note Added: 0041853