Skip to content
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

Feature request: course structure browser/picker for selecting IDs #2449

Open
moloko opened this issue Oct 18, 2019 · 0 comments
Open

Feature request: course structure browser/picker for selecting IDs #2449

moloko opened this issue Oct 18, 2019 · 0 comments
Labels

Comments

@moloko
Copy link
Contributor

moloko commented Oct 18, 2019

Affected Area

I'm not quite sure of the name of it but it's whatever bit of the AAT that presents the author with configuration fields for plugins. Plus the .schema files.

Requested Feature

Add a proper type for 'the id of an object in the course structure' that could be used in properties.schema files to allow a content author to more easily select a content object/article/block/component.

It would do this by displaying a 'choose' button that, when clicked, would show a popup of the course struture allowing the learner to browse through it to what they want then select it, similar to how the 'file upload' control in HTML works.

Current Workaround

Currently if you're authoring something that requires you to supply the ID of an object from the Adapt course structure (start page configuration, for example), the user experience for doing so is a little clunky as you have to stop what you're doing, navigate to that item, copy its ID to the clipboard then return to whatever it was you were configuring to paste the ID in.

Additional Information

Might help #1752 as it could perhaps be done in such a way that obviates the need to store an actual ID; instead it could store a reference to the item in the structure and only look up and populate the ID at preview/build time...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants