Modify

Opened 6 years ago

Closed 5 years ago

#3218 closed enhancement (duplicate)

save selection somehow (like saving reports/queries is possible)

Reported by: anonymous Owned by: diorgenes
Priority: normal Component: TracWikiToPdfPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10

Description

it would be great if the selection could be saved somehow to regenerate with one click later on.

Attachments (0)

Change History (5)

comment:1 Changed 6 years ago by anonymous

can you elaborate on this, please.

comment:2 Changed 6 years ago by anonymous

I think this would be an excellent feature to add as well. What I assume they originally requested is the ability to save the definition of which pages are included in the PDF. For example, if you have a site that is used primarily for documentation of a project or system, it is nice to generate the documentation as a PDF for each release. However, for a large project, that PDF could include tens or hundreds of wiki pages, and creating that final document can be tedious with the WikiToPDF admin page. Most of us are OK doing this once or twice, but if it needs to be done monthly or weekly, we are going to get frustrated. If the definitions of the PDF created in the WikiToPDF admin page could, somehow, be stored somewhere, then not only do you save some people time, but you build in the ability to make minor variations on the same book/PDF.

So, without looking at the code or knowing how Trac stores extra data, it would be nice to have an extra form (say to the right of the WikiToPDF admin form) that lists saved book definitions. These could be loaded, modified, and subsequently saved. The user can then choose a previously defined book, or create a new book. When creating a new book, there would be an additional button at the bottom that allows one to save the book definition. Either an extra text field exists for the book name, or the save button pops up a dialog requesting the book name.

The report definition would be saved in the Trac database with the following fields: book name (used only for identifying different books), title, sub-title, version, date, selected pages (list in the order selected), type (PS or PDF), and possibly some information (managed by the system) about who created it, when it was last modified, and a revision--these might or might not be different from the fields at the top of the WikiToPDF form.

comment:3 Changed 6 years ago by diorgenes

I like your ideas and I have some ideas too, but I don't have much time.
I need more help and more developers.

Regards

Diorgenes F. Grzesiuk

comment:4 Changed 5 years ago by mvlcek

See issue #4616.

You store all the information on a normal wiki page:

  • title page with title and any information you want to have on it
  • header for the table of content
  • links to all pages that should be included in the book

Currently it just creates PDF, but I suppose, it is easy to have both ps and pdf links at the bottom of the page instead of pdf only. The patch is for the Trac 0.10 version, but it should be easy to adapt it to 0.11 if there is even anything to do.

Greetings
Martin Vlcek

comment:5 Changed 5 years ago by grigi

  • Resolution set to duplicate
  • Status changed from new to closed

Please follow ticket #4616.

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from diorgenes. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.