Apologies if this is a duplicate...

Based upon the work done by quickstetch's options_element project, I created a patch for D7. This patch adds a new form element, 'options', and a host of helper functions.

This patch seems to work okay, though I haven't changed any parts of core to take advantage of the functionality yet. Left todo are:
1) Find places in core to use this
2) Figure out where to put the css file (currently it's added to /misc/ directory along with the js file)
3) Write tests

For reference, see:
#740396: Core patch?
http://drupal.org/project/options_element

CommentFileSizeAuthor
#11 options_elements.patch18.63 KBbcn
#11 options-element.js_.txt24.64 KBbcn
#11 options-element.css_.txt1.66 KBbcn
#11 add.png259 bytesbcn
#11 delete.png609 bytesbcn
#10 option-screen-radio.png38.82 KBbcn
#10 option-screen-checkbox.png40.66 KBbcn
#3 Screenshot-Options-element-test-with-keys.jpg43.4 KBbcn
#1 Screenshot-Options_element_test.png33.51 KBbcn
options_element_test_module.zip900 bytesbcn
options_element.patch42.89 KBbcn

Comments

bcn’s picture

bcn commented
StatusFileSize
new Screenshot-Options_element_test.png33.51 KB

Screen shot..

yoroy’s picture

yoroy commented
Issue tags: +Usability, +ui-pattern

Nice. tagging & subscribe.

bcn’s picture

bcn commented
StatusFileSize
new Screenshot-Options-element-test-with-keys.jpg43.4 KB

Screenshot of the other form state.

Again, this is all Nate's work, I mainly just copied and pasted from there to here.

amc’s picture

amc commented
Status: Needs review » Postponed

Seems like we should find a use case for this before it gets put into core. No need to add UI elements that we aren't using anywhere...

Please reopen this issue if there's general agreement on a particular place where this pattern is useful.

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Postponed » Needs review

Ehhh, this is in core.
Try adding a 'List' field to a content type. You will have to enter a list of allowed values in a weird "key|value" pair. Then apply this patch (and clear cache).
The question is rather, whether this is still possible for D7.

amc’s picture

amc commented

Ah. Now I see where it could be used. Not sure if this is the best UI for it, though.

amc’s picture

amc commented
Issue tags: +Needs usability review

correcting tag

Bojhan’s picture

Bojhan commented

This should have a Seven theme on the background. and a in context example.

yched’s picture

yched commented

This would indeed be an ideal UI for the 'list' field types.

[edit: hm, except that the 'Default' checkboxes wouldn't fit in this use case. In Field API / Field UI, default values are configured in a different place]

bcn’s picture

bcn commented
Version: 7.x-dev » 8.x-dev
StatusFileSize
new option-screen-checkbox.png40.66 KB
new option-screen-radio.png38.82 KB

Then apply this patch (and clear cache).
The question is rather, whether this is still possible for D7.

Not really.. The patch doesn't actually change anything in core to make use of the new element. So in a practical sense, it's unlikely that there's time to get this into d7.

List module does seem like the obvious candidate, but there's a good deal of changes necessary to move away from the textarea & key|value method.

@Bojan Attached are some screen's with Seven, in a potential (but not yet coded) context..

bcn’s picture

bcn commented
StatusFileSize
new delete.png609 bytes
new add.png259 bytes
new options-element.css_.txt1.66 KB
new options-element.js_.txt24.64 KB
new options_elements.patch18.63 KB

Updated patch to latest code from options element module...

This patch also includes a dirty hack to the list module to test the options element.

Also note that I couldn't figure out how to get new files added to this patch, so they're attached (with an extra .txt extension) here and need to be dropped in the misc directory.

bcn’s picture

bcn commented
Status: Needs review » Needs work

forgot to change status... Needs work for the changes that need to happen in list.module

fizk’s picture

fizk commented

What's the progress with this issue?

Bojhan’s picture

Bojhan commented
Issue tags: -Needs usability review

I wonder too, I would still like this going in.

simon georges’s picture

simon georges commented

I suppose it's too late now that Feature Freeze has happened, isn't it?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Issue summary: View changes
Status: Needs work » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

smustgrave’s picture

smustgrave commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Since there has been no follow up in 3 months going to close out. But don't worry this can always be re-opened!

Thanks