Jump to content

Peter Kahrel

Members
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. The important part in ChatGPT's promise is 'analyze, learn'. Before it can actually generate working scripts it needs lots of examples, which must necessarily be written by humans. Compare with InDesign: when you ask ChatGPT for a JavaScript to do this or that in InDesign, it gives you an ExtendScript, not a UXP script, because there are zillions of ExtendScripts around and (by comparison) hardly any UXP scripts.
  2. Sounds very sensible, pleased to hear it. Can you say when there'll be something for us to play with? Thanks, Peter
  3. > Our priority for scripting is Photo and things like developing RAW files, adding meta data, . . . etc. > Creating documents and text processing is 'pretty', but it's of zero interest to us compared to the aforementioned raw and image processing which happens every minute of every day and is where the real time savings are. What complete nonsense. Processing text documents can be as time-consuming (or even more so than) whatever you you do in Photo. If you can't automate various typesetting aspects you'll lose a lot of time.
  4. > Those of us who would love to experiment with it early would send an invaluable feedback to the devs, which in my opinion is as important as the release itself. And those who love living on the edge would start using it early and learn what works what what doesn't. Absolutely. Good point.
  5. > I must say thank you for the great book. Glad to hear it!
  6. @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.
  7. That's why a road map of planned features would be useful. P.
  8. That's true. But in InDesign you could do footnotes 'manually' because you could script them.
  9. @GabrielM -- I don't have any particular project file, but it's easy to recreate. In a text frame, type xxx, press Enter/Return, and type zzz (but don't press Enter/Return). Now search .$ (any character at the end of a line). This expression should match first the last x, then the last z. But the last z is not found. Peter
  10. Well, yes, but the ones in Miscellaneous are toggles for panels, not text. P.
  11. Search results of expressions that use lookahead and/or lookaround aren't processed correctly. Search results are displayed in the Find panel, but they are not highlighted in the text and cannot be changed by a replacement text. This is the case with lookahead (?=...), the classic lookbehind (?<=...), and the modern, variable-length, lookbehind, \K P.
  12. Yes, confirmed. The matches are displayed but not highlighted. And i reported the bug. Looks like a general problem with location markers (lookarounds are a kind of location marker). P.
  13. That symbol is the section sign, it indicates the end of the story. P.
×
×
  • 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.