Graeme W

The main reason why Javascript is in the discussion is that this is what is used in InDesign and the other Adobe creative apps. Many of the people looking for scripting in Affinity apps will no doubt have built scripts in those and so using Javascript would make sense in that there would be an easier transition in that regard. I havn't used Quark in a long time (v6.5) so I have no idea what that uses other than just Applescript.
There are plenty of Javascript libraries out there, for example https://github.com/exif-js/exif-js - however, that is where the argument for Javascript does fall down in that because Adobe's Javascript implementation hasn't been updated in well over a decade you cannot actually use any Javascript libraries because they are all using newer features that break in Adobe's environment. For example when I built my last large InDesign script I needed something to write tests in - the best I could manage was getting 14 tests running in Jasmine before it would die.
I don't know Python but that's only because I have not yet had a need to learn it. If we get Python-based scripting in Affinity then great, I guess I will have a reason to learn it. I just feel like the focus really needs to be on making sure that whatever implementation is chosen gives us the depth comparable (or better) to that of InDesign as opposed to the half-assed implementation of Acrobat Professional.

For sure. I think I am looking at it from the point of view of workflow scripting that interacts with other software and files on my machine and probably remote servers. If you were looking at it from the point of view of coding graphics and page layout using a DOM like system without leaving whichever Affinity product you are in then javascript probably makes sense as most people with javascript experience that you will be getting to write code in your graphics apps will be coming from a DOM scripting background. I have to say that I'm already compromising by choosing Python though, Ruby is my favourite. 😅

The main reason why Javascript is in the discussion is that this is what is used in InDesign and the other Adobe creative apps. Many of the people looking for scripting in Affinity apps will no doubt have built scripts in those and so using Javascript would make sense in that there would be an easier transition in that regard. I havn't used Quark in a long time (v6.5) so I have no idea what that uses other than just Applescript.
There are plenty of Javascript libraries out there, for example https://github.com/exif-js/exif-js - however, that is where the argument for Javascript does fall down in that because Adobe's Javascript implementation hasn't been updated in well over a decade you cannot actually use any Javascript libraries because they are all using newer features that break in Adobe's environment. For example when I built my last large InDesign script I needed something to write tests in - the best I could manage was getting 14 tests running in Jasmine before it would die.
I don't know Python but that's only because I have not yet had a need to learn it. If we get Python-based scripting in Affinity then great, I guess I will have a reason to learn it. I just feel like the focus really needs to be on making sure that whatever implementation is chosen gives us the depth comparable (or better) to that of InDesign as opposed to the half-assed implementation of Acrobat Professional.

If we get scripting then it won't be Applescript. Pretty sure Apple EOL'd it years ago and besides it's not cross platform so would mean the devs having to spend their time on multiple scripting interfaces. 
We need scripting capabilities to rival InDesign and that is a lot of work to do so choosing a language that would suit every platform is a must. 

If we get scripting then it won't be Applescript. Pretty sure Apple EOL'd it years ago and besides it's not cross platform so would mean the devs having to spend their time on multiple scripting interfaces. 
We need scripting capabilities to rival InDesign and that is a lot of work to do so choosing a language that would suit every platform is a must. 

Agree with all, should be at document creation, should not need setting per-page or on a master page, and amount on each side should be linked by default (so I only type 3mm once), with an option to unlink them if needed. That's in addition to bleed being a visible guide off the page. This applies to Designer too, and I know visible guides of bleed has long been asked for there, so really hoping this can be done in one hit for all the 1.7 versions 

Hi,
first of huge fan of the fact that I can almost trow out my indesign. Props for Affinity!!
What I noticed when creating a new document in AFP is that you do not have the option to enter the amount of bleed you 
want on the document. 
 
This is to be found afterwards in under: File -> document setup -> bleed
would we nice to have this in the new document creation dialog as well
 

I can't imagine why setting up a new document that Bleed options are not there. 
Especially when choosing any of the Print setups. 
Can you please ensure this is included in the dialog box by default in File>New?

What also would be awesome is an publisher linux server client - which can use publisher files built on an windows/mac desktop - so a server can directly build pdf files out of these templates for Webservices

Hi guys,
 
I think Affinity is the future of design software. The one thing keeping me from switching from Adobe to Affinity is the scripting/automation feature. I have a bunch of scripts running in Photoshop and Illustrator and can't think about switching to Affinity and doing things manually again. You probably got this request earlier, but I'm just signaling the importance of automation/scripting in design software
 
I hope this feature will appear soon
All the best from Poland,
 
Sebastian from Keyshorts

Are there any plans to add scripting support?
I notice there is no Applescript library at all but am interested to know if there are plans to add Applescript or perhaps Javascript support. Virtually everything we do as far as creating PDFs, packaging, placing images and text, formatting, proofing, sending pages to print etc is done via script.
Tagged text goes hand-in-hand with scripting so I think this needs to also be supported.

Please add scripting support. Applescript would be nice but Javascript is even better because it can be used on both platforms. Please consider implementing the Ecmascript 2018 specs...  

@kimtorch
Welcome to the Serif Affinity forums
There are plans to add scripting to the Affinity range, but few details have been released yet.