-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spend at most a day researching higher-level publication pattern for Event system #9
Comments
We could do something similar to OSD and structure our events like this: var events = {
'NS1' : {
'handlers' : [NS1handler1, NS1handler2],
'events' : {
'event1' : [eventhandler1, eventhandler2],
'event2' : []
}
},
'NS2' : {
'handlers' : [NS2handler1, NS2handler2],
'events' : {
'event3' : [],
'event4' : []
}
}
} Which allows us to handle events for an entire namespace. And you can raise events like 'NS1:event2'. |
Here is the article on which I based the annotation layer event system, after reading this little library, and the backbone events source code. And then there's the jQuery "custom" events, that, in theory, can use namespacing on objects |
I like the tiny pub/sub you link to since it includes the namespacing we want. I'm happy to go with that. I think it'll nicely address our issues. |
Okay. I pushed what I have for the workspaces this morning. I don't think On 6 May 2014 12:57, rsinghal notifications@github.com wrote:
|
Fix VideoViewer component tests Closes ProjectMirador#9 See merge request iiif/mirador-video-annotation!7
Objects (such as the workspace) may need to communicate with a third, higher-level object that affects objects horizontally in the hierarchy. How can we namespace events to allow this level of control?
The text was updated successfully, but these errors were encountered: