Re: Arguments expected by .setProperty() method on JSA collections ? (has)
Re: Arguments expected by .setProperty() method on JSA collections ? (has)
- Subject: Re: Arguments expected by .setProperty() method on JSA collections ? (has)
- From: jif <email@hidden>
- Date: Tue, 19 Jan 2016 21:51:55 +0000
>
> Nope. You're working on the fundamentally broken assumption that JXA's
> Apple event bridge has anything to do with Arrays or collections, or
> bears any resemblance to JavaScript objects, methods, or behaviors in
> general.
No. Not my assumption at all. These are functions which themselves expose their own public methods, the rest is syntactic sugar.
> In fact, I'm not even sure where you got getProperty from,
You should look directly at the public interface using the Webkit debugger - you can see there what actually lies behind the bracket syntax sugaring which you describe below.
These are public (not private) functions. Documentation is another matter - some of them are shown in the thinnish documentation, others can be seen in the reductions returned to the user in the Script Editor results panel.
All of them work exactly as theory would predict, with the exception of the .setProperty method on collection functions, which can be coaxed into at least producing some side effects, and returning no error messages, with Apple apps like TextEdit, but does seem generally at the very least a little off with functions returning collection references, though it works perfectly (and is the real process behind the bracket sugaring) with single objects.
More generally, I find JavaScript for Automation is a consistently useful tool, though one which has been through far fewer iterations of development so far than AS. It will improve to the extent that it is used, and if it is permitted to harvest usable feedback.
I do, of course, understand your real disappointment and exasperation that your own carbon-based offerings where not taken up, and I have no doubt that in some respects they were superior.
A lot of time has now passed, however, and by now a 'cui bono' question is inevitably raised by your continuing to sail so very close to the wind of 'not an answer'. Insistently jamming all technical questions with the same familiar schtick (about 6 endlessly repeated stock phrases) of 'it's all broken etc' does begin to lose its charm and fragrance after a while, and simply degenerates into an obstacle to the work of others.
Where you have an answer, do give one. Where you don't - no need to fret, we are all more than clear about your view already. You are more than entitled to it. But please don't go on jamming. It's becoming a slight embarrassment and nuisance. There are other things in life. We all lose some of our battles. The thing is just to move on.
jif
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden