[katello-devel] a followup form the demo

Tomas Strachota tstrachota at redhat.com
Fri Dec 7 09:37:28 UTC 2012


On 12/06/2012 05:09 PM, Dmitri Dolguikh wrote:
> On 06/12/12 04:08 PM, Bryan Kearney wrote:
>> On 12/06/2012 11:03 AM, Dmitri Dolguikh wrote:
>>> On 06/12/12 02:46 PM, Bryan Kearney wrote:
>>>> On 12/06/2012 09:45 AM, Bryan Kearney wrote:
>>>>> Dmitri:
>>>>>
>>>>> I did have one question. What would it take to get the fancy text
>>>>> editor
>>>>> (ace.ajax.or_ from foreman into the katello ui?
>>>>>
>>>>
>>>>
>>>> sorry ace.ajax.org
>>>>
>>>> -- bk
>>>>
>>>> _______________________________________________
>>>> katello-devel mailing list
>>>> katello-devel at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/katello-devel
>>>
>>> I think adding ace editor on the "new" screen should be pretty trivial.
>>> Show/modify might present an issue - since we somehow need to integrate
>>> with/mimic jeditable behaviour.
>>
>> Do we need to mimic it?
>
> if not the look, then behaviour: we need to send updates on focus
> change/timeout or something like that.

Do we really have to make it such complicated? Wouldn't a simple form 
and a save button be just fine?
We already use this approach on other places where we use ajax-saved 
jeditable for text inputs and more complicated elements are saved via 
classic forms.

>
>>
>>>
>>> How important is this?
>>
>> Not major, I notice that a big template does not look great. But, I
>> would prefer features over skinning now.
>
> Nods. Let's put it on the backlog? Perhaps mark it as "nice-to-have"
> feature?
> -d
>
>>
>> -- bk
>>
>>
>> _______________________________________________
>> katello-devel mailing list
>> katello-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/katello-devel
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel




More information about the katello-devel mailing list