[TYPO3-core] RFC: TCEForms -- Group Field with one option does not have to be selected

[Benjamin Mack]

Hey olly,

thanks for the reply.

I agree with you, but it's mainly meant for selection fields where max. 
one item can be in the list anyway (e.g. GRSP). I wouldn't then consider 
it a different behaviour for the group since for the user it's a 
different element (a "group" box with max. 1 entry possible doesn't 
sound like a group to me ;-) - if you take it in real life, me as a 
person is not a group either).

Also, I was only curious about this behaviour because a client found it 
annoying in a "max-1-group-select" to select and then to delete the 
entry. Actually, I had another client a couple months ago on the support 
phone who didn't get that too, ("I click on "X" but the entry is not 
removed" -- "well, you need to select it first").
Anyway, when I started T3 administration I was annoyed by this as well, 
I remember.

So, I could go with this one:
* Keep behaviour for <select>s with a size bigger than one (TCA: 
maxitems > 1).
* Change the behaviour only for <select>s where the TCA is maxitems=1, 
like on the screenshots where you don't need to select the (only) option 
first.

I'd change the fix for that if that is okay with you.

So, for the screenshot to clarify things:
* Current behaviour (select.png): where you need to select the item 
before you can delete it.
* New behaviour: (no_select.png): No need to select the entry before.
Hope that makes it clearer.


greetings,
benni.
-SDG-

www.xnos.de // www.xnos.org


Oliver Hader wrote:
> Hi Benni,
> 
> Benjamin Mack schrieb:
>> Branch: trunk
>>
>> Problem: If there is a TCE form "group" field with 1 item left and you
>> want to delete this item with the "X" remove button next to it, you need
>> to select it first, which is one click too much for people I think.
>> (example: if I'd want to delete the entry of the General Record Storage
>> Page, I'd need to select the field first and then click on "X", rather
>> than the X should do this directly).
>>
>> Solution: So let's make it more usable: You only need to select this
>> option in the <select>-field if there are more than 1 options in it.
>> Fairly simple.
> 
> For the technical functionality: +1 (works good and read the code)
> But I'm not sure if the behaviour for this individual case (only one
> item in selector box) is good.
> 
> If you use a file explorer on your OS you have to select a file first
> and then you can delete it. There is not feature that removes a file
> which isn't selected.
> 
> I imagine the situation while teaching a client how to use TYPO3:
> "If there are more than one item in a group, you have to select it first
> and then delete it. If there's only one, you can click right away on the
> delete-button."
> IMO the user will always select first and then remove, also if there's
> just one item. Just my two cents on that... ;-)
> 
> But, as written above, technically your patch is good and works.
> 
>> Sorry, I have two questions about this patch...
>> Question a) Is this a no-brainer / FYI?
> 
> No, because it changes functionality and behaviour.
> 
>> Question b) Should this go into 4.1 as well?
> 
> It's new feature, thus Trunk only.
> 
> 
> olly
-------------- next part --------------
A non-text attachment was scrubbed...
Name: no_select.png
Type: image/png
Size: 9521 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20071008/5d49a24c/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: select.png
Type: image/png
Size: 9619 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20071008/5d49a24c/attachment-0003.png