Jump to content

Jon W

Staff
 View Profile  See their activity

  • Posts

    126

  • Joined

  • Last visited

Reputation

159 Good

See reputation activity

5 Followers

About Jon W

Profile Information

  • Gender
    Not Telling
  • Member Title
    Dev

Recent Profile Visitors

3,531 profile views
  1.    baoyu reacted to a post in a topic: Scripting
  2.    baoyu reacted to a post in a topic: Scripting
  3.    Alex Bogomolov reacted to a post in a topic: Scripting
  4.    Helianthropy reacted to a post in a topic: Scripting
  5.    Rudolphus reacted to a post in a topic: Scripting
  6.    Old Bruce reacted to a post in a topic: Scripting
  7.    Peter Werner reacted to a post in a topic: Scripting
  8.    MikeTO reacted to a post in a topic: Scripting
  9.    EricP reacted to a post in a topic: Scripting
  10. Jon W
    Jon W changed their profile photo
  11.    Frozen Death Knight reacted to a post in a topic: Scripting
  12. Jon W
    Hi @Peter Werner, I can confirm we are planning to add support for this. In addition to getting/setting metadata via scripting, we also plan to support setting metadata manually (likely by extending the Tags panel); this is useful for e.g. creating a template document containing placeholder objects which a script can then populate.
  13. Jon W started following Isometric setting off and on
  14. Jon W
    Hi @kimtorch. We are doing our best to engage with our users and understand their requirements. Our primary focus is to expose existing application features to scripts/plugins; text support is just one part of this. We are software developers, not publishers, and although we often liaise with the Publisher team regarding text matters, they are not really scripting experts. So you might have to explain some things that may seem obvious to you. We are aware of InDesign text tags: as I understand it, they are primarily used to map to text styles on import. What we're trying to understand, and I hope you can explain, is how this relates to scripting. I would guess that perhaps you envisage a script which would run as a tagged text import filter, overriding the tag -> style mapping which would normally be set up manually in the app?
  15.    Jon W reacted to a post in a topic: Scripting
  16. Jon W
    I'm happy to report that SDK development is progressing well. We are steadily working towards exposing enough app functionality to make useful plugins, but there's still quite a lot to do before we can consider even a "technology preview" release.
  17. Jon W
    Thanks everyone for all your suggestions - please keep them coming! They are all useful. Initially, we'll be concentrating on exposing existing functionality - primarily, manipulation of documents and their contents. Then later we will be able to move on to some of the "new feature" things that have been suggested: custom tools / shapes / brush engines / personas etc.
  18. Jon W
    Thanks for the explanation. Whilst dynamic layout is certainly an interesting idea, it's somewhat outside the scope of scripting itself - it would have to be considered as a completely new feature. Although we have no plans to allow general scripts to be embedded in documents (primarily due to security issues), if we were to add such a "dynamic layout" feature then I imagine we would use embedded scripts (with limited, layout-specific capabilities).
  19. Jon W
    We are planning to allow custom live filters at some point. It would be possible to write one that used GLSL.
  20. Jon W
    We have no plans for layer/object-specific scripts. However, scripts will be able to run in the background and respond to events such as "document changed". Could you perhaps give an example of how such a layer/object-specific script would be used in practice?
  21. Jon W
    We currently have no plans to allow customisation of existing tool behaviour. However, your wish could be easily realised by a script which performs the Expand Stroke command in response to a notional "object created" notification.
  22.    Jon W reacted to a post in a topic: Scripting
  23.    Jon W reacted to a post in a topic: Scripting
  24. Jon W
    Yes - please do all feel free to post your scripting-related feature requests here! Whilst we can't promise to implement them all, it would be great to get an overview of what our customers want and expect from scripting.
  25. Jon W
    This is the approach we are taking. In our world, scripts are just interpreted plugins, with the exact same capabilities as compiled plugins.
  26. Jon P started following Jon W
  27.    Jon W reacted to a post in a topic: Scripting
  28. Jon W
    This is indeed what we are hoping to do.
  29. Jon W
    The SDK will be fully documented. In fact we expect it to share documentation with our Javascript library, which is largely a wrapper for the SDK.
  30.    Jon W reacted to a post in a topic: Scripting
  31. Jon W
    In some sense yes, but the term "parametric" in the context of editing usually implies that parameters can be changed after the fact (e.g. live filters). Agreed. I agree that such a feature would be a good match for custom brush plugins, but still independent. You might like to raise it on the Feedback and Suggestions forum.
  32. Jon W
    As I said last week: we aren't ruling out built-in support other languages eventually, but we have no current plans to. However, any third-party "interpreter" plugins will have access to all the same capabilities as the built-in ones.
  33. Jon W
    Hi fde101, Thanks for your suggestion. Custom brush engines is an interesting idea and we've added it to our list. Pretty much how the existing brush engine works, unless I'm missing something? This sounds like a general feature request for parametric brushes, which would be equally applicable to the existing vector brush engine and not really specific to scripting.
×
×
  • 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.