A list of any. That's the best you can do.

If you know the type, by all means specify it.

Usually as any.

In script libraries, types are purely informative -- they don't actually do anything, unlike in apps and scripting additions. So just use common sense, and add explanations where you think they will help.

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.

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.

Applescript:

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

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.

Last edited by McUsrII (2014-11-04 10:39:39 am)

sorry, I was wrong, forget the other post

At least it works on my machine only when you write an empty tag as <tagname /> otherwise it won't work.

What I did was
1) create new applescript in script editor
2) save script as script bundle
3) a bundle inspector (drawer) appears, open it
4) create sdef file with plain text editor (sublime text)
5) drag & drop the sdef file inside the bundle
6) fill in the name (without extension) in the sdef field name in the drawer
7) save the file again
8) write the handler as below

on milli secs
return 0
end milli secs

9) compile (the handler should compile properly)

Last edited by DJ Bazzie Wazzie (2014-11-04 10:49:31 am)

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.

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:

1. Edit and save the sdef file.
2. Save the bundle.
3. Add your applescript handler to the bundle.
4. Save and test the bundle.

Last edited by McUsrII (2014-11-05 05:52:36 am)

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!

Last edited by McUsrII (2014-11-05 06:22:34 am)

FWIW, I just use:

Applescript:

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.

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!

Last edited by McUsrII (2014-11-05 06:25:47 am)

FWIW, one of the biggest caching gotchas is that the modification date check is done with the app or library, not the sdef file. Changing a file inside a bundle doesn't always change the bundle's modification date. Even saving over an existing bundle doesn't always change the bundle's modification date, either. So you need to think about doing something like touching the library.