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

manandmouse

Members
  • Posts

    33
  • Joined

  • Last visited

Reputation Activity

  1. Like
    manandmouse got a reaction from Jim_A in Astute Graphics plugins for Affinity Designer   
    I also want this. Astute Graphics "simplify" paths is outstanding. We've been using this for vector images drawn with an iPad with a pen. It creates a lot of nodes and have to ve cleaned up. Their's tools is fantastic and I really want this in Affinity Designer. Or  Affinity could create better clean up/optimise tools themselves. 
  2. Like
    manandmouse got a reaction from k_au in Document layers - feature request   
    As it is now, a layer belongs to a page. In a publishing application, this is not especially useful. Layers should belong to the whole document. I.e:
    If a publication is done in 20 languages, a way to solve this is ta have common images and unique texts. Texts are placed in layers for each language. Enabling/disabling of the current language is easily done by switch a layer on/off. As Publisher is now, this is almost impossible. You would have to have all these layers on every page, and when export PDF, you would have to go over 100 of pages and switch the layers on/off.
    I'm surprised you missed this one. Publisher is a very good first edition. I've been using DTP for 30 years and many different systems and apps. Publisher finally lets me get rid of InDesign.But... you have to make some changes to make it really replace InDesign. I'm quite sure you will.
  3. Like
    manandmouse got a reaction from alexanderklar in Document layers - feature request   
    As it is now, a layer belongs to a page. In a publishing application, this is not especially useful. Layers should belong to the whole document. I.e:
    If a publication is done in 20 languages, a way to solve this is ta have common images and unique texts. Texts are placed in layers for each language. Enabling/disabling of the current language is easily done by switch a layer on/off. As Publisher is now, this is almost impossible. You would have to have all these layers on every page, and when export PDF, you would have to go over 100 of pages and switch the layers on/off.
    I'm surprised you missed this one. Publisher is a very good first edition. I've been using DTP for 30 years and many different systems and apps. Publisher finally lets me get rid of InDesign.But... you have to make some changes to make it really replace InDesign. I'm quite sure you will.
  4. Like
    manandmouse got a reaction from Krustysimplex in Document layers - feature request   
    This may be, as I said, a solution for a simple recurring layout. But take a minut to think about it: You have a 200 page catalog in 24 languages. Each page has it's own layout. That means that you must have 24x200 = 4800 master pages! This is not a made up example. I've been involved in productions like this over 30 years in DTP business.
    Global layers (or document layers) is not a strange thing. It's a very normal and good way to solve many different situations.
  5. Like
    manandmouse got a reaction from Krustysimplex in Document layers - feature request   
    As it is now, a layer belongs to a page. In a publishing application, this is not especially useful. Layers should belong to the whole document. I.e:
    If a publication is done in 20 languages, a way to solve this is ta have common images and unique texts. Texts are placed in layers for each language. Enabling/disabling of the current language is easily done by switch a layer on/off. As Publisher is now, this is almost impossible. You would have to have all these layers on every page, and when export PDF, you would have to go over 100 of pages and switch the layers on/off.
    I'm surprised you missed this one. Publisher is a very good first edition. I've been using DTP for 30 years and many different systems and apps. Publisher finally lets me get rid of InDesign.But... you have to make some changes to make it really replace InDesign. I'm quite sure you will.
  6. Like
    manandmouse got a reaction from Mofab in Document layers - feature request   
    As it is now, a layer belongs to a page. In a publishing application, this is not especially useful. Layers should belong to the whole document. I.e:
    If a publication is done in 20 languages, a way to solve this is ta have common images and unique texts. Texts are placed in layers for each language. Enabling/disabling of the current language is easily done by switch a layer on/off. As Publisher is now, this is almost impossible. You would have to have all these layers on every page, and when export PDF, you would have to go over 100 of pages and switch the layers on/off.
    I'm surprised you missed this one. Publisher is a very good first edition. I've been using DTP for 30 years and many different systems and apps. Publisher finally lets me get rid of InDesign.But... you have to make some changes to make it really replace InDesign. I'm quite sure you will.
×
×
  • 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.