Skip to content

Conversation

@fegemo
Copy link

@fegemo fegemo commented Aug 10, 2015

…bulletting

The motivation (#6) is to allow other plugins to conditionally disable the sub-steps created
by bespoke-bullets. For example, a new bespoke-keys plugin might want to register
a key to allow all bullets in a slide to be activated at once.

…bulletting

The motivation is to allow other plugins to conditionally disable the sub-steps created
by bespoke-bullets. For example, a new bespoke-keys plugin might want to register
a key to allow all bullets in a slide to be activated at once.
@markdalgleish
Copy link
Member

This is looking pretty good! I noticed some xdescribes in the tests, would you be able to enable those tests?

@mojavelinux
Copy link

I wonder if in general core should allow plugins to be enabled and disabled using events (or an API method). This might enable this level of control for all plugins (so long as plugins are developed to honor the request).

@fegemo
Copy link
Author

fegemo commented Aug 12, 2015

Hey @markdalgleish, my bad. I had forgot to implement those. I've just pushed a new commit.

@mojavelinux, I agree it would be a good idea to have standard events for activating/deactivating plugins on bespoke.js itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants