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

Recommended Posts

  • Staff

Hi all,

The team has been making good progress. I don't have any updates on a release date but please be assured we are not sitting on our haunches - we want to get this feature out as much as you want it out!

Naturally we've been exposing more of the apps' functionality to scripts, but we've been working on plugin-specific technology too. For example, there's a new asynchronous file i/o and networking API, initially driven by the Javascript layer but then we thought it would be good for the lower level C/C++ plugins to have access too. Obviously with local and remote i/o, we've had to be careful that a script isn't covertly sending user data somewhere, so we've introduced a permissions system for Javascript plugins - unless you allow a particular script network access, it won't be able to use the networking API. It may not be a big shiny WOW! feature, but it's important to get these things right.

Anecdotally, I can tell you we've actually used some scripts internally to do some genuinely useful stuff that would have taken literally days to do manually. One script I wrote optimised a document and removed about 60000 layers. There have also been relatively simple layout and alignment tasks that scripts can munch through in the blink of an eye. Last week I wrote a script that split a pixel layer into new pixel layers containing the blocks of grouped pixels. Even the pixel processing was done in the script - I didn't have to rely on the app to do the heavy lifting for me because our performance is good enough to implement DBSCAN in Javascript.

Please be patient. We know you all want scripting available yesterday, but we're getting there!

Link to comment
Share on other sites

2 hours ago, Tim France said:

I don't have any updates on a release date but please be assured we are not sitting on our haunches - we want to get this feature out as much as you want it out!

Any progress report on this front is more than appreciated.

From what I know a lot of new development in inDesign is done in JavaScript, so I'm not surprised at all that JavaScript is performing so well in Affinity apps too.

2017 27” iMac 4.2 GHz Quad-Core Intel Core i7 • Radeon Pr 580 8GB • 64GB • Ventura 13.6.4.

iPad Pro (10.5-inch) • 256GB • Version 16.4

Link to comment
Share on other sites

Appreciate the work. Just to let you know that my ability to use Affinity Publishing is "do or die" based on Scripting.

I need to be able to

1 - swap the same master page into 100+ documents at once
2 - save "text version" of 100+ documents at once
3 - save "html version" of 100+ documents at once
4 - generate PDFs of 100+ documents at once

This will allow me to drop InDesign.

Speaking of which, it seems that "save as text" and "save as html" are currently not available? Therefore, that is a feature request, as well.

Otherwise, I am still bound to InDesign (which I don't want to be).

Thanks!

Edited by Daniel77
Link to comment
Share on other sites

@Frozen Death Knight We may have to wait a while for scripting to come to beta and then we will have more info about the controls for them. Hopefully we will know soon in what version it will become available. 

Lenovo IdeaPad 5 Ryzen 7 5700U Rx Vega 8 graphics 

16GB RAM (15.3 usable) 

Affinity Photo 1.10.6

Affinity photo 2 2.3.1 Affinity Designer 2 2.3.1 Affinity Publisher 2 2.3.1 on Windows 11 Pro version 23H2

Beta builds as they come out.

canon 80d| sigma 18-200mm F3.5-6.3 DC MACRO OS HSM | Tamron SP AF 28-75mm f/2.8 XR Di LD | Canon EF-S 10-18mm f/4.5-5.6 IS STM Autofocus APS-C Lens, Black

 

Link to comment
Share on other sites

On 11/18/2023 at 10:16 PM, Daniel77 said:

"save as text"

How would that work?  Do you just mean to export an individual story?

 

On 11/18/2023 at 10:16 PM, Daniel77 said:

"save as html"

From a DTP perspective HTML is essentially an eBook/ePub format, which has already been requested in other threads, such as:

 

Alternatively HTML could be a simple rich text format for exporting an individual story, which would be a different feature request from what people are usually asking for.

 

Either way, this is not the correct place for this - the thread this was posted in is about scripting.  If you are looking for the ePub style export of HTML, you should add your support in an existing thread for that.  If you are looking for a story export, there may be an existing thread requesting that but I am not turning one up in my initial attempt at searching.  If you meant something else by a text format export, I have no idea what that would be, but I would suggest searching for an existing thread and creating one if you can't find it, giving a bit more detailed of an explanation of exactly what you want from it.

Link to comment
Share on other sites

  • 2 weeks later...
  • 5 weeks later...

It's going to be javascript  right?     Wish it would rather be Python . ChatGPT seems so much more proficient with Python  while it took hours if not days to make it write you a working javascript for Photoshop.

 

We need scripting system that works  with ChatGPT nowadays  please.     With Affinity apps I am afraid it would be like persuading it to write you a script for 3d max  vs Blender   where ChatGPT instantly shines.

Link to comment
Share on other sites

I hope that this will make it into version 2 by September of this year.

Lenovo IdeaPad 5 Ryzen 7 5700U Rx Vega 8 graphics 

16GB RAM (15.3 usable) 

Affinity Photo 1.10.6

Affinity photo 2 2.3.1 Affinity Designer 2 2.3.1 Affinity Publisher 2 2.3.1 on Windows 11 Pro version 23H2

Beta builds as they come out.

canon 80d| sigma 18-200mm F3.5-6.3 DC MACRO OS HSM | Tamron SP AF 28-75mm f/2.8 XR Di LD | Canon EF-S 10-18mm f/4.5-5.6 IS STM Autofocus APS-C Lens, Black

 

Link to comment
Share on other sites

51 minutes ago, tzvi20 said:

I hope that this will make it into version 2 by September of this year.

Why - what’s happening in September?

Acer XC-895 : Core i5-10400 Hexa-core 2.90 GHz :  32GB RAM : Intel UHD Graphics 630 : Windows 10 Home
Affinity Publisher 2 : Affinity Photo 2 : Affinity Designer 2 : (latest release versions) on desktop and iPad

Link to comment
Share on other sites

I am going away and then I won't really have access to affinity for a long while. I want to be able to try out scripting once before then being that there is no release date or cycle yet.

Lenovo IdeaPad 5 Ryzen 7 5700U Rx Vega 8 graphics 

16GB RAM (15.3 usable) 

Affinity Photo 1.10.6

Affinity photo 2 2.3.1 Affinity Designer 2 2.3.1 Affinity Publisher 2 2.3.1 on Windows 11 Pro version 23H2

Beta builds as they come out.

canon 80d| sigma 18-200mm F3.5-6.3 DC MACRO OS HSM | Tamron SP AF 28-75mm f/2.8 XR Di LD | Canon EF-S 10-18mm f/4.5-5.6 IS STM Autofocus APS-C Lens, Black

 

Link to comment
Share on other sites

7 hours ago, tzvi20 said:

I am going away and then I won't really have access to affinity for a long while. I want to be able to try out scripting once before then being that there is no release date or cycle yet.

Have a nice trip.

AFAIK scripting will appear after v. 4.0 and it is about 2+ years

All the latest releases of Designer, Photo and Publisher (retail and beta) on MacOS and Windows.
15” Dell Inspiron 7559 i7 Windows 10 x64 Pro Intel Core i7-6700HQ (3.50 GHz, 6M) 16 GB Dual Channel DDR3L 1600 MHz (8GBx2) NVIDIA GeForce GTX 960M 4 GB GDDR5 500 GB SSD + 1 TB HDD UHD (3840 x 2160) Truelife LED - Backlit Touch Display
32” LG 32UN650-W display 3840 x 2160 UHD, IPS, HDR10 Color Gamut: DCI-P3 95%, Color Calibrated 2 x HDMI, 1 x DisplayPort
13.3” MacBook Pro (2017) Ventura 13.6 Intel Core i7 (3.50 GHz Dual Core) 16 GB 2133 MHz LPDDR3 Intel Iris Plus Graphics 650 1536 MB 500 GB SSD Retina Display (3360 x 2100)

Link to comment
Share on other sites

@tzvi20 You can be confused as much as you like, but it is not up to me. :)

All the latest releases of Designer, Photo and Publisher (retail and beta) on MacOS and Windows.
15” Dell Inspiron 7559 i7 Windows 10 x64 Pro Intel Core i7-6700HQ (3.50 GHz, 6M) 16 GB Dual Channel DDR3L 1600 MHz (8GBx2) NVIDIA GeForce GTX 960M 4 GB GDDR5 500 GB SSD + 1 TB HDD UHD (3840 x 2160) Truelife LED - Backlit Touch Display
32” LG 32UN650-W display 3840 x 2160 UHD, IPS, HDR10 Color Gamut: DCI-P3 95%, Color Calibrated 2 x HDMI, 1 x DisplayPort
13.3” MacBook Pro (2017) Ventura 13.6 Intel Core i7 (3.50 GHz Dual Core) 16 GB 2133 MHz LPDDR3 Intel Iris Plus Graphics 650 1536 MB 500 GB SSD Retina Display (3360 x 2100)

Link to comment
Share on other sites

On 1/10/2024 at 5:08 AM, Petar Petrenko said:

AFAIK scripting will appear after v. 4.0 and it is about 2+ years

And what do you base that on, given that it is one of the few items that Serif have actually said they're working on, and provided a demo of some working code?

-- 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.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3.1

Link to comment
Share on other sites

@Petar Petrenko Your comment confused me because Tim France's last comment implied that they want to get it out as it's ready. It does seem like they are pretty close to that point.

Lenovo IdeaPad 5 Ryzen 7 5700U Rx Vega 8 graphics 

16GB RAM (15.3 usable) 

Affinity Photo 1.10.6

Affinity photo 2 2.3.1 Affinity Designer 2 2.3.1 Affinity Publisher 2 2.3.1 on Windows 11 Pro version 23H2

Beta builds as they come out.

canon 80d| sigma 18-200mm F3.5-6.3 DC MACRO OS HSM | Tamron SP AF 28-75mm f/2.8 XR Di LD | Canon EF-S 10-18mm f/4.5-5.6 IS STM Autofocus APS-C Lens, Black

 

Link to comment
Share on other sites

21 minutes ago, walt.farrell said:

And what do you base that on, given that it is one of the few items that Serif have actually said they're working on, and provided a demo of some working code?

On some earlie Affinity's answers on the topic when they announceed it.

All the latest releases of Designer, Photo and Publisher (retail and beta) on MacOS and Windows.
15” Dell Inspiron 7559 i7 Windows 10 x64 Pro Intel Core i7-6700HQ (3.50 GHz, 6M) 16 GB Dual Channel DDR3L 1600 MHz (8GBx2) NVIDIA GeForce GTX 960M 4 GB GDDR5 500 GB SSD + 1 TB HDD UHD (3840 x 2160) Truelife LED - Backlit Touch Display
32” LG 32UN650-W display 3840 x 2160 UHD, IPS, HDR10 Color Gamut: DCI-P3 95%, Color Calibrated 2 x HDMI, 1 x DisplayPort
13.3” MacBook Pro (2017) Ventura 13.6 Intel Core i7 (3.50 GHz Dual Core) 16 GB 2133 MHz LPDDR3 Intel Iris Plus Graphics 650 1536 MB 500 GB SSD Retina Display (3360 x 2100)

Link to comment
Share on other sites

11 minutes ago, tzvi20 said:

...that they want to get it out as it's ready. It does seem like they are pretty close to that point.

And what do you base that on? Just on that last statement from Tim?

That just indicates that the whole is still in progress & in development state, so some more things do work now and have been in a state to be internally reused for certain tasks and tests. But it doesn't tell you how complete the C/C++ API interface and JS scripting engine is at all now, or when the whole is in a state to be released at all.

Further there is also much more than the coding things only named so far to do, namely the whole user & usage documentation of available API & JS functions (aka a concept overview, function list overviews, function explanations, various examples ...). - For developers the later said/named things here (writing the docus & user guides ...) takes in contrast to writing prog code usually more time to build & set them up in a manner, understandable and usable for end users at all.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

  • Staff
49 minutes ago, v_kyr said:

namely the whole user & usage documentation of available API & JS functions (aka a concept overview, function list overviews, function explanations, various examples ...

This.

The scripting devs are going to have to dedicate a significant amount of time towards documentation. We can't expect our docs team to document the ins and outs of an API (technically multiple APIs), it's simply not fair or realistic. Besides, we'd have to tell them what to write, which would mean pretty much writing the documentation anyway. Sure, they'll be able to present it in a way that looks good and integrated with the normal app documentation, but the devs are going to have to provide much of the content.

We're planning to use one of the many available documentation tools to do most of actual generation for us. The current favourite is Doxygen, largely because most of us have had at least some exposure to it.

Please remember too that the scripting team sometimes has to do bits of work away from scripting development. As the dev who wrote the DWG/DXF importer (and now exporter - see here 🙂), I tend to be the one tasked with its fixes and improvements. The same goes for Move and Shape Data Entry. Everyone in dev could put in those fixes, but it makes so much more sense if I do them because I'm most familiar with the code and should be able to do the work faster. The members of the scripting team do spend most of their time doing scripting work, but it's not 100%.

Link to comment
Share on other sites

@Tim France Thanks for letting us know how things are progressing. These comments are more than appreciated.🙂

Lenovo IdeaPad 5 Ryzen 7 5700U Rx Vega 8 graphics 

16GB RAM (15.3 usable) 

Affinity Photo 1.10.6

Affinity photo 2 2.3.1 Affinity Designer 2 2.3.1 Affinity Publisher 2 2.3.1 on Windows 11 Pro version 23H2

Beta builds as they come out.

canon 80d| sigma 18-200mm F3.5-6.3 DC MACRO OS HSM | Tamron SP AF 28-75mm f/2.8 XR Di LD | Canon EF-S 10-18mm f/4.5-5.6 IS STM Autofocus APS-C Lens, Black

 

Link to comment
Share on other sites

37 minutes ago, Tim France said:

The scripting devs are going to have to dedicate a significant amount of time towards documentation. We can't expect our docs team to document the ins and outs of an API (technically multiple APIs), it's simply not fair or realistic. Besides, we'd have to tell them what to write, which would mean pretty much writing the documentation anyway. Sure, they'll be able to present it in a way that looks good and integrated with the normal app documentation, but the devs are going to have to provide much of the content.

Exactly as I thought things will be, as it's always also the same for me here (although in/for other IT areas than graphics) and the dev projects I'm involved in. Or the other way said, from my own long time experiences as a dev I usually somehow know how the rabbit runs here. - Maybe no need to emphasize this, but as devs we usually like more to code than to overall write docs. But hey that's the way of cookie crumbles, somebody has to do the job and that's mostly the API inventors/implementers, as they know best how things have been implemented and how they do work.

37 minutes ago, Tim France said:

Please remember too that the scripting team sometimes has to do bits of work away from scripting development. As the dev who wrote the DWG/DXF importer (and now exporter - see here 🙂), I tend to be the one tasked with its fixes and improvements. The same goes for Move and Shape Data Entry. Everyone in dev could put in those fixes, but it makes so much more sense if I do them because I'm most familiar with the code and should be able to do the work faster. The members of the scripting team do spend most of their time doing scripting work, but it's not 100%.

That's also common usage in my domain, so even you are already working on certain longer time taking tickets, there's then mostly/always some other more urgently one pushing into the todo stack, which then has a higher importance/priority to be more urgently fixed (or to be implemented). So the overall processing sequence importance of to be worked on tickets will be reordered. - As said, it's a well known handling in many dev areas and you are all not alone here, I can sing a song about it too in my domain.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

26 minutes ago, v_kyr said:

That's also common usage in my domain, so even you are already working on certain longer time taking tickets, there's then mostly/always some other more urgently one pushing into the todo stack, which then has a higher importance/priority to be more urgently fixed (or to be implemented). So the overall processing sequence importance of to be worked on tickets will be reordered. - As said, it's a well known handling in many dev areas and you are all not alone here, I can sing a song about it too in my domain.

I worked under that model for many years in the past as well. It was constant painful frustration. Fortunately we finally moved to having feature teams that were off limits to other tasks. Productivity was much better without constant interruptions.

Link to comment
Share on other sites

1 hour ago, Tim France said:

Please remember too that the scripting team sometimes has to do bits of work away from scripting development. As the dev who wrote the DWG/DXF importer (and now exporter

Speaking of import/export, is there any news on whether there will be some form of text tags for scripting formatted text?

Link to comment
Share on other sites

@Tim France

Many thanks for the progress report.

> Naturally we've been exposing more of the apps' functionality to scripts

I hope the ultimate aim is to expose all the app's functionality to scripting. Can you say anything about that?

When you expose only part of the app's functionality you have to make a choice -- you'll always get it wrong.

 

Link to comment
Share on other sites

@Peter Kahrel if you are the author of "GREP in InDesign" I must say thank you for the great book.

All the latest releases of Designer, Photo and Publisher (retail and beta) on MacOS and Windows.
15” Dell Inspiron 7559 i7 Windows 10 x64 Pro Intel Core i7-6700HQ (3.50 GHz, 6M) 16 GB Dual Channel DDR3L 1600 MHz (8GBx2) NVIDIA GeForce GTX 960M 4 GB GDDR5 500 GB SSD + 1 TB HDD UHD (3840 x 2160) Truelife LED - Backlit Touch Display
32” LG 32UN650-W display 3840 x 2160 UHD, IPS, HDR10 Color Gamut: DCI-P3 95%, Color Calibrated 2 x HDMI, 1 x DisplayPort
13.3” MacBook Pro (2017) Ventura 13.6 Intel Core i7 (3.50 GHz Dual Core) 16 GB 2133 MHz LPDDR3 Intel Iris Plus Graphics 650 1536 MB 500 GB SSD Retina Display (3360 x 2100)

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.