Re: Silva 2.2b1dev-r35291: KupuPopupWindow Field

On 22 Jul 2009, at 08:59, Marc Petitmermet wrote:

> On 22. Jul 2009, at 22. Jul 2009|08:36 Uhr, Kit BLAKE wrote:
>
>> Marc,
>> Sorry, this fell below the horizon:
>>> how do i get the KupuPopupWindow Field to pop up in the preview tab
>>> and the public view? i only get it popping up on the edit tab.
>>
>> The KupuPopupWindow Field requires javascript which is only present  
>> in
>> the edit screen.
>
> why? to enlighten me, can you tell me a use case for an author to  
> have a KupuPopupWindow in the external source?

The KupuPopupWindow is pretty tightly integrated with the External  
Source toolbox. But I can certainly understand (based on your use case  
below) why you'd like to have something similar.

>> This is if I'm interpreting your question correctly
>> (we usually call it the lookup window).
>>
>>> because of the above the below questions are more or less  
>>> theoretical.
>>>
>>> i don't want to show the kupupopup textarea on the public view only
>>> the kupupopup contentbox. i can probably do this with some css
>>> (.kupupopuptextarea {display:none;}), is there any other way?
>>
>> I don't understand what you're trying to do. Do you want the public  
>> to
>> use Kupu in the public view?
>
> yesss! i have the following use case: we have a yearly conference  
> here at the eth. people are allowed to submit a text-only abstract  
> of 300 words. until now i have used a TextAreaField. but people try  
> quite funny and strange things to "format" their input which we then  
> need to manually clean up. for the next conference i wanted to use  
> KupuPopupWindow to allow the participant to format their input and  
> spare us the manual cleanup. this would also result in nicer  
> abstract pages, booklets, etc.

I wonder if we could make a Formulator field that provides a rich text/ 
Kupu for a textarea.

>>> is there a possibility to disable the "get link reference..." button
>>> in the link tool box? on a public page i don't always want users to
>>> have access to the silva innards.
>
> in the above use case, i'd like to have the participant be able to  
> set a link to their research facilities home page.

Yes, the get link reference launches the lookup window, which is only  
meant to lookup Silva objects.

>>> the second time i click on the edit button, after saving inbetween,
>>> the selection of toolboxes made in the zmi is ignored; all are  
>>> shown.
>
> in the above use case this is a big problem.

This is happening in your public page? There's a cookie that holds  
that info, but again I think it's integrated with the edit screen.

Kit


-- 
Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051