hi,

no, i think there doesn't exist an out of the box solution in any other
webframework.

you have to implmenent a visitor, which uses the java-programming policy
and:
- manipulates the htmlattributes for "static" fields
- add an ajax-behavior for dynamic fields.

i will implement this policy and present my first solution in a few days.

so long... alex


Scott Swank wrote:
> 
> The chief problem in constructing pages with a consistent tabindex is
> that you must:
> 
> 1. Know from which parent component you are basing your numbering.
> 2. Handle ajax insertions of of components within your current
> tabindex strategy.
> 
> Our current code has edge conditions where it fails, and is on our
> short list of areas where we need  a redesign.  I am happy to work
> with anyone on creating a more robust solution.  Does anyone know how
> or whether any other web frameworks implement a tabindex strategy?
> 
> Scott
> 
> 
> On Mon, Feb 23, 2009 at 10:20 AM, Martin Makundi
> <[email protected]> wrote:
>> Here are some more scientific thoughts about it:
>>
>> http://www.mail-archive.com/[email protected]/msg26372.html
>>
>> 2009/2/23 alexander.elsholz <[email protected]>:
>>>
>>> hi,
>>>
>>> where is the difference?
>>>
>>> yes, the html attribute tabindex helps to define a focus-policy. so i
>>> can
>>> define a default policy and update the attribute with an ajax behavior.
>>>
>>> i think a problem is the amount of updated components, when tabindices
>>> changed because of business logic. her i could play with the index range
>>> 0-32767.
>>>
>>> i try to implement a panel-based strategy and present the result in this
>>> list.
>>>
>>> thanks alex
>>>
>>>
>>> Martin Makundi wrote:
>>>>
>>>> Do yu mean really focus or html tabindex?
>>>>
>>>> **
>>>> Martin
>>>>
>>>> 2009/2/23 alexander.elsholz <[email protected]>:
>>>>>
>>>>> Hi,
>>>>>
>>>>> had somebody implement a focuspolicy in wicket such as swings
>>>>> focustraversalpolicy?
>>>>>
>>>>> the policy should be analyzed in browser by default(a sorted list of
>>>>> wicket-ids) because of performance. In some cases we need
>>>>> business-code
>>>>> to
>>>>> evaluate next component. in this case we pass the determination via
>>>>> ajax-callback (getNextWicketComponentID) to server-business code
>>>>>
>>>>> Had somebody implemented this?
>>>>> Are ther some tips, how to implement this policy myself?
>>>>>
>>>>> thanks a lot alex
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Wicket-Focus-Policy-tp22165578p22165578.html
>>>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Wicket-Focus-Policy-tp22165578p22166754.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Focus-Policy-tp22165578p22200861.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to