Opened 14 years ago

Closed 11 years ago

#334 closed Enhancement (Won't Fix)

AS - script file .scpt extensions and aliases

Reported by: Niteshade Owned by: timothy
Component: Colloquy (Mac) Version: 2.0 (Mac)
Severity: Normal Keywords: alias .scpt extension optional


At the moment one requires an ending of .scpt for Colloquy to recognise an applescript plugin and load it.

It would be nice if scripts where recognised if

  • the ".scpt" file extension was absent (the OS has older better ways for recognising an applescript, without resorting to messing up the file name with hidden file name extensions that may or may not be there...).
  • an alias to the file was used. For when the file is stored elsewhere (e.g. in an area of your hard drive that you regularly back up). At the moment you have to give aliases an extension of ".scpt" to get them to work. It shouldn't be that cryptic.


Change History (2)

comment:1 Changed 14 years ago by brennan@…

It might even be useful to accept text files also (i.e. .txt). If the file is recognised as text, it should be fed to the AppleScript? 'compiler' exactly as happens when you do (run script (choose file)), the resulting script object returned should then be treated in the same way as any other script object.

Note also that some scripts are applets or droplets. These will end with .app rather than .scpt Right now I can't think of a reason to load a droplet into colloquy, but that doesn't mean there isn't a good reason to do so. Certainly it might make sense to have an applet loaded into colloquy. (Probably some scoping issues to attend to, so that the instance loaded into colloquy is guaranteed to be the same as the one running in the applecript applet, or if not, that there is some way to hook them up to each other).

comment:2 Changed 11 years ago by Rinoa

  • Resolution set to wontfix
  • Status changed from new to closed
  1. We require extensions. The missing .scpt file could actually be a .js file and we couldn't tell the difference.
  1. We don't plan to fix this as we don't plan to support alias' for plugins. A symlink would work.
Note: See TracTickets for help on using tickets.