Jump to content
You must now use your email address to sign in [click for more info] ×

Suggestio for far improved "Pages" Pannel


Recommended Posts

Hi

I just recreated a Document for my company that they use for our Architects, when they make Layouts for Beamer Presentations (most time the produce pdf´s)

I Found that they not only use the Masterpages for Structuring Layouts and Design elements, but especially , to Copy predefined Contend from the Masterpages because the Presentations mostly reuse Informations about our company, but also have to be flexible adopted.  So they just Copy paste what they need to the document pages.

So some suggestions from me. Realy not polished. Maybe some of the ideas doesn´t make sense, when i look deeper.. but it s open for discussion and maybe for an improved Pages Pannel for Publisher 1.9     :-)

  • Better Organisation of Masterpages with Categories and Subcategories
  • Ability to set Pathes on your Serverstructure for all users of a company, to load typical Masterpages from this location if needed .  Also the possibility to set such a path for all copys of Publisher when Installing the Software from our IT Team. ( So typical Users only load the app, and the pathes are allredy set to the right place...   also for Colors, Assets and so on good)
  • Drag and Drop of Masters as in the layers pannel of affinity Photo, to reorganise the Masterpages... Highly useful.
  • Set Colors for better recognicion of differing Categories or / And Masterpages.

Heres a Screenshot of a Mocup... i created.. 

Suggestion for Affinity Publisher Masters.jpg

Link to comment
Share on other sites

by the way...  just look on the viewportdisplay of pages and masterpages in Indesign..  its done very slick.. 

just by positioning the names of the masterpages in front of the masterpages, and organising the names of the real pages below, you     clearly  !!  see with one look what are masterpages, and which ar pages....

in Publisher all bleeds together and its difficult to see what are masterpages, and what are real pages... 

Come on Servif...     be superior..   i am sure.. here has to be done some polishing of the interface.... 

 image.thumb.png.84456f7c19811d22354284a80f1dc9e0.png

Link to comment
Share on other sites

2 hours ago, Tom Schülke said:

in Publisher all bleeds together and its difficult to see what are masterpages

I'm afraid I don't follow this one.

They are separated into two sections of the studio panel with separate scrollable areas with a header in between.

 

5 hours ago, Tom Schülke said:

Drag and Drop of Masters as in the layers pannel of affinity Photo, to reorganise the Masterpages... Highly useful.

This one I agree with.

 

5 hours ago, Tom Schülke said:
  • Better Organisation of Masterpages with Categories and Subcategories

Do people seriously use that many master pages in a single publication?

I had no idea...

Link to comment
Share on other sites

Hi fde101.. I also had no idea.  But i am not a specialist in this..  i got such a document from our PR Team..  so maybe this totaly doesnt make any sense, to use the Masterpannel as an Assetrepository..     i allready got elsewere the suggestion to just copy all this stuff directly to a templetefile.. which makes sense..   
To your first Point..

when you compare the Pages Pannel of Affinity to the one of illustrator,   Illustrator at the moment wins   hands down   when you look at the optical readability.. 

in Affinity Photo left..  all  pages have the same width,  look same,  only in the middle a tiny section separates the pages from the masters..  In Illustrator on the other hand..  with only one look you see what is what.. 


image.thumb.png.6b6c2bd16664576137953fdd916fed1b.pngimage.thumb.png.9ec7d2f6d28b1a8bfe18c20b654a7118.png

Link to comment
Share on other sites

2 hours ago, Tom Schülke said:

so maybe this totaly doesnt make any sense, to use the Masterpannel as an Assetrepository

If what you want is to use things as Assets, it seems more reasonable to me to simply store them as Assets, rather than trying to pervert the idea of Master Pages.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

10 hours ago, Tom Schülke said:
  • Better Organisation of Masterpages with Categories and Subcategories

> It can be interesting, yes

  • Ability to set Pathes on your Serverstructure for all users of a company, to load typical Masterpages from this location if needed .  Also the possibility to set such a path for all copys of Publisher when Installing the Software from our IT Team. ( So typical Users only load the app, and the pathes are allredy set to the right place...   also for Colors, Assets and so on good)

> Perhaps some preferences file log? Or you need to prevent users to mess/modify with those files later…

  • Drag and Drop of Masters as in the layers pannel of affinity Photo, to reorganise the Masterpages... Highly useful.

> +1. Creating/dupplicating some Master Pages can mess the order in which we want them

  • Set Colors for better recognicion of differing Categories or / And Masterpages.

> No ! (Or different greys, but I can't work on a design with something colorfull around, it'll mess the ability to choose good colours if some other ones are near the pages).

 

2 hours ago, walt.farrell said:

store them as Assets

Unless the assets stay in the file, (and this should be called a project, not a document), having hundred of assets, and needing to export them or part of them when we need to give/send a file would be prone to error… Or they should be part of a new feature we need: the Archive/Export (file, fonts, linked resources, colour palette, assets, ???, etc.) one.

And we need the assets to be debugged (problem with dupplicated styles), perhaps with a magnifier, since it's difficult to reconize some assets (big ones for example, shown as icons), and giving long named isn't really usefull. That's why a lot of us put some objects in the canvas' margin: easy to see, easy to take if needed, easy to use as example too, good place to put tips.

 

My ID document that use the more Master Pages' got 24. But it's like a "mother" document, once some modifiable but repetitive parts are validated by the client, I export the 24 parts that'll be use for a book, and delete the unused MP in each part of the book. (That's faster than modifying 24 times thoses documents, and I can do it depending of the progress).

Link to comment
Share on other sites

14 hours ago, walt.farrell said:

If what you want is to use things as Assets, it seems more reasonable to me to simply store them as Assets, rather than trying to pervert the idea of Master Pages.

Well i allready understood now that the document i got ,  somehow was screwed up, and i translated it one to one to publisher without thinking to much about it.. 

I still would need for my purpose, to have some sort of "mother document", wich enables our architects to pick all the stuff, they need for making their presentation. 

logicaly , this for mee would now belong to the asset pannel..   But there i cant store whole pages and furthermore, i cant see what a page would look like, befor i would drag it to the scene.

So another suggestion was, just to leave in the master pages section only what belongs there, and to put into the real pages section everythin possibly nessesair for differing presentations... 

positioning in between colord blank pages, to get some optical feedback, when scrolling throug the document, to see the differing groups of pages available..

So our architects, just would drag and drop the pages to the beginning of the document in the order they need, and delete the rest...   

this at the moment makes sense for me...  

 

Link to comment
Share on other sites

Another point to keep elements in Master Pages or in a separate document on Pages: you can easily copy-paste and they'll be at the exact coordinates without needing to move them. That' important when you've got repetitive elements on pages, and that's why we use Master Pages, or pre-filled pages that we only need to change contents.

Your Mother document can be the one you mentioned, with blank or title pages with tips for sections/parts, or with only Master Pages with meaningful names if they're used to those names (using a new program and a new organisation can be difficult).

The only problem I saw in using separate documents or assets, is that you can't check if you applied the correct Master Page (you won't have a displayed Master Page's name), and if they need to "re-apply" it, or if someone check the file to ensure the graphical chart is respected, it'll be harder.

Link to comment
Share on other sites

  • Staff
On 1/25/2019 at 9:33 AM, Tom Schülke said:

Well i allready understood now that the document i got ,  somehow was screwed up, and i translated it one to one to publisher without thinking to much about it.. 

I still would need for my purpose, to have some sort of "mother document", wich enables our architects to pick all the stuff, they need for making their presentation. 

logicaly , this for mee would now belong to the asset pannel..   But there i cant store whole pages and furthermore, i cant see what a page would look like, befor i would drag it to the scene.

So another suggestion was, just to leave in the master pages section only what belongs there, and to put into the real pages section everythin possibly nessesair for differing presentations... 

positioning in between colord blank pages, to get some optical feedback, when scrolling throug the document, to see the differing groups of pages available..

So our architects, just would drag and drop the pages to the beginning of the document in the order they need, and delete the rest...   

this at the moment makes sense for me...  

 

Hi Tom Schülke,
The assets panel is just for storing assets (elements - not pages - you may use frequently on your projects). The Master pages are used to set/place repeating elements and/or layout structures (picture frames/text frames/headers etc etc) used along the document (you may have several masters depending on the complexity of the publication). The content itself is placed on regular pages. What's missing is some sort of page templates with pre-made/built layouts you may want to use frequently - those will come later in an upcoming version (eventually after Publisher's release).

Link to comment
Share on other sites

Hallo MEB,

thanks for your Answer.  Yes.. You are right.  I have without thinking about it, just reproduced a document comming from our PR appartment..  

to position about 40 Pages into the masterpages together with  alterning content..   , is realy screwing up the purpose of masterpages..  

 

Never the less, a funktion to load pagetemplates would be very much appreciated..  and if it will come later thats great news..   

greetings from Hamburg.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.