![]() ![]() (Sadly, I am highly allergic to subscription. Rather, I differentiate by length when assigning tags: short (20min) audio-visual inputs, because I build both differently into my workday. I don't listen to anything on the side while on the road. I do both on my computer, because I only listen to both at home with access to my computer. I sit down at my computer in both cases and take notes as I watch and listen.įor me personally, it doesn't even make a difference whether I'm listening to a podcast or watching a video. It is completely irrelevant to me at the action level. I have started to distinguish whether an audio-visual input is an interview or a lecture. The #tags should be instructive for the nature of the task. But if I prepare some difficult research object or prepare something over a long time, I like the infinite nesting of TaskPaper.īut it seems that TaskPaper will be my long-term storage for all of my research work and Things is more for the immediate and normal tasks (like watering the plants) It is: Areas, Projects, Tasks, Checklists. More difficult for me is that Things doesn't seem to allow very deep nesting. This is my (little) issue with things, too. Things3 is very "click-heavy" unless you learn the relevant keyboard shortcuts.Īh, thanks. If the opportunity was there, surely someone else would have seized on it.Yes. In the time since JavaScript for Automation was released, nobody else that I’m aware of has introduced a tool for it. I know this news is disappointing for those looking for better JavaScript for Automation tools - I’m sorry I cannot help. I don’t see a profitable opportunity with JavaScript for Automation. My experience with Script Debugger has taught me how incredibly difficult it is to build a viable business around automation tools. Script Debugger would need an entirely new debugging infrastructure, all of the code-building tools would have to be redone to support JavaScript, and I could go on and on. It may seem like something that can be easily added to the existing Script Debugger product, but that is not the case. This leaves me believing that there is no viable business for a JavaScript for Automation product. Try searching for JavaScript for Automation or JXA on and see what you find.Īpple’s Swift programming language was introduced at the same time as JavaScript for Automation and the difference in how Apple has promoted the two technologies is dramatic. There have been few improvements, no new documentation efforts and no promotion of the technology. Other developers are doing similar things, resulting in a vast array of JavaScript implementations based on different technologies.Īfter the initial release of JavaScript for Automation, Apple has not progressed the technology in any meaningful way. Unfortunately, the Omni Group is not utilizing Apple’s JavaScript for Automation. For instance, the Omni Group has done a fantastic job of integrating a JavaScript runtime environment directly into all of their products on the Mac and iOS. While there has been a lot of recent activity with JavaScript automation, both on macOS and on iOS, little of it has anything to do with Apple’s JavaScript for Automation. I can’t believe it’s been so long since Apple introduced JavaScript for Automation (JXA). I last dealt with this issue publicly back in December 2014. The short answer is no, we are not going to develop a version of Script Debugger for JavaScript. (Quark seems to be using V8, others JSC (JSContext) – which already looks like a technical challenge – and perhaps these embedded JS interpreters while fast, and without the JXA defects, are also rather out of reach for 3rd party tools ?) Perhaps some scope for SDJS there ? Or perhaps the costs/benefits/feasability of that still look unconvincing ? Safari debugging did work well for JXA for a while, but since some breaking change quite a while back (two OS versions, I think) (much radared, little attended to) probing the Automation interface of apps through the Safari debugger is now rewarded by nothing more than an instant crash. Some real unfinished areas in the JXA Automation API, combined with a heroically single-minded campaign of sulphur, brimstone, and worse, from Hamish, have protected the AS ecosystem a bit from that particular JS incursion, but I wonder what your current thoughts are about the future (given this newer pattern of app-embedded JS interpreters) and about the possibility of supporting JS-based app automation debugging in any way ? You have probably been around this issue a number of times, but it’s noticeable that cross-platform and other issues are now displacing the centre of macOS scripting gravity somewhat towards JS (OmniGraffle, OmniOutliner, soon OmniFocus, TaskPaper of long date, and now QuarkXPress 2018, which feels like a bit of a watershed).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |