I still for one try to get ajax away for public(unauthorized) parts,
for seo and caching purposes but it depends on the situation..
Timo Rantalaiho wrote:
On Mon, 18 Aug 2008, Patrick Angeles wrote:
Does it make sense to have outputMarkupId default to true for FeedbackPanel?
Use case:
Just making feedback panel write markup id doesn't mean your
application has to be all ajaxy...
-Matej
On Tue, Aug 19, 2008 at 8:25 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
I still for one try to get ajax away for public(unauthorized) parts, for
seo and caching
Hehe no completely true.. But it does generate more output.. However
dosent matter much for me what the default are.. as long as I can set a
property to control it:)
Matej Knopp wrote:
Just making feedback panel write markup id doesn't mean your
application has to be all ajaxy...
-Matej
On
It's kind of an established standard that by default,
outputMarkupId is false, so in 1.3 or 1.4 I don't see it
could be changed. Later on, if the change is made, maybe it
would be better to change the default for all Components and
not just FeedbackPanel.
+1 from me. I don't see any
Does it make sense to have outputMarkupId default to true for FeedbackPanel?
Use case:
somePanel.add (new OnChangeAjaxBehavior() {
protected void onUpdate (AjaxRequestTarget target) {
// do stuff,
Session.get().info (did stuff);
target.addChildren (getPage(), FeedbackPanel.class)
On Mon, 18 Aug 2008, Patrick Angeles wrote:
Does it make sense to have outputMarkupId default to true for FeedbackPanel?
Use case:
somePanel.add (new OnChangeAjaxBehavior() {
protected void onUpdate (AjaxRequestTarget target) {
// do stuff,
Session.get().info (did stuff);
