Grayhem

Yes please this is needed - this is a feature in Figma [ design tool for mobile development ] in their corner radius section. Corner smoothing.
The problem with Figma is that when exporting an SVG with this corner smoothing applied, it doesnt respect the extra smoothing and just gives you the 'bog-standard' rounded corners. So all the nice smoothing is lost.

Affinity could be first to implement this? so that your extra smooth corners could be 'baked' into the paths.

+1      [ Is there any news on the progress or likelihood of this feature being included? Is this HARD feature to achieve?? ]

Yes absolutely agree - font organisation is such a missing thing in computers in general - for so long there has just been one long alphabetical list. Now at least we have favourites etc - but categories would be 'groundbreaking'  [... ie long overdue]

I would love to have the ability to create own categories for fonts and to assign my fonts to these categories.
Maybe I'm not the only one with a ridiculous amount of fonts . I design crafting paper sets for different themes and need several fonts for different purposes. For example I would create a category for handwritten fonts, for romantic fonts, for bold gothic fonts, and so on. Because of the vast amount of fonts (and no, I really don't want to miss one of them ) I have to go through the 100m long list of fonts, that are sortet alphabetically. I love that I can see what the fonts look like, but if I find a good one, I would like to assign it to a category for later reuse. And it would be great, if I could assign each font to more than one category. As this kind of thing is database based, it shouldn't be so hart to built this, I hope.
To the Affinity team: I love that you listen to the users. Many of the new changes in the actual beta version are things that used to annoy me, to. And I'm glad, you made it all better, this saves much time and a lot of klicking

I got V1. And I loved it.
I jumped onto V2 when it came out, allowing me to use the latest version on my Mac, my Windows desktop and my iPad, thinking I was making a great move forwards.
Then I discovered some of the people I know only have v1, and didn't make that leap, and quite simply aren't going to, because of their customers, friends etc.
After all, not everyone is a graphic designer, happy to spend on the latest software. I'm certainly not!
(And if I was in the V1 Camp, I'd be doing my best to discourage people thinking of going to V2, only to be left behind!)

Without some form of backward compatible export, I either have to keep files in V2 and then recreate them using V1, copying across the layers into new documents, or I have to try to put it into an interim non-Affinity format like a PSD, with even more compatibility issues than V2 to V1, which seems counter-intuitive when we all want to live in the world of Affinity!
Backward compatibility is something we all take for granted. Of course V1 files may not support all of the V1 features. Of course some things might be lost in the export. But backwards compatibility is something that not having, splits the world of Affinity users into 2 camps. V1's and V2's, and there's no easy way of sharing or collaborating.
Why ever would a company that rivals Adobe for having a wonderful graphical package choose to alienate existing customers, or restrict new customers in such a terrible way?
Please please please can we encourage Affinity to create a v1 exporter, so that we can share our V2 love with those left behind, and help support V1 users for continuing with the product until it's right for them to invest in the benefits that V2 can bring.
I can see 2 clear ways forward, both of which would show a united front for Affinity software:
1. An export from V2 to V1 compatible files
2. The ability for V1 to open V2 files in read only mode, to then be able to extract/copy the layers into new files.
Let us find a way for Affinity users to unite, share resources, and all grow together.

Yes please +1 

Save as version 1

Publisher 2.0.4 for macOS doesn't allow me to select objects on separate spreads - I can of course select objects on both pages in a spread, just like in v1.
And there is no need with v1 or v2 to pick on the page or pasteboard to let Publisher know which page you're working with. If page 1 is selected in the Pages panel and I click on an object on page 2, page 2 will become selected in the Pages panel. I can't see any changes from v1.
I'll have to step back since I'm on macOS and there are no crashes or lags with the Pages panel for Mac. Perhaps a Windows user that uses long documents could chime in here.
Cheers

Having a way to break down a project will be a very important step to allow collaboration. The elements contributing to a shared workflow would be:
- Splitting the project between modules (a book section), as atomic as possible (down to an 'H4' level).
- An effective way of managing and navigating through the building blocks (sort of an interactive ToC).
- Dynamic linking of texts in an AfPub document.
- Dynamic linking of images in an AfPub document.
- Preflighting/checking of error and coherence between all building blocks.
- Propagation of properties (color tables, text styles…) to all the building block.
This should make for an effective collaboration between writer, translators, page artists, illustrators, drawing artists, and the project manager.
Paolo
 

+1      [ Is there any news on the progress or likelihood of this feature being included? Is this HARD feature to achieve?? ]

Yes agree. Love this idea. Someone else posted about that here on this topic too:
 
 

That link doesn't seem to work anymore, but I'm interested in the scattering of vector based objects, and not pixel based.
Is that possible?

+1      [ Is there any news on the progress or likelihood of this feature being included? Is this HARD feature to achieve?? ]

I moved all office to Affinity, but we still pay Adobe for licenses because we're not able to export PDF files with non-printable layers form Affinity .
Today I'm sending another job to printers that has perforation marked on non-printable layer.
This is not just any feature but something that is used in print industry and professional printing every day.

Just being able to write Odd and Even in large letters on a non-printable layer can assist booklet production, no end.
It was a God send in PagePlus and I think the omission of this facility in Publisher is a huge failing on the designers part.  Please add a non-printable layers option to the next Publisher update.

If would be useful to have a no print option for layers, which should also prevent export. 
Many applications from using any object as a construction guide, to keeping notes about irritating clients. 

I also like to use the no-print setting for dielines and other guides when working on packaging etc. 
Please add that among other already suggested settings into an "Appearance" panel, as this is going to impact the ability to make print ready files greatly.

Back in the day, Serif’s vector drawing and page layout software had separate ‘Visible’ and ‘Printable’ settings, but several years ago they opted to go down the ‘if you can see it, it will print’ route, and they seem to have decided to continue with that approach. I personally think there’s something to be said for being able to specify that some layers should be visible at design time yet not included in the output, but I don’t hold out much hope for Serif choosing to revert to their old ways.

Yes, unchecking visibility in the Layers panel keeps a layer from printing. But it also cannot be seen. The request is to keep an item visible on screen, but suppress printing of that item.

It already is. This suggestion is to add it to the new screen so the welcome screen stays relevant after the first month of usage and isn't just disabled outright (plus if it's disabled you have to go to the File tab and then under recents to open the recent files, and there's no thumbnails. Sounds like this would be a major improvement)

Yes please this is needed - this is a feature in Figma [ design tool for mobile development ] in their corner radius section. Corner smoothing.
The problem with Figma is that when exporting an SVG with this corner smoothing applied, it doesnt respect the extra smoothing and just gives you the 'bog-standard' rounded corners. So all the nice smoothing is lost.

Affinity could be first to implement this? so that your extra smooth corners could be 'baked' into the paths.

Yes please this is needed - this is a feature in Figma [ design tool for mobile development ] in their corner radius section. Corner smoothing.
The problem with Figma is that when exporting an SVG with this corner smoothing applied, it doesnt respect the extra smoothing and just gives you the 'bog-standard' rounded corners. So all the nice smoothing is lost.

Affinity could be first to implement this? so that your extra smooth corners could be 'baked' into the paths.

For those who have long, text-heavy documents it would be enormously helpful if Affinity Publisher could import native WritePlus (*.stt) files. I hope Serif haven’t ruled out the possibility of adding such a facility. 

A feature that still gives Illustrator a slight edge over AF is the vector 'filters' and 'effects' - things that change the appearance of the vector paths [ which can then be 'expanded' into curves if need be.]

For instance there is a simple 'roughen' effect [or filter] that can be applied to the vector shapes in illustrator

Another example is the powerful feature of the 'transform' effect. see image

 
Any thoughts?

A feature that still gives Illustrator a slight edge over AF is the vector 'filters' and 'effects' - things that change the appearance of the vector paths [ which can then be 'expanded' into curves if need be.]

For instance there is a simple 'roughen' effect [or filter] that can be applied to the vector shapes in illustrator

Another example is the powerful feature of the 'transform' effect. see image

 
Any thoughts?

I like the ability to customize the tools pallet - however the changes do not carry over when reopening AD - How do I save it as the new default layout?