Hello.
Thanks a whole lot Shane. I was really wondering about this. My qualms with return types, is of course when the return types varies, which isn’t good practice, but which choose from list for instance uses anyway.
Hello.
Thanks a whole lot Shane. I was really wondering about this. My qualms with return types, is of course when the return types varies, which isn’t good practice, but which choose from list for instance uses anyway.
Hello.
I am at a loss,wondering about how I make scripting terminology for a handler that takes no parameters, if that is possible.
It doesn’t just work by leaving out the direct parameter definition, and any other parameter description. I hope I have overlooked something.
Most simplest form of a command is like:
<command name="command name" code="suitcomm" />
where the implementation is like:
on command name
return true
end command name
which should be used like
use script "name of library"
set x to command name
p.s. Tested and worked in Mavericks
Hello.
I can’t compile anything like that, maybe I am doing something wrong, (I get the message: Expected «given», «into», «with», «without» or other parametername, but found end of line) I am on Mavericks too.
use AppleScript version "2.3"
use scripting additions
use framework "Foundation"
use framework "AppKit"
(* ========== debug suite ========== *)
on milli secs
# from start
tell current application to set this_time to (its NSDate's timeIntervalSinceReferenceDate()) * 1000
return this_time
(*
if start = 0 then
return this_time
else
return (this_time - start)
end if
*)
# NSDate's alloc()'s init() to return ((its timeIntervalSince1970()) * 1000)
end milli secs
from the Cocoa Scripting documentation
Cocoa scripting will generate default keys for property and element attributes and for commands, if you do not specify them. For a property, it capitalizes each word of the property’s name except the first word, then removes any spaces. For an element, it specifies the plural of the element type. For a command, the default is NSScriptCommand
apart from that, the handler parentheses are missing
on milliSecs()
Hello Stefan.
Thanks for the input, I had a question earlier in this thread regarding parenthesis, and by the answer I got from Shane, I figured I couldn’t use parenthesis with a command that is supported with terminology.
Edit
I asked the question in post #9, and Shane answered it in post #11, (page 1 ).
The motivation, is of course to have the terminology load with the use script clause, so I won’t have to use a script object in order to utilize the commands, but can use them like I can with a scripting additions command.
For the record, the script bundle is named corelibrary, the sdef file is named corelibrary.sdef, the name in the bundle tab is corelibrary, and the id is net.mcusr.corelibrary. ASOBJC is enabled, and the sdef document a valid sdef/xml utf-8 document.
your sdef should have an empty command tag if it is really empty, I guess it uses libxml to parse the file because in libxml there is a difference between and . So you sdef should look like:
<?xml version="1.0" encoding="UTF-8"?>
apart from that, the handler parentheses are missing
Not when you use your own scripting definition, parentheses are not needed then.
sorry, I was wrong, forget the other post
Hello.
Thanks for answering DJ Bazzie Wazzie, I have tried that as well.
Hello.
Thanks for answering DJ Bazzie Wazzie, I have tried that as well.
At least it works on my machine only when you write an empty tag as otherwise it won’t work.
What I did was
on milli secs
return 0
end milli secs
Hello.
I have done what you have done, and I have also tried with/without use AppleScript version “2.3”
But it just doesn’t work. (I also added a title tag to the dictionary.)
Hello.
Restarting ScriptEditor and closing bundles with various earlier attempts , and “test scripts”, made sure of that there wasn’t any conflicting terminology around, and it worked!
Thanks
I did add "use AppleScript version “2.3” " in addition to following DJ Bazzie Wazzie’s receipe to the point.
At least it works on my machine only when you write an empty tag as otherwise it won’t work.
I’m a bit surprised by this. The reason is because I went back and looked at the sdef for ASObjC Runner, which does this very thing for several commands, and they all work fine.
Hello.
It’s surprising that you have to use an “empty tag” though, when there is nothing to be put inside the command tag.
Hindsightly I guess I had saved some hours if I had started out with AppleScriptObjC Explorer in the first place. I managed to wreak havoc with AppleScript Editor over the course, and I actually had to restart it, not only close the script bundle, which I had figured up front I never would have, as long as I didn’t add the script bundle to the dictionary library of AppleScript Editor. Now things are working great, and thanks for all your help and patience!
Edit
The main take away from me besides using “empty tags”, when there wasn’t any content to put within has been the cycle:
It’s surprising that you have to use an “empty tag” though, when there is nothing to be put inside the command tag.
UPDATE: It seems that once it compiled it doesn’t matter?
Looking further into this…
Hello.
I think I’ll just use what you call an “empty” tag, when there are nothing like direct-parameter and other parameters inside the command block. It’s a good rule of thumb, particularily, when Shane’s AsObjC Explorer creates such sdef definitions for such commands.
I think I may have really littered Script Editor in the process, but now the process is controllable again.
When there is no dictionary added to the library of AppleScript Editor, no script in the editor , that uses the library bundle I am editing in the editor; then edititing the sdef, saving the bundle, adding the handler, then compiling the bundle, and re-saving it works well!
This even works if I have to change words in the command or parameters, due to having used some reserved word, like “using” for instance, and re compile, works like a charm now!
I think I’m losing my mind here
Yesterday, behind the same machine I couldn’t compile your sdef file and when changed it into <command > I could compile it. When I set it back to tag it wouldn’t compile again just to make sure that it was the problem. And again when set to style it would compile. Because I was working with libxml2, and it does have a difference between these two (the check for empty tag will return true for <command > and will return false ), I assumed there is a difference for script libraries as well. But today I wanted to get the same “error” again and everything compiles just fine, even without extra saving. So I guess it has to do with some caching or something in the background.
Einstein once said: “Insanity is doing the same thing over and over again and expecting different results.”. I’m in doubt if I’m going insane or Mavericks :D.
It’s a good level of thumb, particularily, when Shane’s AsObjC Explorer creates such sdef definitions for such commands.
FWIW, I just use:
NSData *sdefData = [self.sdefXMLDocument XMLDataWithOptions:NSXMLDocumentTidyXML];
The only messing with XML I do is when I read in an existing sdef, in which case I turn all type attributes into elements, because it makes the interface simpler. And of course the table handles things like escaping reserved characters.
You young 'uns have it easy In the old pre-Mavericks days, the slightest mistake in an sdef would usually mean at least quitting and relaunching your editor. After much begging, sdef file modification dates are now compared and caches cleared if necessary.
I think I’m losing my mind here
Well it was you or me, so I’m happy
Hello.
I believe what ruined it totally for me yesterday, was having several scriptbundles, with almost the same terminology, and some driver scripts as well. I guess I managed somehow to trash the cache, but I am not looking back into it.
Next time I get serious issues, I’ll restart the Script Editor and take it from there.
Thanks for the tidy xml command Shane, I didn’t know it convert tags!