Hi,
Intermediate result of the vote:
[1] +3, 1 veto
[2] +1, 3 vetoes
[3] +0, 3 vetoes
[4] +1, 0 vetoes
Matthias, I've attached below the description of the tomahawk solution.
I've come to like it, it brings our solution to Mojarra users and allows
for a more appealing interface and sensible defaults. Can you eventually
be convinced to withdraw your veto on [1]?
Best Regards,
Ganesh
tomahawk can bring it's own myfaces.js file that t:ajax builds on.
This solution does have a whole bunch of benefits:
- the optimization options become available to Mojarra users
- Mojarra Javascript bugs don't affect t:ajax users
- view options like disable (naming elements to disable while xhr
runs) and loadingbar (a turning snake to display while xhr is running)
can be integrated with t:ajax
- the options can be used naturally <t:ajax execute="..." render="..."
pps="..." disable="..."/>, no more need for a myfaces subarray
- defaulting can include pps="true" and queuesize="1"
- myfaces.js would include a function myfaces.ajax.request that is
triggered by t:ajax. The parameters of myfaces.ajax.request could also
be set up more naturally, the need for a myfaces subarray would drop
out: myfaces.ajax.request(execute:"..." render:"..." pps:"..."
disable:"..."), thus aligning the procedural and the declarative solution
