being able to bulk change removes my objections ;-)
----- Original Message -----
It doesn't have to be an either or. I can add a checkbox at the
bottom that enables batch mode. Then I can switch the grid into
multi-select mode. Best of both worlds.
I will have to play with the behavior to see if I can get it to be
the same in single select versus multiple select.
On May 4, 2012, at 8:24 AM, Alan Santos wrote:
> Mazz - I think that's a fair point though I strongly favor the
> in-place editing.
>
> Mike - does this have to be an either/or choice? if the user
> selects multiple rows can the behavior remain the same? It would
> be nice if the collection interval, enable/disable buttons were
> only visible in the multi-select scenario to help make the use
> obvious.
>
>
>
>
> On May 4, 2012, at 11:17 AM, John Mazzitelli wrote:
>
>> I don't know about anyone else, but when I change schedules, I
>> almost always do it in bulk. either I want to bulk disable a set
>> of metrics, or bulk enable them (changing from 20 minutes to,
>> say, 1 minute - or the reverse). What happens if someone wants to
>> just disable ALL metric collection for a particular resource? And
>> what if that resource has lots of metrics?
>>
>> It just seems like we are getting rid of functionality that is
>> useful for no apparent reason.
>>
>> IMO, losing bulk editing is a big loss in functionality. We should
>> keep that ability.
>>
>> ----- Original Message -----
>>>
>>>
>>> Here is revised example of the in-place editing model that we
>>> would
>>> like to roll out to the editable grids.
>>>
>>>
>>>
>>>
>>> The first screenshot is the read-only mode where a row has not
>>> been
>>> selected.
>>>
>>>
>>>
>>>
>>>
>>> This second screenshot is a row being edited in-place. The
>>> changes
>>> are saved once the save (check) is clicked or Enter key pressed.
>>>
>>>
>>>
>>>
>>>
>>> Notably missing is the bulk edit feature (selecting multiple
>>> rows).
>>> The in-place editing model switches the grid into single
>>> selection
>>> mode so multiple rows cannot be selected. It is assumed that this
>>> model will enable edits quickly enough that a bulk editing model
>>> will not be needed.
>>>
>>>
>>> Feedback?
>>>
>>>
>>>
>>>
>>> -- Mike
>>> _______________________________________________
>>> rhq-devel mailing list
>>> rhq-devel(a)lists.fedorahosted.org
>>>
https://fedorahosted.org/mailman/listinfo/rhq-devel
>>>
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel(a)lists.fedorahosted.org
>>
https://fedorahosted.org/mailman/listinfo/rhq-devel
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/rhq-devel