General developer forum

Hi Justin,

That looks awesome - thanks!

I'm going to submit a couple of Pull Requests for you shortly. Largely to add additional notes to the readme.

I notice that you're using this._config = config. One of the features that we're making massive use of in Atto is that of YUI Attributes. Every Atto plugin extends Y.Attribute which provides these. Rather than working with the config in the initializer, saving it, writing defaults, etc. you can instead add an additional object after your prototype which describes all of the attribute you wish to use, and their defaults:

Y.namespace('M.atto_NEWTEMPLATE').Button = Y.Base.create('button', Y.M.editor_atto.EditorPlugin, [], {
    initializer: function() {
        // Handle the button addition here.

        // Handle any other things which *must* be done on setup. Try to keep this to a minimum.
    }
}, {
    // We put the attributes here.
    disabled: {
        // We are not disabled by default:
        value: false
    },

    usercontextid: {
        // By default we do not have a usercontextid - it must be specified.
        value: null
    }

}
});

Then when you wish to use one, you can simply use:

this.get('disabled');

There are other handy features to attributes like setters, and getters. By default they lazy-load so that any expensive work isn't done until the first time that they're accessed. You can also define them as read-only, or writeOnce, and other such things. There's more information at http://yuilibrary.com/yui/docs/base/#attrsprop

Another feature of the new plugin system is that attributes are inheritted from the parent class (as you would expect). In the case of EditorPlugin there are only two at present (group, and host). You automatically have access to these in the same way - just use this to get the instance of the Editor itself:

this.get('host');

You can find documentation on those attributes at http://apidocs.moodle.org/js/master/classes/M.editor_atto.EditorPlugin.html#index

You can also access the attributes of the Editor itself too - see http://apidocs.moodle.org/js/master/classes/M.editor_atto.Editor.html#index for the list of options. The Editor instance is available to the plugin at this.get('host'), so you can access it's elementid (for example) with:

this.get('host').get('elementid');

Hope that this helps, and keep up the good work.

Best wishes,

Andrew

Hi Justin,

I get the plugin is not underway. I use Moodle 2.7.3 and renamed everything and let you install the plugin and it went well.
I have the plugin also added under the atto settings but if I get an editor open , I do not see the plugin. What is going wrong here?

I want to create a plugin that I have a style selections in the text " class" can give . So the stylesheet from my theme here style may grant .

greeting Edwin