-
Notifications
You must be signed in to change notification settings - Fork 217
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
XBlock Scoping #219
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reported by @pmitros:
"NONE and ALL mean the same things, and expose our particular implementation details to XBlock authors.
Students may want to modify a course. Examples:
See:
http://en.wikipedia.org/wiki/Von_Neumann_architecture
http://en.wikipedia.org/wiki/Harvard_architecture
TYPE should be BLOCK_TYPE
DEFINITION and USAGE should be the same. The set of things which are overridable/advertisable should not be pre-defined by the XBlock author. Especially things like number of attempts can fall into either bin, and which makes more sense depends on how they are used. This is an artificial split due to architectural issues on our side, but it shouldn't be exposed to an XBlock author.
I can see there being something here, but not this. SCOPE could have an additional axis indicating something along the lines of whether something is mutable or read-only, or perhaps whether it ought to be versioned, or whether Big Things Happen when it changes (e.g. other chunks of state become inconsistent) or something, but I'm not quite sure what that is. I'm pretty sure it's not what we've got, though."
The text was updated successfully, but these errors were encountered: