to object styles.Ī style is just a collection of settings, where each setting can be set or System from char/paragraph styles to line styles, table styles, cell On our roadmap we have the extension of the current inheritable style So I think the concept is familiar and even expected by many users. Also, master pages have been used for at least a decade,
I'd like to know more about the consequences. This would be a big change indeed, best put somewhere down the roadmap.Ĭhristoph: Sounds complicated again, but who knows. Maybe Master Pages should be abandoned altogether, in favor of allowing all objects to have an attribute that allows them to appear on all pages, odd pages, even pages, or a list of pages. From experience I know that people learn things easier, when the concepts seem familiar. In this case it would just beīit different: applying changes to master pages. those that use the master page, single pages and range)Ĭhristoph: Again, this is just the extension of an already existing concept, ie, applying master pages to existing pages. Scribus would then bring up a dialog similar to the current "Apply Master Page" dialog. Once the editing is finished, the user would have to click on the edit button in the status bar again. There's one way to do it in a certain program (here: the many page features and layers), which can also be followed with other features (master Just remember the many questions regarding very basic operations. At least for experienced users.Ĭhristoph: No. Intuitive means one can figure out the feature by oneself, To disconnect an item from the master page and use it only on the current page, one could use the "Send to Layer" feature: Each document has at least one layer, so that sending the item to "Background" (or any other layer in the current document) should be enough to remove the item from the master page.Ĭhristoph: If properly documented, I think this would be rather intuitive, because it simply extends the concept of layers (see my reply to Greg). The user could set the degree (transparency) of the visibility. My idea was to edit a master page while the
#Atc 250r spark plug pdf
Default should be 0%, so that the content is invisible.Īvox: I don't follow your opacity explanation there.Ĭhristoph: Perhaps it is clearer if you download the PDF file that's attached to the original posting. There should also be a spin box to set the opacity of the actual page content, so that users can check how changes to the master page will affect the layout as a whole. When it comes to editing an item only on the current page, there should be a second button to switch on the editing mode for master page items on the currently selected page.
Again, technically the same as opening in the document outline, except that the user doesn't have to find out which master page is used for the current page.
Have a button beside the page list that would open the master page of the currently selected page for editing. This would have the same effect as selecting the master page in the Document Outline. List all master pages in the page list, so that the master page can be directly edited by selecting it in the list. Set a mark in both text and they will be set at the height of the later one (they could be set for the titles) Synchronise columns in side by side translated text Layout of a multilanguage flyer (same layout, partially adapted images, content may have small differences in length This table is still empty and will be until a working agreement is reached about the scenarios and proposals to solve them. The discussion about the future development of Master Pages Scenarios/Proposals Editing objects on master pages for one or more particular regular pages. 1.4 Another KISS way (the "prototype" approach).1.3.4 Tagging, Selecting and Batch Processing.1.3.2 Role of the scrapbook and enhancements needed.1.3.1 Features and limits of the Master Pages.1.3 Going the KISS way (the "Scrapbook" approach).1.2 Running summary from scribus-dev at.1.1.1 Editing objects on master pages for one or more particular regular pages.1 The discussion about the future development of Master Pages.
0 kommentar(er)
