Kara-Moon Forum
March 19, 2024, 02:23:17 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: You can go back to the main site here: Kara-Moon site
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Plugin names  (Read 3200 times)
sciurius
Sr. Member
****
Posts: 443



« on: February 19, 2016, 07:38:19 AM »

(I tried to add a comment to the blog, but that didn't seem to work)

What problems do you expect from calling plugins by their names (i.e. without @ prefix)?
One of the charms of plugins is that added functions look/behave like ordinary commands.
Logged
bvdp
Kara-Moon Master
****
Posts: 1436


WWW
« Reply #1 on: February 19, 2016, 04:30:48 PM »

(I tried to add a comment to the blog, but that didn't seem to work)

What problems do you expect from calling plugins by their names (i.e. without @ prefix)?
One of the charms of plugins is that added functions look/behave like ordinary commands.

Comments on the blog should work. I'll have to look at that!

I have the plugins working and can happily report no problems. Once the plugin is written one just calls it by its name. The "@" forms part of the name. So, we could have a plugin create (silly example) a new command called @VOLUME and it gets called just like any other MMA command. Of course, what @VOLUME does is entirely up to the plugin code.

Note that the @ is part of the name. Two reasons: it highlights the fact that this is in fact a plugin, not a native command; and it ensures that we're not overwriting the original command.

This release is very close. I'm tied up with other stuff for a few days, but I think that very early next week I'll be able to put up a developer tarball.
Logged

My online life: http://www.mellowood.ca
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.036 seconds with 19 queries.