date:20130321

readering strategy of the 'head' section

2013-03-21 Thread Harrie Hazewinkel

Hello,


I recently upgraded from wicket 1.5 to 6. This is mostly not a real problem. 
However,
I believe that the complete change of the header render strategy is not 
compatible.
This is also mentioned in various places. Wicket 1.5 may not have been 
consistent
in for the header rendering, but why not trying to maintain some easy 
compatibility?


As Wicket 1.5 used a parent first render strategy, I can find still ways that 
Wicket 6
can support this. Why not supporting this in the applications settings either?

It eases upgrades of big projects and overcomes a way that there is a lot of 
code
to be added in Java. Wondering if more people believe a better support for the
ParentFirstHeaderRenderStrategy is wished for instaed of adding renderHead
code all over.


Or do I miss something?


Harrie
hhazewin...@gmail.com





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: readering strategy of the 'head' section

2013-03-21 Thread Martin Grigorov

Hi,

The change to use ChildFirstHeaderRenderStrategy by default was introduced
in 1.5.0. The usage of a system property to switch the strategy was
intentional - to make it harder. Wicket developers believe that
ParentFirstHeaderRenderStrategy should not be used.
But there was a bug that wicket:head didn't followed the rules. In 6.0
both Java and HTML contributions became more consistent.
Additionally now the application developer can promote the HeaderItems by
wrapping them in PriorityHeaderItem. Yet another way is to use
custom org.apache.wicket.settings.IResourceSettings#setHeaderItemComparator.

What is your usecase to prefer ParentFirstHeaderRenderStrategy ?






On Thu, Mar 21, 2013 at 9:55 AM, Harrie Hazewinkel hhazewin...@gmail.comwrote:

 Hello,


 I recently upgraded from wicket 1.5 to 6. This is mostly not a real
 problem. However,
 I believe that the complete change of the header render strategy is not
 compatible.
 This is also mentioned in various places. Wicket 1.5 may not have been
 consistent
 in for the header rendering, but why not trying to maintain some easy
 compatibility?


 As Wicket 1.5 used a parent first render strategy, I can find still ways
 that Wicket 6
 can support this. Why not supporting this in the applications settings
 either?

 It eases upgrades of big projects and overcomes a way that there is a lot
 of code
 to be added in Java. Wondering if more people believe a better support for
 the
 ParentFirstHeaderRenderStrategy is wished for instaed of adding renderHead
 code all over.


 Or do I miss something?


 Harrie
 hhazewin...@gmail.com





 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com http://jweekend.com/

Re: Wicket Ajax Debug Errors - how to debug?

2013-03-21 Thread Sven Meier


You can ignore it for now.

Thanks
Sven

On 03/17/2013 11:08 PM, Marios Skounakis wrote:

Did so - WICKET-5104 https://issues.apache.org/jira/browse/WICKET-5104

I still don't understand what the problem is. Despite the error things seem
to be working. Is it safe to ignore it, or should I find a workaround until
it is fixed?


On Sat, Mar 16, 2013 at 8:53 AM, Sven Meier s...@meiers.net wrote:


Seems like this is caused by WICKET-4959.

Please file a Jira issue.

Sven


On 03/15/2013 09:56 PM, Marios Skounakis wrote:


Hi all,

I am using a modal window as a substitute for messageboxes. E.g. I have a
few forms with an ajax submit button, and I am using the modal window to
first display a confirmation message, and if the user accepts it, to
display a success / failure message.

I am getting frequent errors in the Wicket Ajax Debug console. One is:
*
ERROR: *

Wicket.Ajax.Call.**processEvaluation: Exception evaluating javascript:
TypeError: Wicket.TimerHandles is undefined, text:
(function(){clearTimeout(**Wicket.TimerHandles['**spinner21e']); delete
Wicket.TimerHandles['**spinner21e'];})();

The spinner control mentioned above is an image component with an
AbstractAjaxTimerBehavior. In all cases of error, it has
setVisibilityAllowed(false) (it's hidden).

Usually the errors can be ignored and the page still functions normally.

I've never really dug into the way ajax responses are handled so I'm not
sure where to start in order to track this error down.

Any ideas?
Thanks in advance,
Marios



--**--**-
To unsubscribe, e-mail: 
users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket Application Design Question

2013-03-21 Thread Martin Grigorov

Hi,

I also recommend to use separate .js files for the different components.
I'd also prefer a Behavior to contribute some common JS logic like
validation. If a component needs validation then add this behavior to it.

Since 6.0 Wicket supports resource bundling, i.e. combine several .js or
.css files in one bundle.
Take a look at
http://wicketinaction.com/2012/07/wicket-6-resource-management/ and the
linked demo application.

JS world is also going in this direction.
Dojo as component based framework does this since its early versions. AMD
frameworks do the same. And they also provide bundling.
JQuery developers also realized this and now the split the bigger .js into
several smaller ones

On Thu, Mar 21, 2013 at 12:33 AM, Sven Meier s...@meiers.net wrote:

Wicket Application Design

Point your colleagues to the components in wicket-core and
wicket-extensions:
Is there a global .js file or many component specific ones?

*After* you've experienced performance problems, you should look into
ResourceBundles.

Hope this helps
Sven

On 03/20/2013 09:53 PM, xe0nre wrote:

Hello,

At my current place of employment we are using wicket for quite some time
and I believe that we are comfortable with it..but this days I had a
discussion with a colleague about the javascript files that we write for
our
components.We could not agree and I think that we can find the answer on
wicket forum.So here it goes:
I believe that because wicket is a component-based web framework the
javascript code that only applies to one component should be only loaded
when that component is being used.We have a global js file where I believe
that we can keep javascript code that can be applied in multiple places
like validation behavior for textfields.This way we also support component
portability.
My colleague believes that we should only use the global js file and
place
all our javascript code there.One argument witch i believe is true is that
one js file loads faster that multiple js files - but i think that this is
true only when you load all the js code in that multiple files.I think
that
if you only load what you need it cannot impact the page load time.
To give you a example of our problem: We have a component that handles
file
upload witch is only used in one place in the entire application. I think
that the js code that handles validation for this component should only be
used when the component is used.I see no reason the load the js code it
the
entire applications if it is only used on one page.
Any opinions are appreciated.

TL;DR: Should javascript code that is only used on one component/panel be
placed on a js file that is loaded only when component/panel is used or
on a
global js file that in loaded on every page.

--
View this message in context: http://apache-wicket.1842946.**
n4.nabble.com/Wicket-**Application-Design-Question-**tp4657388.htmlhttp://apache-wicket.1842946.n4.nabble.com/Wicket-Application-Design-Question-tp4657388.html
Sent from the Users forum mailing list archive at Nabble.com.

--**--**-
To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com http://jweekend.com/

Re: readering strategy of the 'head' section

2013-03-21 Thread Harrie Hazewinkel

Hello,


After the upgrade to 6.x I found that the order of the headers were reverse 
compared to 1.5.
This caused the com.googlecode.wicket.jquery.ui.form.datepicker.DatePicker to 
fail as it did not
wanted to display the popup to pick the date in a panel. The problem was that 
it depended on
common jquery that was added in a parent page. Then by using the 
ParentFirstHeaderRenderStrategy
this worked again and NO other code changes were needed.

But speaking of a general usecase, I see that you can then simply follow the 
page structure and panel
structure as how also the page inheritance goes and the panel inheritance as 
well. Common things go
in the parent page or panel and only specifics go into the page or panel itself.

Also what I found was that html header elements like 'title' were not place in 
the beginning of the
header anymore (which I believe is nicer to have it before javascript 
includes). A title element I mostly
added in the base page of my application of which all other pages inherited 
from.


Although, I do not understand why wicket developers (and I assume you mean the 
core developers and
not those developers using the framework) do not like a parent first strategy, 
I simply would say….
Wicket is modular and pluggable in many ways. Why would wicket developers force 
this to there users by
 not allowing it? Given the framework supports this almost already, leave this 
as a choice to the users to
select it as what would be the best for them.

Of course, a default implementation can be the preferred way of the wicket 
developers, but allowing users
there own choice.



Harrie


On Mar 21, 2013, at 9:20 AM, Martin Grigorov mgrigo...@apache.org wrote:

 Hi,
 
 The change to use ChildFirstHeaderRenderStrategy by default was introduced
 in 1.5.0. The usage of a system property to switch the strategy was
 intentional - to make it harder. Wicket developers believe that
 ParentFirstHeaderRenderStrategy should not be used.
 But there was a bug that wicket:head didn't followed the rules. In 6.0
 both Java and HTML contributions became more consistent.
 Additionally now the application developer can promote the HeaderItems by
 wrapping them in PriorityHeaderItem. Yet another way is to use
 custom org.apache.wicket.settings.IResourceSettings#setHeaderItemComparator.
 
 What is your usecase to prefer ParentFirstHeaderRenderStrategy ?
 
 
 
 
 
 
 On Thu, Mar 21, 2013 at 9:55 AM, Harrie Hazewinkel 
 hhazewin...@gmail.comwrote:
 
 Hello,
 
 
 I recently upgraded from wicket 1.5 to 6. This is mostly not a real
 problem. However,
 I believe that the complete change of the header render strategy is not
 compatible.
 This is also mentioned in various places. Wicket 1.5 may not have been
 consistent
 in for the header rendering, but why not trying to maintain some easy
 compatibility?
 
 
 As Wicket 1.5 used a parent first render strategy, I can find still ways
 that Wicket 6
 can support this. Why not supporting this in the applications settings
 either?
 
 It eases upgrades of big projects and overcomes a way that there is a lot
 of code
 to be added in Java. Wondering if more people believe a better support for
 the
 ParentFirstHeaderRenderStrategy is wished for instaed of adding renderHead
 code all over.
 
 
 Or do I miss something?
 
 
 Harrie
 hhazewin...@gmail.com
 
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 
 
 -- 
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com http://jweekend.com/

Harrie
hhazewin...@gmail.com





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket Application Design Question

2013-03-21 Thread xe0nre

Thanks for your answers .At this point we are using wicket 1.5.9 but plan a
switch to wicket 6.Maybe we well use resource bundling to improve
performace.

Thanks again



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-Application-Design-Question-tp4657388p4657398.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket Application Design Question

2013-03-21 Thread armandoxxx

From my experience use small component based .js and css files.

But just be careful and read the docs and references three times of how
wicket renders them to head !!! 
One tiny little advice about wicket:head tag .. just dost use it .. put
everything to renderHead() method in component class ;) 


Regards

Armando






--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-Application-Design-Question-tp4657388p4657399.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Adding to the existing AjaxBehavior of a component

2013-03-21 Thread eugenebalt

We have a large panel containing components with multiple Ajax behaviors.

In one context where this panel is used, we need to augment (add) the
existing AjaxBehavior of a certain component by adding extra functionality
to it. It seems that if we add it the usual way (add (new
AjaxComponentUpdating Behavior {..})), it breaks the existing Ajax behavior
defined previously in the panel.

Is there a way to plug into an existing Ajax behavior of a component
without replacing it, but adding to it?

Thanks



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Adding-to-the-existing-AjaxBehavior-of-a-component-tp4657400.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Wicket panel - call jQuery

2013-03-21 Thread mac

Hi,
I have a panel component containing
org.apache.wicket.extensions.markup.html.tabs.TabbedPanel(s):

Java (my component constructor):
ListTab tabs = new ArrayList();
...
add( new AjaxTabbedPanel( menu, tabs ) );

HTML:
div id=menu
   div class=tab-row
  ...
   /div
   div class=tab-panel
  ...
   /div
   ...
/div

I need to add a css class to tab-row and tab-panel selectors (by jQuery
I suppouse). 
I tried calling 
response.render( JavaScriptHeaderItem.forScript( $(#menu 
.tab-row).addClass(myClass);, someId ) );
inside myComponent#renderHead but without any success.

Maybe my way is not correct? Thanks for any help.

mac



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-panel-call-jQuery-tp4657401.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket panel - call jQuery

2013-03-21 Thread Ernesto Reinaldo Barreiro

try with DomReadyHederItem to see if you get a different behavior.

On Thu, Mar 21, 2013 at 3:44 PM, mac gmaci...@gmail.com wrote:

 Hi,
 I have a panel component containing
 org.apache.wicket.extensions.markup.html.tabs.TabbedPanel(s):

 Java (my component constructor):
 ListTab tabs = new ArrayList();
 ...
 add( new AjaxTabbedPanel( menu, tabs ) );

 HTML:
 div id=menu
div class=tab-row
   ...
/div
div class=tab-panel
   ...
/div
...
 /div

 I need to add a css class to tab-row and tab-panel selectors (by jQuery
 I suppouse).
 I tried calling
 response.render( JavaScriptHeaderItem.forScript( $(#menu 
 .tab-row).addClass(myClass);, someId ) );
 inside myComponent#renderHead but without any success.

 Maybe my way is not correct? Thanks for any help.

 mac



 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Wicket-panel-call-jQuery-tp4657401.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Regards - Ernesto Reinaldo Barreiro
Antilia Soft
http://antiliasoft.com/ http://antiliasoft.com/antilia

Re: Wicket panel - call jQuery

2013-03-21 Thread Jered Myers

I am not positive, but your selector appears wrong to me.  Try 
response.render( DomReadyHeaderItem.forScript( 
$(\#menu\).find(\.tab-row\).addClass(\myClass\);, someId ) );


On 03/21/2013 07:50 AM, Ernesto Reinaldo Barreiro wrote:

try with DomReadyHederItem to see if you get a different behavior.

On Thu, Mar 21, 2013 at 3:44 PM, mac gmaci...@gmail.com wrote:


Hi,
I have a panel component containing
org.apache.wicket.extensions.markup.html.tabs.TabbedPanel(s):

Java (my component constructor):
ListTab tabs = new ArrayList();
...
add( new AjaxTabbedPanel( menu, tabs ) );

HTML:
div id=menu
div class=tab-row
   ...
/div
div class=tab-panel
   ...
/div
...
/div

I need to add a css class to tab-row and tab-panel selectors (by jQuery
I suppouse).
I tried calling
response.render( JavaScriptHeaderItem.forScript( $(#menu 
.tab-row).addClass(myClass);, someId ) );
inside myComponent#renderHead but without any success.

Maybe my way is not correct? Thanks for any help.

mac



--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-panel-call-jQuery-tp4657401.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket panel - call jQuery

2013-03-21 Thread mac

Thanks, it workes perfectly.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-panel-call-jQuery-tp4657401p4657404.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

UrlValidator issue

2013-03-21 Thread Teresa Batista Neto

Dear all,

One of our users got an error message when trying to add a new URL:

'http://en.wikipedia.org/wiki/Genus_(mathematics)' is not a valid URL

I just created very quickly a junit test and it fails:

String[] schemes = {http};
UrlValidator urlValidator = new UrlValidator(schemes);
assertTrue(urlValidator.isValid(
http://en.wikipedia.org/wiki/Genus_(mathematics)));

Any ideas?
Teresa

Re: Adding to the existing AjaxBehavior of a component

2013-03-21 Thread Andrea Del Bene


Hi,

how does the additional behavior break the existing one?

We have a large panel containing components with multiple Ajax behaviors.

In one context where this panel is used, we need to augment (add) the
existing AjaxBehavior of a certain component by adding extra functionality
to it. It seems that if we add it the usual way (add (new
AjaxComponentUpdating Behavior {..})), it breaks the existing Ajax behavior
defined previously in the panel.

Is there a way to plug into an existing Ajax behavior of a component
without replacing it, but adding to it?

Thanks



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Adding-to-the-existing-AjaxBehavior-of-a-component-tp4657400.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Free Wicket guide now available!

2013-03-21 Thread Andrea Del Bene


Dear Wicketers,

I'm really excited to announce that, after almost two years of work (in 
may spare time), I've finished and published my free guide to Wicket!
You can find it at https://code.google.com/p/wicket-guide/. I've chosen 
to use Google Project because many of us have a gmail account that can 
be used to sign in and leave a feedback (for example opening an issue). 
The document is structured as a step-by-step tutorial and is released 
under Creative Commons license (CC BY-NC-SA 3.0). Unfortunately I didn't 
cover yet the topic of WebSocket, but I think that writing a chapter on 
it will be my very next step :).


Hope you find it helpful!

PS: feel free to contact me via mail. Any feedback is REALLY appreciated!

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: UrlValidator issue

2013-03-21 Thread Sven Meier


It seems UrlValidator chokes on parantheses.

Please open an Jira issue.

Thanks
Sven

On 03/21/2013 04:33 PM, Teresa Batista Neto wrote:

Dear all,

One of our users got an error message when trying to add a new URL:

'http://en.wikipedia.org/wiki/Genus_(mathematics)' is not a valid URL

I just created very quickly a junit test and it fails:

String[] schemes = {http};
UrlValidator urlValidator = new UrlValidator(schemes);
assertTrue(urlValidator.isValid(
http://en.wikipedia.org/wiki/Genus_(mathematics)));

Any ideas?
Teresa




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

39 matches

Mail list logo