Jump to content

kimtorch

Members
  • Posts

    32
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. They chose what they believed was most suitable. As Adobe and Quark use Javascript - and as they're the closest competitors - it makes sense to have a language with which potential users would be familiar. I doubt they care what Blender etc use as they're not the users they're trying to attract. In all the software I use none uses Python, but many support javascript and/or applescript.
  2. It's encouraging to hear this and I want to thank TonyB (and Affinity) for putting it out there. At least we now have some glimmer of hope for the future. I'm happy enough with javascript as the language. It makes sense to have a single, cross platform language and with JS already available in InDesign, it means a lot of active scripters will have a head start. It will be interesting to see the syntax and object model - just imagine if a script which runs on InDesign could run on Publisher with only minor changes (similar to how Affinity works their magic with IDML files). I know it's fanciful, but it really would be magical! I'd love to have a rough time-frame but I expect that's asking too much. As mentioned elsewhere I'd be happy with some basics to get started and then build up the library over time. Having an API is also encouraging. I don't write C but I can imagine there will be an active marketplace for plugins if they keep to the low-cost Affinity model.
  3. If so, you will likely be able to afford hi-end software that can do the job for you the way you need. Right? Yes we can, and it's exactly what we do. You seem to be suggesting Affinity has no desire for our business and the way to resolve the deficiencies of their product is to use a different app. No problem, I'm sure they're happy for you to tell people not to use their software. I'd bet we're not the only media company who'd love to change but won't because they can't do the job we need.
  4. I'm beyond depressed reading this thread. I started it almost 4 years ago and there's been nothing but crickets... For mine there should be a few criteria for scripting: 1) it must be cross platform. I don't care if it's two languages (like InDesign) or one but clearly one would be better. I think the obvious one would be javascript but at this stage I'd be happy with even a basic Applescript library 2) it should be able to access non-Affinity apps (Filemaker, Access, Word, Excel etc). The real power of scripting comes from inter-app data sharing. Virtually everything we do with InDesign involves pulling data from our editorial or advertising databases. 3) it needs to be easy enough for a non-programmer to access. Whilst I'm now a programmer, I started my coding journey writing scripts and scripting should be easy enough for a novice. I can't believe people are suggesting every known programming language for simple scripting - some of which would be a terrible introduction to coding. Given the elapsed time, I think Affinity have given up on the idea of scripting. Sales data probably suggests their market is 'backyarders' so they're largely ignoring the commercial market where scripting is widely used. Ironically, if they had more advanced features they would probably make inroads into the commercial media space. I think not targeting large businesses is vastly underselling Affinity's potential. I believe if Affinity had serious plans for scripting they would announce it in a roadmap similar to how they announced the iPad products. You'd think if there was even an inkling it might be in the future there would be messages/surveys going to users - particularly users in this thread - about what might be desired. No, I think scripting is as good as dead and buried so discussion about languages is moot.
  5. As the OP, I'm amazed that nearly 4 years later there is zero information or progress on this. The second post in the thread suggest Affnity had plans for scripting but after 4 years there's nothing. As I've said before, I expect Affinity are happy for Publisher to be the 'backyarders' publishing program because without scripting it's unlikely to ever supplant InDesign in professional production environments. It's truly disappointing.
  6. I agree. In fact in the very first post of this thread I mentioned that tagged text goes hand in hand with scripting and needs to be supported for automated import of text. I'm not holding my breath for either. I don't think people or companies who use automation are the target audience of Affinity. They seem to be content serving individual users rather than businesses or companies.
  7. No, it doesn't work similarly for other modes. On the Mac the unit is only available in Resample. It may be a bug, but it definitely doesn't work on Unconstrained as Loukash's screenshot shows. And in Resample you can't do it with a single dimension, the 'crop' is constrained to a two parameter ratio. For people working on a few web images or designing small flyers or posters it may not matter too much but when you're producing hundreds of pages each week and you want standardised widths for all images this sort of thing makes a difference. It's also why the lack of scripting is such an issue for professional workflows. Ironically if scripting was available the cropping could possibly be worked around. AP is trying to compete with Photoshop so it needs to be able to do all the basics. Preferably do them better rather than not at all.
  8. The problem is exactly what you just described - I can't have an unconstrained crop in centimetres. An unconstrained crop should still be able to have one dimension - as Photoshop has had since I started using it circa 1992. AP doesn't allow this as it REQUIRES both parameters as detailed in my original post. I get you don't see it as an issue, that doesn't mean it's not an issue for others. It's a basic function which should be available if it expects to compete with PS.
  9. You can't ignore the height, you must enter a value if you want to use centimetres. The ONLY way you can have unconstrained crop is using pixels. It's annoying given all other measurements (rulers, transform etc) are all in Cms. It makes no sense to use multiple units when the user has chosen the one they want.
  10. Affinity Photo cropping is doing my head in. Here's what we currently do dozens of times a day in Photoshop. Open an image, set a width and a resolution in the crop tool. Leave the height blank. Draw our unconstrained crop box. Double click in the middle to crop. A few seconds, max. For the life of me, in Affinity Photo I can't find a way to replicate this process: 1) crop to a width only (seems you have to also specify a height) 2) have Unconstrained crop appear in Centimetres despite have Centimetres select as units in Transform panel. If I type 15cm into the Custom Ratio fields it simply reverts it to Pixels. I can't believe at version 1.9.2 the crop tool - one of the true fundamentals of photo editing - is so pathetic. I'll happily apologise if I've missed something and someone can explain how to do these things. This should be simple!
  11. This is the key - Affinity are working on the tools and forgetting about the result (getting the job done). Here's an analogy. I have a really nice Dewalt cordless screwdriver. It's a fantastic tool I enjoy using but if I had to screw in 5000 screws it wouldn't matter how good the tool is the job becomes slow, boring and uneconomical. This is why companies use robotics in manufacturing - it's essentially mechanical scripting. No matter how pretty and elegant the interface, I don't want to have to have to create 100, 500, 1000 PDFs manually. Or manually place images, create boxes, format text and export to our RIPS. We do these tasks thousands of times a week (literally). This is why Affinity Publisher is just pipe dream for us right now.
  12. It's been almost three years since my original post and not a word on progress or even possibilities from Affinity. Clearly automation isn't high on their priority list. I'd imagine if there'd been internal discussion at Affinity they would have reached out (maybe privately) to some of the people here who have vast knowledge and experience scripting publishing apps. Implementation and beta testing for a large scripting environment would be a huge undertaking and if it hasn't started now I have little faith it will be with us inside a couple of years. Sadly, I have little faith it's EVER going to happen. Looking back on what I said early on, I'd be happy to have ANYTHING - even the bare basics - just as evidence they actually might be doing something...
  13. I've given up on Affinity. I started this thread over two years ago with great hope of replacing CC but there's been zero input from Affinity regarding progress on scripting which gives me little confidence anything will be coming. It seems the primary market for Publisher, Designer etc is smaller agencies who might not benefit greatly from scripting. I continue to tweak our InDesign scripts and software every few weeks and I just can't see how we could survive doing everything manually. I'm retiring from the trade next year so it's not going to be relevant to me anyway, but it's a shame it doesn't seem to be on the radar of important features.
  14. We produce several hundred pages each week of the same size with the same columns (newspaper pages). I've made a custom sized page and created a preset but I can't see any way of applying column guides to the preset. Am I missing something or can you not have column guides on a custom page (preset)?
  15. Not much to add except "me too". It's actually the first thing I've tried on Affinity Photo and I had to go straight back to Photoshop bcause I was getting almost identical results to you with Invert.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.