Seneca

We need Publisher ASAP, thanks.  :)

We need Publisher ASAP, thanks.  :)

I'm not sure what you mean.
 
We don't need a dumbed down version of inDesign. We need a Desktop Publishing application that beats inDesign.
While inDesign may be daunting to you it's geared towards a professional market and we need a professional application to do that.
 
There is nothing near in the market at the moment that rivals inDesign for its depth etc., when it comes to professional publishing.
That's why we need Publisher to rival that and not something that dumbs it down.

1. I think macros are fine and they can do a lot to automate certain processes.
 
2. But we definitely need scripting to push the automation envelope further.
That goes particularly for Designer and later Publisher.
 
3. I also hope that Affinity is planning to expose their APIs so that we can write Plug-ins to go much further  (to infinity affinity and beyond!!!  :)).
Regards

Sorry, I wasn't doing it right. I got it now.

Can you please release the damn thing so that we can have our lives back.
Regards  :ph34r:  :)

Can you please release the damn thing so that we can have our lives back.
Regards  :ph34r:  :)

Slides on steroids!
 
I don't recall seeing so many options in the Slices Tab before, especially when you click on the triangle left to the name.
Have they been there before or is it a new addition to Beta 1.5 release? JSON? Wow.
 
That would merit a good video tutorial from the Affinity Team.  :)
 
Regards

I'm not sure what you mean.
 
We don't need a dumbed down version of inDesign. We need a Desktop Publishing application that beats inDesign.
While inDesign may be daunting to you it's geared towards a professional market and we need a professional application to do that.
 
There is nothing near in the market at the moment that rivals inDesign for its depth etc., when it comes to professional publishing.
That's why we need Publisher to rival that and not something that dumbs it down.

Frankly, I was very surprised that Affinity didn't think of implementing scripting in their applications from the beginning, particularly, since they developed common engine for all applications (Designer, Photo, Publisher) over the last 5 year. Surely, they know how popular it is in Adobe products. I don't want to second-guess why this happened. These guys are smart and know what they are doing. Having said that I would hope/expect/pray, (add your own words) for the following to happen:
 
1. DOM accessibility through a scripting language like JavaScript
2. Affinity to open up their APIs so that other small companies, resourceful users can fill the gap with features that Affinity doesn't want to support.

This should be reported as a bug on apple developer forums or simply filing a bug with apple directly.
Apple says they take all reports seriously  ;)

Thanks for Paragraph and Character Styles.
 
First a bug.
It happens when you want to update the Paragraph Style. Right-mouse click on the name of the style to get a pop-up menu to "Update Style from Paragraph.
The same crash happens when you access the same menu from the menu next to the name of the style and ask to Update the style.
 
There word Heirechical is misspelled on the Pop-up menu at the right of the Text Styles palette.
 
It's great to have such a feature rich styles as the initial release.
 
However, I think it would be great if you could also add:
 
1. Styles for a ruler above and ruler below.
2. Nested Styles
3. Grep Styles
 
I know you might want to include these 3 in the Affinity Publisher but it would be great to have them here as well.
 
I feel we should also have Show invisible Characters. This feature is invaluable for me when scanning text for double spaces, etc.
 
I'm not sure how the developers feel about adding Object Style to the mix.
 
This is it for now. I'm sure I will have more to say when I play with the Styles a bit more.
 
And of course a big thank you for this release.

Call it plug-ins or scripts, I would love to see something like that developed by Serif.
I hope that Serif will do a better job than Adobe, though.
 
Quite frankly I would standardise on JavaScript.
It would satisfy both mac and windows users and would prevent maintaining 2 languages by the plugin developers one for Mac and another for Windows platform.

MattP wrote: Is this such a frequent problem that it can't be worked around (i.e. by just making the artboard in the first place?)
 
I think this is a bit of an edge case.
I suggest we just wait for 1.5 beta and do the necessary nitty gritty there.
Best regards

Hello CartoonMike,
I think the community has given a lot of a lot of consideration and patience over the last 4-5 months.

Hello CartoonMike,
I think the community has given a lot of a lot of consideration and patience over the last 4-5 months.

People (including me) have been asking about scripting and plug-in development for Affinity. From what I've seen so far theres been no definitive word from anyone at Serif confirming or really denying that they are even looking at it. It's an important avenue to explore for the continued adoption of these products. I'd love to hear something from you guys about it. Is it even on the roadmap?

hifred,
You should expect that. This is a mac forum and not a mixed one.
I'm sure once the windows betas start to appear and there will be more mac-windows posts, things will change.
So far this has been a Mac only forum. Chill.
 
PS: Your example of 3D software proves nothing. I remember the time when all apps were written for Mac only as the windows was till a joke to use.  ;)  ;)

Try this.
 
You need to tweak some preferences on your Mac.
 
System Preferences -> Accessibility
 
Select Keyboard from the list on the Left
 
Click Open Keyboard Preferences (bottom)
 
Once then select Shortcuts from the top tab.
 
Select All Controls (bottom).
 
 
See whether this works for you.
 
Regards

That's a very good question quarki69.
I also think that duplicating the same background onto 3 or more parts is not the best way to go about it. But at the moment that the only way to do it.
I hope that when Master Pages are added to the Designer that should fix this issue.
Best regards

JGD,
 
Your logic would work if the Affinity products were on an equal feature-set with Adobe.
At the moment that's not the case so there is no need for any secrecy, etc.
That may change in the future of course.
 
An early community feedback on certain choices taken by the developers might prove to be of great benefit to them and us, who end up using the software.
 
But, this is only speculation on our part. But it does require bold thinking.

pullapooh- The icons should be updated to be prettier.
 
I couldn't agree more.

Hi rui_mac,
I don't think these two things should exclude each other.
We should definitely have a plug-in architecture mentioned by tomek as well as the facility to script the all the applications.
And you are absolutely right, this should be suit-wise.
Regards

I know that you're hard at work with on the other cornerstone of the Affinity suite - Publisher. And having seen the quality of your work with the other two applications I have no doubt that you've done your homework. But, when doing research on this sort of development project it is easy to lose sight of things that are not on the development map. It's also easy to dismiss ideas that go against the architecture or particular implementation details. And in the end it is what is useful to the intended end user that is actually more important than the internals of the software.
 
Hence I would like to start a thread where all serious DTP experts, professionals and advanced users could contribute ideas. In particular, features that have been long standing requested of other software but haven't been implemented.
 
Anyway, I await the first beta of Publisher with much anticipation and to get started here's my first request:
 
Enable plug-in architecture similar to InDesign which would allow a whole Affinity eco system to flourish while freeing the core team to concentrate on the important bits.
 
cheers,
-tomek

I would love to be an alpha tester for Affinity Publisher (to get my hand on it as soon as possible :-) ). I have a lot of experience in the publishing field (~30 years) and would love to contribute in any way I can to make the Publisher the platform of choice of a new generations of publishing tools.