![]() ![]() When you review these notes in the future you might further enhance the information you captured. As you take notes, you can use OmniOutliner outlining prowess to logically group related items together. OmniOutliner is also a popular app for taking notes. This might include reviewing and updating your course outline, writing a summary of the course, and opening the course for registration. An OmniFocus project along the lines of “Prepare to Lead Course” would prompt you to take whatever actions are needed to prepare to lead the course. OmniOutliner documents can be used to store details that are helpful as you move projects towards fruition.įor example, if you were preparing to lead a course, an OmniOutliner document may contain details of what you’re sharing and how much time you’ll be spending on each section. OmniFocus is well suited to managing projects and actions but doesn’t tend to be the best place to house project support information. Drawing on this clarity, OmniFocus projects and actions can be created to bring your great idea to fruition. You can use OmniOutliner to capture and structure your ideas. As you go through this planning process you’ll likely find that your desired outcomes naturally emerge. If the opportunity was there, surely someone else would have seized on it.OmniOutliner can be very helpful if you have a great idea, but lack clarity on specific outcomes that you want to achieve and actions that will take you there. 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 |