Jump to content


  • Content count

  • Joined

  • Last visited

About kimtorch

  • Rank

Recent Profile Visitors

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

  1. So how do you handle these things now in your existing InDesign scripted workflow?
  2. I haven't had a lot to say here because - to be frank - we don't need Affinity Designer. I WANT to change to Designer, but we already run successfully with the Adobe products and can continue to do so. The point I'm trying to make is that Affinity need to persuade or entice existing ID scripters with a compelling reason to move. They're not going to do that by trashing everything they've invested in either Applescript or Javascript with ID. The other issue that people keep ignoring is inter-application scripting. I don't just want to script Affinity Designer - I want to talk to Filemaker, Mail, Capture One, Acrobat and any number of other scriptable applications. Just targeting your own app would b very shortsighted and really misses the point of what can be achieved with lateral thinking.
  3. Just because Adobe's implementation isn't great doesn't mean Affinity's won't be. This aside, the major thing that you're missing is the integration with other applications. For example, I can't use Python to access a Filemaker database and script that into AP (or ID). I can't easily tap into my Mail program or Capture One or Excel or my own apps. People tend to forget the cross application integration that Applescript allows. I'm not for a moment suggesting Applescript or Javascript (with which I have little experience) are perfect, but they *are* extremely practical and Applescript in particular allows far greater inter-application functionality than any other available language. This is something Affinity should consider - are they just going to script AP or are they going to allow functionality to be greatly extended with access to non-Affinity apps?
  4. lol indeed. Having used Macs since day one I'm not aware of any standard Mac app which supports python but literally thousands that support Applescript. I'm all for open discussion but I'd prefer it be realistic. As much as my preference is Applescript, I think the most practical would be javascript due to its cross platform nature. I believe either of these would be openly accepted by current InDesign scripters who already script in these languages. I believe Python would turn existing ID users off - it certainly would me as I don't want to learn yet another language. If Affinity do the syntax and object model right, a lot of existing ID code could even be reusable/transportable which would be a HUGE consideration to switching.
  5. Whilst I applaud 'thinking outside the square', I'm not sure whether this is applicable. Firstly, it appears to be Mac only which eliminates at least 50% of the potential audience. Second, it appears to still require the existance of Apple Events built into the appication (in which case it's already Applescriptable) and third, I'm not sure the sort of people who have the option to write apple or java scripts will be interested in writing them in Obj C. I'm not familiar with scripting bridges at all so might be completely wrong in my assessments but from briefly reading the supplied links this is what I was left with. The key point I came out with is that the application has to be inherently scriptable before the bridging can exist. But once again, maybe I have that wrong.
  6. I don't have a horse in this race but the company I work for has been printing/publishing for 98 years and stopped using picas around 25 years ago when we dropped hot metal. I'm not going to suggest AP shouldn't have 'traditional' publishing measures, just that I believe much of the printing/publishing world has moved on.
  7. I'm not suggesting for a moment they shouldn't do a full and complete library of scripting functions. I'd be disappointed if it was JUST basics. I'm simply saying a good starting point would be the fundamental functions I detailed above. I would, however be extremely disappointed if scripting was delayed because they were trying to build every obscure and little used functionality in before releasing it. Get some basic functions out early and build upon that. Getting AP to the level of a genuine ID competitor will take years but I certainly don't want to wait that long for scripting support. We are simply no chance of changing from ID to AP without scripting - it would cripple our workflow. If we could get the fundamentals I stated above we would be half a chance to move quite early.
  8. I have no experience with python but have extensive experience with Applescript and PHP scripting. I've written numerous standalone apps in BASIC plus we wrap a lot of scripts in BASIC apps so we can pipe data directly from mysql to Applescript. My preference would be Applescript but I understand they're not going to want to support two scripting methods for multiple platforms. My second choice would be BASIC but I think javascript makes the most sense. The best thing about choosing JS is that anyone with existing ID scripts will have a head start when looking to port them to AP. Our longest Applescript is 738 lines and I wouldn't look forward to rewriting it into a new language with a new object model. I would be happy to have a concise, targeted set of logical commands rather than trying to support every single feature of the app but making the scripting unnecessarily complex.
  9. I'd like to offer some brief suggestions of what I believe would be a good start for scripting support. Clearly both InDesign and Quark have extensive scripting libraries but I think with some basic fundamentals a lot can be achieved. I believe the below would allow us to do about 80% of what we need. Ability to create objects (text frame, image frames and rules) of specific sizes at specific co-ordinates using a list of properties. (set myFrame to create frame (x-coord, y-coord, width, height, colour, tint, border, name, columns, inset etc, etc) Ability to populate frames with text or images with ability to fit or scale as required (set story 1 of frame 1 to "myText.txt") Ability to assign styles to objects (set paragraph style of text frame 1 to "Heading 1") Ability to create new pages with properties for size, bleed, numbering, spreads etc Ability to reference selections (set border of selected frame to 0 - set style of selection to "Bold") Ability to export using defined PDF Presets (export to myPath with PDF Preset "My Preset") Ability to address (or loop through) all objects on a pages (set background of all text frames on selected page to "Transparent") Ability to test for missing or broken links to assets Ability to create colour swatches, character or paragraph styles, PDF Presets Ability to create and manipulate layers Most importantly, the ability to query for any property related to an object (set myProperties to properties of my selection -> list of all available properties) This is incredibly useful for writing and debugging.
  10. I'd like to congratulate the developers for what they've done. I'm sure they've spent many a long night trying to mould AP into a product suitable for public testing. You've done a great job getting to where it is now and I hope the sudden rush of bugs and features requests are seen as users desperately trying to help rather than an unscalable mountain of work. Enjoy what you've been able to achieve - it's probably better than I was expecting for a first release - well done.
  11. I hope so. Tagged text is incredibly useful and in many cases can substitute for many formatting scripting commands (style from the tagged text rather than setting text and then applying formats via script).
  12. Is this where you'd like Bug reports? I can reliably crash Publisher by selecting some text and then going to 'Expand' in the text menu - immediate crash with no error other than standard system 'the app has quit'. Happy to provide a crash log if you let me know where to send it.
  13. 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.