[TYPO3-core] RFC: #undefined: Popup-functionality for Pages dokType=Shortcut

Steffen Kamper info at sk-typo3.de
Wed Apr 22 23:14:10 CEST 2009


Hi,

REMINDER # 3

vg Steffen

Steffen Kamper schrieb:
> REMINDER #2
> 
> vg Steffen
> 
> Steffen Kamper schrieb:
>> Hi Masi,
>>
>> Martin Kutschker schrieb:
>>> Steffen Kamper schrieb:
>>>> 400x200       => will open the page in popup with 400x200
>>>> ,120 300x50   => will open the page with type 120 using popup 300x50
>>>> ,118          => will open page with type 118
>>>> ,200 _blank   => will open page with type 118, target="_blank"
>>>> any_other     => same as before (target="any_other")
>>>
>>> The syntax for the page type looks odd and is incomprehensible (for
>>> editors). I think you can omit the comma and still determine the 
>>> intention:
>>>
>>> 400x200      => will open the page in popup with 400x200
>>> 120 300x50   => will open the page with type 120 using popup 300x50
>>> 118          => will open page with type 118
>>> 200 _blank   => will open page with type 118, target="_blank"
>>> any_other    => same as before (target="any_other")
>>>
>>
>> i stripped the comma so it's not needed anymore
>>
>>> Actually I think you could even allow an arbitrary order as seen with
>>> some CSS properties:
>>>
>>> <number>x<number> = window size
>>> <number> = page type
>>> <alpha><alphanum> = target
>>>
>>> So you could enter the more logical value of "_blank 400x200" into a
>>> field called "target".
>>>
>>> Masi
>>
>> would be nice, but didn't managed that for now.
>> It's not as important imho as the link values in typolink also doesn't 
>> allow an arbitrary order. So this context is exactly the same as in 
>> parameters for typolink.
>>
>> vg Steffen
>>


More information about the TYPO3-team-core mailing list