Re: DatePicker is not appear properly
Thank you very much. After we implementing IWiqueryPlugin in base page and refer its jquery reference in renderHead method, the datepicker working fine.
Re: DatePicker is not appear properly
Hielke, Yes I know (in fact you will have it from wicket itself). But for 1.5.X is still a valid solution. On Tue, Sep 18, 2012 at 10:04 AM, Hielke Hoeve wrote: > Ernesto, > > Per WiQuery 6.0.0 IWiQueryPlugin is deprecated. Users have to add the > resources to the component themselves. > > > > From: Ernesto Reinaldo Barreiro [reier...@gmail.com] > Sent: 18 September 2012 08:47 > To: users@wicket.apache.org > Subject: Re: DatePicker is not appear properly > > Hi, > > If you mark a component on the page with interface IWiQueryPlugin the > wiquery will add jquery to you page (whether you use the date picker or > not) that way you will not have to add jquery manually. > > On Tue, Sep 18, 2012 at 8:29 AM, Madasamy Sankarapandian < > madas...@mcruncher.com> wrote: > > > Right now I'm migrating a application from wicket -1.4.x. to 1.5.8. > > > > We use wiQuery 1.5.7 (which depends on jQuery 1.6.4) in our project > mainly > > for the date picker component. > > We also use jQuery 1.7.1 directly. The jQuery resource reference shall be > > added in the "renderHead" method of our base page. > > > > This use to work fine in wicket-1.4.x (of course with the older wiQuery > > version) > > > > But wiQuery components (date picker) are not displayed after migrating to > > wicket 1.5.8. > > Please note that when a wiQuery component is used in a page, it shall add > > it's bundled jQuery reference to head. > > May be there's a conflict between the jQuery versions, which I'm not > sure. > > > > I also noted that in such cases, wiQuery's jQuery reference takes > > precedence rather than the one in my base page. > > May be the order in which the header contributions are added is causing > the > > problem? > > > > When I don't add jQuery-1.7.1 in my base page, wiQuery components are > > displayed properly. > > But we do need jQuery reference to be added irrespective of whether the > > page uses wiQuery components or not as we use some of the jQuery > functions > > in our pages. > > > > Instructing wiQuery not to add jQuery reference doesn't help either. > > > > > > -- > Regards - Ernesto Reinaldo Barreiro > Antilia Soft > http://antiliasoft.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
RE: DatePicker is not appear properly
Ernesto, Per WiQuery 6.0.0 IWiQueryPlugin is deprecated. Users have to add the resources to the component themselves. From: Ernesto Reinaldo Barreiro [reier...@gmail.com] Sent: 18 September 2012 08:47 To: users@wicket.apache.org Subject: Re: DatePicker is not appear properly Hi, If you mark a component on the page with interface IWiQueryPlugin the wiquery will add jquery to you page (whether you use the date picker or not) that way you will not have to add jquery manually. On Tue, Sep 18, 2012 at 8:29 AM, Madasamy Sankarapandian < madas...@mcruncher.com> wrote: > Right now I'm migrating a application from wicket -1.4.x. to 1.5.8. > > We use wiQuery 1.5.7 (which depends on jQuery 1.6.4) in our project mainly > for the date picker component. > We also use jQuery 1.7.1 directly. The jQuery resource reference shall be > added in the "renderHead" method of our base page. > > This use to work fine in wicket-1.4.x (of course with the older wiQuery > version) > > But wiQuery components (date picker) are not displayed after migrating to > wicket 1.5.8. > Please note that when a wiQuery component is used in a page, it shall add > it's bundled jQuery reference to head. > May be there's a conflict between the jQuery versions, which I'm not sure. > > I also noted that in such cases, wiQuery's jQuery reference takes > precedence rather than the one in my base page. > May be the order in which the header contributions are added is causing the > problem? > > When I don't add jQuery-1.7.1 in my base page, wiQuery components are > displayed properly. > But we do need jQuery reference to be added irrespective of whether the > page uses wiQuery components or not as we use some of the jQuery functions > in our pages. > > Instructing wiQuery not to add jQuery reference doesn't help either. > -- Regards - Ernesto Reinaldo Barreiro Antilia Soft http://antiliasoft.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DatePicker is not appear properly
Hi, If you mark a component on the page with interface IWiQueryPlugin the wiquery will add jquery to you page (whether you use the date picker or not) that way you will not have to add jquery manually. On Tue, Sep 18, 2012 at 8:29 AM, Madasamy Sankarapandian < madas...@mcruncher.com> wrote: > Right now I'm migrating a application from wicket -1.4.x. to 1.5.8. > > We use wiQuery 1.5.7 (which depends on jQuery 1.6.4) in our project mainly > for the date picker component. > We also use jQuery 1.7.1 directly. The jQuery resource reference shall be > added in the "renderHead" method of our base page. > > This use to work fine in wicket-1.4.x (of course with the older wiQuery > version) > > But wiQuery components (date picker) are not displayed after migrating to > wicket 1.5.8. > Please note that when a wiQuery component is used in a page, it shall add > it's bundled jQuery reference to head. > May be there's a conflict between the jQuery versions, which I'm not sure. > > I also noted that in such cases, wiQuery's jQuery reference takes > precedence rather than the one in my base page. > May be the order in which the header contributions are added is causing the > problem? > > When I don't add jQuery-1.7.1 in my base page, wiQuery components are > displayed properly. > But we do need jQuery reference to be added irrespective of whether the > page uses wiQuery components or not as we use some of the jQuery functions > in our pages. > > Instructing wiQuery not to add jQuery reference doesn't help either. > -- Regards - Ernesto Reinaldo Barreiro Antilia Soft http://antiliasoft.com
