Re: Wicket7: MediaComponent and Source classes
I also did changes in Wicket jQuery UI, all seems to be ok too, I will test further the coming days... On Tue, Jul 14, 2015 at 5:36 PM, Martin Grigorov wrote: > I have made the changes in Wicket Bootstrap and all seems to be fine! > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Fri, Jul 10, 2015 at 10:53 AM, Sebastien wrote: > > > Hi Martin, > > > > On Fri, Jul 10, 2015 at 8:35 AM, Martin Grigorov > > wrote: > > > > > On Fri, Jul 10, 2015 at 1:27 AM, Sven Meier wrote: > > > > > > > Yes, an overriden method with ART parameter will be something to be > > > > migrated :/. > > > > > > > > > We can try though! > > > > > > > > I've greped the Wicket's souce code once again, and only on*()- and > > > > respond()-methods kept their ART. > > > > All other 'active' methods (e.g. ModalWindow#close()) take a > > > > IPartialPageRequestHandler now. > > > > > > > > > > I've missed that ModalWindow#close() is changed too. > > > I'll do a grep as well. > > > > > > Since this change is done for Wicket then it should be done for other > > more > > > important UI libraries like Wicket jQuery UI, Wicket Bootstrap and > > > WicketStuff Foundation. > > > I suggest to postpone the release of Wicket 7.0.0 with few weeks until > we > > > make the changes and test them for few days. > > > WDYT? > > > > > > > +1, would be a wise decision... > > > > > > > > > > > > > > > > > > If it helps, I could create a pull-request for the relevant methods > in > > > > wicket-jquery-ui. > > > > > > > > Sven > > > > > > > > > > > > > > > > On 09.07.2015 22:32, Martin Grigorov wrote: > > > > > > > >> On Thu, Jul 9, 2015 at 9:23 PM, Sven Meier wrote: > > > >> > > > >> Ok. you're partially right :/ > > > >>> > > > >>> The compilation error would happen if an application extends > > > ModalWindow > > > >> and overrides #close(AjaxRequestTarget) method to do some extra > > tasks. I > > > >> have such code for Wicket Bootstrap's Modal component in one of my > > > >> applications. > > > >> > > > >> > > > >> #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) > > > > > > >>> Every application has to be recompiled as the method argument type > > has > > > >>> changed. But there won't be any compilation error. > > > >>> But for a migration to Wicket 7 each application will have to be > > > >>> recompiled anyway. > > > >>> > > > >> > > > >> The problem is that we probably won't find and change all possible > > > >> candidates for this change. And once 7.0.0 is out it will be too > late. > > > We > > > >> can try though! > > > >> > > > >> > > > >> > > > >>> Sven > > > >>> > > > >>> > > > >>> > > > >>> On 09.07.2015 20:11, Sven Meier wrote: > > > >>> > > > >>> Hi Martin, > > > > > > This is what I meant as too disruptive change. If we change the > > type > > > of > > > > > > > the parameter from ART > > > > > > > to IPPRH then every application that uses ModalWindow will have > to > > > fix > > > > > > > the compilation error. > > > > > > but ART *is* an IPPRH, so there will be no compilation error. > > > > > > If we broaden the API from #close(AjaxRequestTarget) to > > > > > > > #close(IPartialPageRequestHandler) then this will be an API > break. > > > > Every application will both at compile time and runtime. > > > > > > > > Nope, see above. > > > > > > Regards > > > Sven > > > > > > On 09.07.2015 16:35, Martin Grigorov wrote: > > > > > > Hi Sven, > > > > > > > > On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier > > wrote: > > > > > > > > Hi, > > > > > > > >> I've just changed all relevant places in Wicket from > > > AjaxRequestTarget > > > >> to > > > >> IPartialPageRequestHandler. > > > >> > > > >> I don't think this change is too disruptive: > > > >> > > > >> - client code can still call the existing methods with an ART, > > e.g. > > > > > > > > modalWindow.close(ajaxRequestTarget) > > > >> > > > >> What Maxim wanted as changes in Wicket jQuery UI are actually > > > >> changes > > > >> > > > > exactly like ModalWindow#close(). > > > > He needs to be able to close jQuery UI dialogs (non-modal window) > > > from > > > > WebSocket response. > > > > This is what I meant as too disruptive change. If we change the > > type > > > of > > > > the > > > > parameter from ART to IPPRH then every application that uses > > > > ModalWindow > > > > will have to fix the compilation error. > > > > > > > > > > > > - all places needing an ART remain unchanged, e.g. > > > > > > > >> AjaxLink#onClick(AjaxRequestTarget) > > > >> > > > >> It is not possible to click a link with WebSocket request so > > this > > > is > > > >> > > > > OK. > > > > The application developer can roll WebSocketLink if something >
Re: Wicket7: MediaComponent and Source classes
I have made the changes in Wicket Bootstrap and all seems to be fine! Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jul 10, 2015 at 10:53 AM, Sebastien wrote: > Hi Martin, > > On Fri, Jul 10, 2015 at 8:35 AM, Martin Grigorov > wrote: > > > On Fri, Jul 10, 2015 at 1:27 AM, Sven Meier wrote: > > > > > Yes, an overriden method with ART parameter will be something to be > > > migrated :/. > > > > > > > We can try though! > > > > > > I've greped the Wicket's souce code once again, and only on*()- and > > > respond()-methods kept their ART. > > > All other 'active' methods (e.g. ModalWindow#close()) take a > > > IPartialPageRequestHandler now. > > > > > > > I've missed that ModalWindow#close() is changed too. > > I'll do a grep as well. > > > > Since this change is done for Wicket then it should be done for other > more > > important UI libraries like Wicket jQuery UI, Wicket Bootstrap and > > WicketStuff Foundation. > > I suggest to postpone the release of Wicket 7.0.0 with few weeks until we > > make the changes and test them for few days. > > WDYT? > > > > +1, would be a wise decision... > > > > > > > > > > > > If it helps, I could create a pull-request for the relevant methods in > > > wicket-jquery-ui. > > > > > > Sven > > > > > > > > > > > > On 09.07.2015 22:32, Martin Grigorov wrote: > > > > > >> On Thu, Jul 9, 2015 at 9:23 PM, Sven Meier wrote: > > >> > > >> Ok. you're partially right :/ > > >>> > > >>> The compilation error would happen if an application extends > > ModalWindow > > >> and overrides #close(AjaxRequestTarget) method to do some extra > tasks. I > > >> have such code for Wicket Bootstrap's Modal component in one of my > > >> applications. > > >> > > >> > > >> #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) > > > > >>> Every application has to be recompiled as the method argument type > has > > >>> changed. But there won't be any compilation error. > > >>> But for a migration to Wicket 7 each application will have to be > > >>> recompiled anyway. > > >>> > > >> > > >> The problem is that we probably won't find and change all possible > > >> candidates for this change. And once 7.0.0 is out it will be too late. > > We > > >> can try though! > > >> > > >> > > >> > > >>> Sven > > >>> > > >>> > > >>> > > >>> On 09.07.2015 20:11, Sven Meier wrote: > > >>> > > >>> Hi Martin, > > > > This is what I meant as too disruptive change. If we change the > type > > of > > > > > the parameter from ART > > > > > to IPPRH then every application that uses ModalWindow will have to > > fix > > > > > the compilation error. > > > > but ART *is* an IPPRH, so there will be no compilation error. > > > > If we broaden the API from #close(AjaxRequestTarget) to > > > > > #close(IPartialPageRequestHandler) then this will be an API break. > > > Every application will both at compile time and runtime. > > > > > > Nope, see above. > > > > Regards > > Sven > > > > On 09.07.2015 16:35, Martin Grigorov wrote: > > > > Hi Sven, > > > > > > On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier > wrote: > > > > > > Hi, > > > > > >> I've just changed all relevant places in Wicket from > > AjaxRequestTarget > > >> to > > >> IPartialPageRequestHandler. > > >> > > >> I don't think this change is too disruptive: > > >> > > >> - client code can still call the existing methods with an ART, > e.g. > > > > > > modalWindow.close(ajaxRequestTarget) > > >> > > >> What Maxim wanted as changes in Wicket jQuery UI are actually > > >> changes > > >> > > > exactly like ModalWindow#close(). > > > He needs to be able to close jQuery UI dialogs (non-modal window) > > from > > > WebSocket response. > > > This is what I meant as too disruptive change. If we change the > type > > of > > > the > > > parameter from ART to IPPRH then every application that uses > > > ModalWindow > > > will have to fix the compilation error. > > > > > > > > > - all places needing an ART remain unchanged, e.g. > > > > > >> AjaxLink#onClick(AjaxRequestTarget) > > >> > > >> It is not possible to click a link with WebSocket request so > this > > is > > >> > > > OK. > > > The application developer can roll WebSocketLink if something like > > this > > > is > > > needed. > > > > > > > > > - a dozen Wicket components had to be changed to cooperate with > > > > > >> IPartialPageRequestHandler instead of just ART: > > >> find(IPartialPageRequestHandler.class) > > >> > > >> Those are good changes! > > >> > > > > > > If we identify other methods later, we can still broaden their > > > signature > > > > > >> to use IPartialPageRequestHandler > > >
Re: Wicket7: MediaComponent and Source classes
Hi Martin, On Fri, Jul 10, 2015 at 8:35 AM, Martin Grigorov wrote: > On Fri, Jul 10, 2015 at 1:27 AM, Sven Meier wrote: > > > Yes, an overriden method with ART parameter will be something to be > > migrated :/. > > > > > We can try though! > > > > I've greped the Wicket's souce code once again, and only on*()- and > > respond()-methods kept their ART. > > All other 'active' methods (e.g. ModalWindow#close()) take a > > IPartialPageRequestHandler now. > > > > I've missed that ModalWindow#close() is changed too. > I'll do a grep as well. > > Since this change is done for Wicket then it should be done for other more > important UI libraries like Wicket jQuery UI, Wicket Bootstrap and > WicketStuff Foundation. > I suggest to postpone the release of Wicket 7.0.0 with few weeks until we > make the changes and test them for few days. > WDYT? > +1, would be a wise decision... > > > > > > If it helps, I could create a pull-request for the relevant methods in > > wicket-jquery-ui. > > > > Sven > > > > > > > > On 09.07.2015 22:32, Martin Grigorov wrote: > > > >> On Thu, Jul 9, 2015 at 9:23 PM, Sven Meier wrote: > >> > >> Ok. you're partially right :/ > >>> > >>> The compilation error would happen if an application extends > ModalWindow > >> and overrides #close(AjaxRequestTarget) method to do some extra tasks. I > >> have such code for Wicket Bootstrap's Modal component in one of my > >> applications. > >> > >> > >> #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) > > >>> Every application has to be recompiled as the method argument type has > >>> changed. But there won't be any compilation error. > >>> But for a migration to Wicket 7 each application will have to be > >>> recompiled anyway. > >>> > >> > >> The problem is that we probably won't find and change all possible > >> candidates for this change. And once 7.0.0 is out it will be too late. > We > >> can try though! > >> > >> > >> > >>> Sven > >>> > >>> > >>> > >>> On 09.07.2015 20:11, Sven Meier wrote: > >>> > >>> Hi Martin, > > This is what I meant as too disruptive change. If we change the type > of > > > the parameter from ART > > > to IPPRH then every application that uses ModalWindow will have to > fix > > > the compilation error. > > but ART *is* an IPPRH, so there will be no compilation error. > > If we broaden the API from #close(AjaxRequestTarget) to > > > #close(IPartialPageRequestHandler) then this will be an API break. > > Every application will both at compile time and runtime. > > > > Nope, see above. > > Regards > Sven > > On 09.07.2015 16:35, Martin Grigorov wrote: > > Hi Sven, > > > > On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier wrote: > > > > Hi, > > > >> I've just changed all relevant places in Wicket from > AjaxRequestTarget > >> to > >> IPartialPageRequestHandler. > >> > >> I don't think this change is too disruptive: > >> > >> - client code can still call the existing methods with an ART, e.g. > > > > modalWindow.close(ajaxRequestTarget) > >> > >> What Maxim wanted as changes in Wicket jQuery UI are actually > >> changes > >> > > exactly like ModalWindow#close(). > > He needs to be able to close jQuery UI dialogs (non-modal window) > from > > WebSocket response. > > This is what I meant as too disruptive change. If we change the type > of > > the > > parameter from ART to IPPRH then every application that uses > > ModalWindow > > will have to fix the compilation error. > > > > > > - all places needing an ART remain unchanged, e.g. > > > >> AjaxLink#onClick(AjaxRequestTarget) > >> > >> It is not possible to click a link with WebSocket request so this > is > >> > > OK. > > The application developer can roll WebSocketLink if something like > this > > is > > needed. > > > > > > - a dozen Wicket components had to be changed to cooperate with > > > >> IPartialPageRequestHandler instead of just ART: > >> find(IPartialPageRequestHandler.class) > >> > >> Those are good changes! > >> > > > > If we identify other methods later, we can still broaden their > > signature > > > >> to use IPartialPageRequestHandler > >> without breaking the API. > >> > >> No. If we broaden the API from #close(AjaxRequestTarget) to > > #close(IPartialPageRequestHandler) then this will be an API break. > > Every application will both at compile time and runtime. > > > > > > > > we are very (very) close to release 7.0.0, that's why I am a > little > >> bit > >> > >> concerned > >>> > >>> So am I, but for now I think it's simpler to go one step further > >>> > >> instead > >> of 2 steps back. > >> > >> IMO, it i
Re: Wicket7: MediaComponent and Source classes
Hi Sven, On Fri, Jul 10, 2015 at 12:27 AM, Sven Meier wrote: > Yes, an overriden method with ART parameter will be something to be > migrated :/. > > > We can try though! > > I've greped the Wicket's souce code once again, and only on*()- and > respond()-methods kept their ART. > All other 'active' methods (e.g. ModalWindow#close()) take a > IPartialPageRequestHandler now. > > If it helps, I could create a pull-request for the relevant methods in > wicket-jquery-ui. > Thank you very much for your offer but I will handle it :) > > Sven > >
Re: Wicket7: MediaComponent and Source classes
On Fri, Jul 10, 2015 at 1:27 AM, Sven Meier wrote: > Yes, an overriden method with ART parameter will be something to be > migrated :/. > > > We can try though! > > I've greped the Wicket's souce code once again, and only on*()- and > respond()-methods kept their ART. > All other 'active' methods (e.g. ModalWindow#close()) take a > IPartialPageRequestHandler now. > I've missed that ModalWindow#close() is changed too. I'll do a grep as well. Since this change is done for Wicket then it should be done for other more important UI libraries like Wicket jQuery UI, Wicket Bootstrap and WicketStuff Foundation. I suggest to postpone the release of Wicket 7.0.0 with few weeks until we make the changes and test them for few days. WDYT? > > If it helps, I could create a pull-request for the relevant methods in > wicket-jquery-ui. > > Sven > > > > On 09.07.2015 22:32, Martin Grigorov wrote: > >> On Thu, Jul 9, 2015 at 9:23 PM, Sven Meier wrote: >> >> Ok. you're partially right :/ >>> >>> The compilation error would happen if an application extends ModalWindow >> and overrides #close(AjaxRequestTarget) method to do some extra tasks. I >> have such code for Wicket Bootstrap's Modal component in one of my >> applications. >> >> >> #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) >>> Every application has to be recompiled as the method argument type has >>> changed. But there won't be any compilation error. >>> But for a migration to Wicket 7 each application will have to be >>> recompiled anyway. >>> >> >> The problem is that we probably won't find and change all possible >> candidates for this change. And once 7.0.0 is out it will be too late. We >> can try though! >> >> >> >>> Sven >>> >>> >>> >>> On 09.07.2015 20:11, Sven Meier wrote: >>> >>> Hi Martin, This is what I meant as too disruptive change. If we change the type of > the parameter from ART > to IPPRH then every application that uses ModalWindow will have to fix > the compilation error. but ART *is* an IPPRH, so there will be no compilation error. If we broaden the API from #close(AjaxRequestTarget) to > #close(IPartialPageRequestHandler) then this will be an API break. > Every application will both at compile time and runtime. > > Nope, see above. Regards Sven On 09.07.2015 16:35, Martin Grigorov wrote: Hi Sven, > > On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier wrote: > > Hi, > >> I've just changed all relevant places in Wicket from AjaxRequestTarget >> to >> IPartialPageRequestHandler. >> >> I don't think this change is too disruptive: >> >> - client code can still call the existing methods with an ART, e.g. > > modalWindow.close(ajaxRequestTarget) >> >> What Maxim wanted as changes in Wicket jQuery UI are actually >> changes >> > exactly like ModalWindow#close(). > He needs to be able to close jQuery UI dialogs (non-modal window) from > WebSocket response. > This is what I meant as too disruptive change. If we change the type of > the > parameter from ART to IPPRH then every application that uses > ModalWindow > will have to fix the compilation error. > > > - all places needing an ART remain unchanged, e.g. > >> AjaxLink#onClick(AjaxRequestTarget) >> >> It is not possible to click a link with WebSocket request so this is >> > OK. > The application developer can roll WebSocketLink if something like this > is > needed. > > > - a dozen Wicket components had to be changed to cooperate with > >> IPartialPageRequestHandler instead of just ART: >> find(IPartialPageRequestHandler.class) >> >> Those are good changes! >> > > If we identify other methods later, we can still broaden their > signature > >> to use IPartialPageRequestHandler >> without breaking the API. >> >> No. If we broaden the API from #close(AjaxRequestTarget) to > #close(IPartialPageRequestHandler) then this will be an API break. > Every application will both at compile time and runtime. > > > > we are very (very) close to release 7.0.0, that's why I am a little >> bit >> >> concerned >>> >>> So am I, but for now I think it's simpler to go one step further >>> >> instead >> of 2 steps back. >> >> IMO, it is OK-ish to change APIs in Wicket jQuery UI (Sebastien does >> > this > from time to time). > Even if we decide to not break the API of some component then as I > suggested it should be possible to create an adapter from IPPRH to ART: > > MyComponent.java: > > add(new WebSocketBehavior() { > protected void onPush(WebSocketRequestHandler handler, > IWebSocketPushMessage message) > { >>>
Re: Wicket7: MediaComponent and Source classes
Yes, an overriden method with ART parameter will be something to be migrated :/. > We can try though! I've greped the Wicket's souce code once again, and only on*()- and respond()-methods kept their ART. All other 'active' methods (e.g. ModalWindow#close()) take a IPartialPageRequestHandler now. If it helps, I could create a pull-request for the relevant methods in wicket-jquery-ui. Sven On 09.07.2015 22:32, Martin Grigorov wrote: On Thu, Jul 9, 2015 at 9:23 PM, Sven Meier wrote: Ok. you're partially right :/ The compilation error would happen if an application extends ModalWindow and overrides #close(AjaxRequestTarget) method to do some extra tasks. I have such code for Wicket Bootstrap's Modal component in one of my applications. #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) Every application has to be recompiled as the method argument type has changed. But there won't be any compilation error. But for a migration to Wicket 7 each application will have to be recompiled anyway. The problem is that we probably won't find and change all possible candidates for this change. And once 7.0.0 is out it will be too late. We can try though! Sven On 09.07.2015 20:11, Sven Meier wrote: Hi Martin, This is what I meant as too disruptive change. If we change the type of the parameter from ART to IPPRH then every application that uses ModalWindow will have to fix the compilation error. but ART *is* an IPPRH, so there will be no compilation error. If we broaden the API from #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) then this will be an API break. Every application will both at compile time and runtime. Nope, see above. Regards Sven On 09.07.2015 16:35, Martin Grigorov wrote: Hi Sven, On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier wrote: Hi, I've just changed all relevant places in Wicket from AjaxRequestTarget to IPartialPageRequestHandler. I don't think this change is too disruptive: - client code can still call the existing methods with an ART, e.g. modalWindow.close(ajaxRequestTarget) What Maxim wanted as changes in Wicket jQuery UI are actually changes exactly like ModalWindow#close(). He needs to be able to close jQuery UI dialogs (non-modal window) from WebSocket response. This is what I meant as too disruptive change. If we change the type of the parameter from ART to IPPRH then every application that uses ModalWindow will have to fix the compilation error. - all places needing an ART remain unchanged, e.g. AjaxLink#onClick(AjaxRequestTarget) It is not possible to click a link with WebSocket request so this is OK. The application developer can roll WebSocketLink if something like this is needed. - a dozen Wicket components had to be changed to cooperate with IPartialPageRequestHandler instead of just ART: find(IPartialPageRequestHandler.class) Those are good changes! If we identify other methods later, we can still broaden their signature to use IPartialPageRequestHandler without breaking the API. No. If we broaden the API from #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) then this will be an API break. Every application will both at compile time and runtime. we are very (very) close to release 7.0.0, that's why I am a little bit concerned So am I, but for now I think it's simpler to go one step further instead of 2 steps back. IMO, it is OK-ish to change APIs in Wicket jQuery UI (Sebastien does this from time to time). Even if we decide to not break the API of some component then as I suggested it should be possible to create an adapter from IPPRH to ART: MyComponent.java: add(new WebSocketBehavior() { protected void onPush(WebSocketRequestHandler handler, IWebSocketPushMessage message) { AjaxRequestTarget target = WebApplication.get().getAjaxRequestTargetProvider().get(handler.getPage()); modalWindow.close(target); } }); Regards Sven On 09.07.2015 00:31, Sebastien wrote: Hi Sven, But it seems in wicket-jquery-ui there are more methods of this kind? True, about 85 methods (taking an ART without starting with "on"-prefix). In these, I should identify the ones that should be changed (like #open, #close, #show, #hide, #refresh, etc), the others, plus 2 calls to #find(ART.class) to be taken into account... This is a new change since -M6 and we are very (very) close to release 7.0.0, that's why I am a little bit concerned (did I wrote "worried" previously? ;)). I hope I/we do not miss/forget something here... Thanks & best regards, Sebastien. - 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,
Re: Wicket7: MediaComponent and Source classes
On Thu, Jul 9, 2015 at 9:23 PM, Sven Meier wrote: > Ok. you're partially right :/ > The compilation error would happen if an application extends ModalWindow and overrides #close(AjaxRequestTarget) method to do some extra tasks. I have such code for Wicket Bootstrap's Modal component in one of my applications. > > >#close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) > > Every application has to be recompiled as the method argument type has > changed. But there won't be any compilation error. > But for a migration to Wicket 7 each application will have to be > recompiled anyway. The problem is that we probably won't find and change all possible candidates for this change. And once 7.0.0 is out it will be too late. We can try though! > > > Sven > > > > On 09.07.2015 20:11, Sven Meier wrote: > >> Hi Martin, >> >> > This is what I meant as too disruptive change. If we change the type of >> the parameter from ART >> > to IPPRH then every application that uses ModalWindow will have to fix >> the compilation error. >> >> but ART *is* an IPPRH, so there will be no compilation error. >> >> If we broaden the API from #close(AjaxRequestTarget) to >>> #close(IPartialPageRequestHandler) then this will be an API break. >>> Every application will both at compile time and runtime. >>> >> >> Nope, see above. >> >> Regards >> Sven >> >> On 09.07.2015 16:35, Martin Grigorov wrote: >> >>> Hi Sven, >>> >>> On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier wrote: >>> >>> Hi, I've just changed all relevant places in Wicket from AjaxRequestTarget to IPartialPageRequestHandler. I don't think this change is too disruptive: >>> - client code can still call the existing methods with an ART, e.g. >>> modalWindow.close(ajaxRequestTarget) What Maxim wanted as changes in Wicket jQuery UI are actually changes >>> exactly like ModalWindow#close(). >>> He needs to be able to close jQuery UI dialogs (non-modal window) from >>> WebSocket response. >>> This is what I meant as too disruptive change. If we change the type of >>> the >>> parameter from ART to IPPRH then every application that uses ModalWindow >>> will have to fix the compilation error. >>> >>> >>> - all places needing an ART remain unchanged, e.g. AjaxLink#onClick(AjaxRequestTarget) It is not possible to click a link with WebSocket request so this is >>> OK. >>> The application developer can roll WebSocketLink if something like this >>> is >>> needed. >>> >>> >>> - a dozen Wicket components had to be changed to cooperate with IPartialPageRequestHandler instead of just ART: find(IPartialPageRequestHandler.class) Those are good changes! >>> >>> >>> If we identify other methods later, we can still broaden their signature to use IPartialPageRequestHandler without breaking the API. >>> >>> No. If we broaden the API from #close(AjaxRequestTarget) to >>> #close(IPartialPageRequestHandler) then this will be an API break. >>> Every application will both at compile time and runtime. >>> >>> >>> we are very (very) close to release 7.0.0, that's why I am a little bit > concerned > > So am I, but for now I think it's simpler to go one step further instead of 2 steps back. IMO, it is OK-ish to change APIs in Wicket jQuery UI (Sebastien does >>> this >>> from time to time). >>> Even if we decide to not break the API of some component then as I >>> suggested it should be possible to create an adapter from IPPRH to ART: >>> >>> MyComponent.java: >>> >>> add(new WebSocketBehavior() { >>> protected void onPush(WebSocketRequestHandler handler, >>> IWebSocketPushMessage message) >>> { >>> AjaxRequestTarget target = >>> WebApplication.get().getAjaxRequestTargetProvider().get(handler.getPage()); >>> >>> modalWindow.close(target); >>> } >>> }); >>> >>> >>> Regards Sven On 09.07.2015 00:31, Sebastien wrote: Hi Sven, > > > But it seems in wicket-jquery-ui there are more methods of this kind? > >> >> True, about 85 methods (taking an ART without starting with >> > "on"-prefix). > In these, I should identify the ones that should be changed (like > #open, > #close, #show, #hide, #refresh, etc), the others, plus 2 calls to > #find(ART.class) to be taken into account... > This is a new change since -M6 and we are very (very) close to release > 7.0.0, that's why I am a little bit concerned (did I wrote "worried" > previously? ;)). I hope I/we do not miss/forget something here... > > Thanks & best regards, > Sebastien. > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org >> >>
Re: Wicket7: MediaComponent and Source classes
Ok. you're partially right :/ >#close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) Every application has to be recompiled as the method argument type has changed. But there won't be any compilation error. But for a migration to Wicket 7 each application will have to be recompiled anyway. Sven On 09.07.2015 20:11, Sven Meier wrote: Hi Martin, > This is what I meant as too disruptive change. If we change the type of the parameter from ART > to IPPRH then every application that uses ModalWindow will have to fix the compilation error. but ART *is* an IPPRH, so there will be no compilation error. If we broaden the API from #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) then this will be an API break. Every application will both at compile time and runtime. Nope, see above. Regards Sven On 09.07.2015 16:35, Martin Grigorov wrote: Hi Sven, On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier wrote: Hi, I've just changed all relevant places in Wicket from AjaxRequestTarget to IPartialPageRequestHandler. I don't think this change is too disruptive: - client code can still call the existing methods with an ART, e.g. modalWindow.close(ajaxRequestTarget) What Maxim wanted as changes in Wicket jQuery UI are actually changes exactly like ModalWindow#close(). He needs to be able to close jQuery UI dialogs (non-modal window) from WebSocket response. This is what I meant as too disruptive change. If we change the type of the parameter from ART to IPPRH then every application that uses ModalWindow will have to fix the compilation error. - all places needing an ART remain unchanged, e.g. AjaxLink#onClick(AjaxRequestTarget) It is not possible to click a link with WebSocket request so this is OK. The application developer can roll WebSocketLink if something like this is needed. - a dozen Wicket components had to be changed to cooperate with IPartialPageRequestHandler instead of just ART: find(IPartialPageRequestHandler.class) Those are good changes! If we identify other methods later, we can still broaden their signature to use IPartialPageRequestHandler without breaking the API. No. If we broaden the API from #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) then this will be an API break. Every application will both at compile time and runtime. we are very (very) close to release 7.0.0, that's why I am a little bit concerned So am I, but for now I think it's simpler to go one step further instead of 2 steps back. IMO, it is OK-ish to change APIs in Wicket jQuery UI (Sebastien does this from time to time). Even if we decide to not break the API of some component then as I suggested it should be possible to create an adapter from IPPRH to ART: MyComponent.java: add(new WebSocketBehavior() { protected void onPush(WebSocketRequestHandler handler, IWebSocketPushMessage message) { AjaxRequestTarget target = WebApplication.get().getAjaxRequestTargetProvider().get(handler.getPage()); modalWindow.close(target); } }); Regards Sven On 09.07.2015 00:31, Sebastien wrote: Hi Sven, But it seems in wicket-jquery-ui there are more methods of this kind? True, about 85 methods (taking an ART without starting with "on"-prefix). In these, I should identify the ones that should be changed (like #open, #close, #show, #hide, #refresh, etc), the others, plus 2 calls to #find(ART.class) to be taken into account... This is a new change since -M6 and we are very (very) close to release 7.0.0, that's why I am a little bit concerned (did I wrote "worried" previously? ;)). I hope I/we do not miss/forget something here... Thanks & best regards, Sebastien. - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
Hi Martin, > This is what I meant as too disruptive change. If we change the type of the parameter from ART > to IPPRH then every application that uses ModalWindow will have to fix the compilation error. but ART *is* an IPPRH, so there will be no compilation error. If we broaden the API from #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) then this will be an API break. Every application will both at compile time and runtime. Nope, see above. Regards Sven On 09.07.2015 16:35, Martin Grigorov wrote: Hi Sven, On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier wrote: Hi, I've just changed all relevant places in Wicket from AjaxRequestTarget to IPartialPageRequestHandler. I don't think this change is too disruptive: - client code can still call the existing methods with an ART, e.g. modalWindow.close(ajaxRequestTarget) What Maxim wanted as changes in Wicket jQuery UI are actually changes exactly like ModalWindow#close(). He needs to be able to close jQuery UI dialogs (non-modal window) from WebSocket response. This is what I meant as too disruptive change. If we change the type of the parameter from ART to IPPRH then every application that uses ModalWindow will have to fix the compilation error. - all places needing an ART remain unchanged, e.g. AjaxLink#onClick(AjaxRequestTarget) It is not possible to click a link with WebSocket request so this is OK. The application developer can roll WebSocketLink if something like this is needed. - a dozen Wicket components had to be changed to cooperate with IPartialPageRequestHandler instead of just ART: find(IPartialPageRequestHandler.class) Those are good changes! If we identify other methods later, we can still broaden their signature to use IPartialPageRequestHandler without breaking the API. No. If we broaden the API from #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) then this will be an API break. Every application will both at compile time and runtime. we are very (very) close to release 7.0.0, that's why I am a little bit concerned So am I, but for now I think it's simpler to go one step further instead of 2 steps back. IMO, it is OK-ish to change APIs in Wicket jQuery UI (Sebastien does this from time to time). Even if we decide to not break the API of some component then as I suggested it should be possible to create an adapter from IPPRH to ART: MyComponent.java: add(new WebSocketBehavior() { protected void onPush(WebSocketRequestHandler handler, IWebSocketPushMessage message) { AjaxRequestTarget target = WebApplication.get().getAjaxRequestTargetProvider().get(handler.getPage()); modalWindow.close(target); } }); Regards Sven On 09.07.2015 00:31, Sebastien wrote: Hi Sven, But it seems in wicket-jquery-ui there are more methods of this kind? True, about 85 methods (taking an ART without starting with "on"-prefix). In these, I should identify the ones that should be changed (like #open, #close, #show, #hide, #refresh, etc), the others, plus 2 calls to #find(ART.class) to be taken into account... This is a new change since -M6 and we are very (very) close to release 7.0.0, that's why I am a little bit concerned (did I wrote "worried" previously? ;)). I hope I/we do not miss/forget something here... Thanks & best regards, Sebastien. - 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: Wicket7: MediaComponent and Source classes
Hi Sven, On Thu, Jul 9, 2015 at 4:31 PM, Sven Meier wrote: > Hi, > > I've just changed all relevant places in Wicket from AjaxRequestTarget to > IPartialPageRequestHandler. > > I don't think this change is too disruptive: - client code can still call the existing methods with an ART, e.g. > modalWindow.close(ajaxRequestTarget) > What Maxim wanted as changes in Wicket jQuery UI are actually changes exactly like ModalWindow#close(). He needs to be able to close jQuery UI dialogs (non-modal window) from WebSocket response. This is what I meant as too disruptive change. If we change the type of the parameter from ART to IPPRH then every application that uses ModalWindow will have to fix the compilation error. > - all places needing an ART remain unchanged, e.g. > AjaxLink#onClick(AjaxRequestTarget) > It is not possible to click a link with WebSocket request so this is OK. The application developer can roll WebSocketLink if something like this is needed. > - a dozen Wicket components had to be changed to cooperate with > IPartialPageRequestHandler instead of just ART: > find(IPartialPageRequestHandler.class) > Those are good changes! > > If we identify other methods later, we can still broaden their signature > to use IPartialPageRequestHandler > without breaking the API. No. If we broaden the API from #close(AjaxRequestTarget) to #close(IPartialPageRequestHandler) then this will be an API break. Every application will both at compile time and runtime. > > > we are very (very) close to release 7.0.0, that's why I am a little bit >> concerned >> > > So am I, but for now I think it's simpler to go one step further instead > of 2 steps back. > IMO, it is OK-ish to change APIs in Wicket jQuery UI (Sebastien does this from time to time). Even if we decide to not break the API of some component then as I suggested it should be possible to create an adapter from IPPRH to ART: MyComponent.java: add(new WebSocketBehavior() { protected void onPush(WebSocketRequestHandler handler, IWebSocketPushMessage message) { AjaxRequestTarget target = WebApplication.get().getAjaxRequestTargetProvider().get(handler.getPage()); modalWindow.close(target); } }); > > Regards > Sven > > > > On 09.07.2015 00:31, Sebastien wrote: > >> Hi Sven, >> >> >> But it seems in wicket-jquery-ui there are more methods of this kind? >>> >>> >>> True, about 85 methods (taking an ART without starting with >> "on"-prefix). >> In these, I should identify the ones that should be changed (like #open, >> #close, #show, #hide, #refresh, etc), the others, plus 2 calls to >> #find(ART.class) to be taken into account... >> This is a new change since -M6 and we are very (very) close to release >> 7.0.0, that's why I am a little bit concerned (did I wrote "worried" >> previously? ;)). I hope I/we do not miss/forget something here... >> >> Thanks & best regards, >> Sebastien. >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Wicket7: MediaComponent and Source classes
Hi, I've just changed all relevant places in Wicket from AjaxRequestTarget to IPartialPageRequestHandler. I don't think this change is too disruptive: - client code can still call the existing methods with an ART, e.g. modalWindow.close(ajaxRequestTarget) - all places needing an ART remain unchanged, e.g. AjaxLink#onClick(AjaxRequestTarget) - a dozen Wicket components had to be changed to cooperate with IPartialPageRequestHandler instead of just ART: find(IPartialPageRequestHandler.class) If we identify other methods later, we can still broaden their signature to use IPartialPageRequestHandler without breaking the API. we are very (very) close to release 7.0.0, that's why I am a little bit concerned So am I, but for now I think it's simpler to go one step further instead of 2 steps back. Regards Sven On 09.07.2015 00:31, Sebastien wrote: Hi Sven, But it seems in wicket-jquery-ui there are more methods of this kind? True, about 85 methods (taking an ART without starting with "on"-prefix). In these, I should identify the ones that should be changed (like #open, #close, #show, #hide, #refresh, etc), the others, plus 2 calls to #find(ART.class) to be taken into account... This is a new change since -M6 and we are very (very) close to release 7.0.0, that's why I am a little bit concerned (did I wrote "worried" previously? ;)). I hope I/we do not miss/forget something here... Thanks & best regards, Sebastien. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
Hi Sebastien, On Wed, Jul 8, 2015 at 10:04 PM, Sebastien wrote: > Hi, > > Sorry, little bit late on the topic... > > On Fri, Jul 3, 2015 at 7:38 AM, Martin Grigorov > wrote: > >> HI Maxim, >> >> This will lead to a big API break. >> If we change this signature then we will have to change many more to keep >> it consistent, and this will lead to a lot of work for the application >> developers to change AjaxRequestTarget with IPartialPageRequestHandler. >> > > That's exactly the point I am worrying about... All signatures have to be > checked to see whether or not it's an AjaxRequestTarget usage only or a > method that can works with websockets too (and then change the signature to > IPartialPageRequestHandler)... With the same idea, > IListener/AbstractListener are part of ART. But #add(Component...) is part > of IPartialPageRequestHandler, so adding a component via websocket will not > trigger IListener#onBeforeRespond (1) ? This would probably lead to some > unexpected behaviors, like for instance in Wicket jQuery UI where there is > a "DestroyListener" (which handles the jquery #destroy of the widget)... > > Am I accurate on the analysis or did I missed a point? > You are correct! But this is the case even now (in Wicket 6.x) because WebSocketRequestHandler has empty implementations of the listener related methods: https://github.com/apache/wicket/blob/wicket-6.x/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/WebSocketRequestHandler.java#L72-L82 There is a workaround though - it is very easy to create AjaxRequestHandler out of IPartialPageRequestHandler and use it when this is needed. > > Thanks & best regards, > Sebastien. > > (1) actually I never double checked this is the case, but on the > principle/theoretically I guess it should be... > > > >> >> We may need to make this change for Wicket 8.x if there are many users >> wanting this change, but for now I'd suggest you to create an adapter. >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik >> wrote: >> >>> Hello Martin, >>> >>> I guess following method need to be additionally updated: >>> >>> org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer >>> >>> On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov >>> wrote: >>> >>> > The change is rather big: >>> > >>> > >>> https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af >>> > I guess many other methods will need to be changed too if one needs to >>> use >>> > them with WebSocket. >>> > The improvement in the Wicket API looked so innocent ... >>> > >>> > Martin Grigorov >>> > Freelancer. Available for hire! >>> > Wicket Training and Consulting >>> > https://twitter.com/mtgrigorov >>> > >>> >>
Re: Wicket7: MediaComponent and Source classes
Hi Sven, > But it seems in wicket-jquery-ui there are more methods of this kind? > > True, about 85 methods (taking an ART without starting with "on"-prefix). In these, I should identify the ones that should be changed (like #open, #close, #show, #hide, #refresh, etc), the others, plus 2 calls to #find(ART.class) to be taken into account... This is a new change since -M6 and we are very (very) close to release 7.0.0, that's why I am a little bit concerned (did I wrote "worried" previously? ;)). I hope I/we do not miss/forget something here... Thanks & best regards, Sebastien.
Re: Wicket7: MediaComponent and Source classes
Hi, that change seems to have a hight impact - sorry, I didn't think of these implications. > But #add(Component...) is part of IPartialPageRequestHandler > so adding a component via websocket will not trigger IListener#onBeforeRespond WebSockerRequestHandler#addListener() was a noop previously, so we don't lose anything here >I guess following method need to be additionally updated: >org.apache.wicket.ajax.AbstractAjaxTimerBehavior#onTimer Why, an Ajax timer is triggered by Ajax calls only, isn't it? AbstractAjaxTimerBehavior#restart() and #stop() could be invoked from a WebSocket request though. >All signatures have to be checked ... AjaxRequestTarget or ... IPartialPageRequestHandler I checked Wicket's code for methods that take ART as argument and having a name which doesn't start with an 'on'-prefix: There are the two methods above and ModalWindow#show() and #close() that should be changed to IPartialPageRequestHandler. These are backwards compatible changes actually. There are half a dozen calls to #find(AjaxRequestTarget.class) in Wicket classes which should switch from ART to IPartialPageRequestHandler, to restore cooperation with WebSockets. But it seems in wicket-jquery-ui there are more methods of this kind? Regards Sven On 08.07.2015 21:30, Sebastien wrote: Hi, Sorry, little bit late on the topic... On Fri, Jul 3, 2015 at 7:38 AM, Martin Grigorov wrote: HI Maxim, This will lead to a big API break. If we change this signature then we will have to change many more to keep it consistent, and this will lead to a lot of work for the application developers to change AjaxRequestTarget with IPartialPageRequestHandler. That's exactly the point I am worrying about... All signatures have to be checked to see whether or not it's an AjaxRequestTarget usage only or a method that can works with websockets too (and then change the signature to IPartialPageRequestHandler)... With the same idea, IListener/AbstractListener are part of ART. But #add(Component...) is part of IPartialPageRequestHandler, so adding a component via websocket will not trigger IListener#onBeforeRespond (1) ? This would probably lead to some unexpected behaviors, like for instance in Wicket jQuery UI where there is a "DestroyListener" (which handles the jquery #destroy of the widget)... Am I accurate on the analysis or did I missed a point? Thanks & best regards, Sebastien. (1) actually I never double checked this is the case, but on the principle/theoretically I guess it should be... We may need to make this change for Wicket 8.x if there are many users wanting this change, but for now I'd suggest you to create an adapter. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik wrote: Hello Martin, I guess following method need to be additionally updated: org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov wrote: The change is rather big: https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af I guess many other methods will need to be changed too if one needs to use them with WebSocket. The improvement in the Wicket API looked so innocent ... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
Hi, Sorry, little bit late on the topic... On Fri, Jul 3, 2015 at 7:38 AM, Martin Grigorov wrote: > HI Maxim, > > This will lead to a big API break. > If we change this signature then we will have to change many more to keep > it consistent, and this will lead to a lot of work for the application > developers to change AjaxRequestTarget with IPartialPageRequestHandler. > That's exactly the point I am worrying about... All signatures have to be checked to see whether or not it's an AjaxRequestTarget usage only or a method that can works with websockets too (and then change the signature to IPartialPageRequestHandler)... With the same idea, IListener/AbstractListener are part of ART. But #add(Component...) is part of IPartialPageRequestHandler, so adding a component via websocket will not trigger IListener#onBeforeRespond (1) ? This would probably lead to some unexpected behaviors, like for instance in Wicket jQuery UI where there is a "DestroyListener" (which handles the jquery #destroy of the widget)... Am I accurate on the analysis or did I missed a point? Thanks & best regards, Sebastien. (1) actually I never double checked this is the case, but on the principle/theoretically I guess it should be... > > We may need to make this change for Wicket 8.x if there are many users > wanting this change, but for now I'd suggest you to create an adapter. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik > wrote: > >> Hello Martin, >> >> I guess following method need to be additionally updated: >> >> org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer >> >> On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov >> wrote: >> >> > The change is rather big: >> > >> > >> https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af >> > I guess many other methods will need to be changed too if one needs to >> use >> > them with WebSocket. >> > The improvement in the Wicket API looked so innocent ... >> > >> > Martin Grigorov >> > Freelancer. Available for hire! >> > Wicket Training and Consulting >> > https://twitter.com/mtgrigorov >> > >> >
Re: Wicket7: MediaComponent and Source classes
Just have tried :) hopefully it'll help :) On Sun, Jul 5, 2015 at 1:40 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > May it helps when you add me to your contact list. > > kind regards > > Tobias > > > Am 05.07.2015 um 07:40 schrieb Maxim Solodovnik : > > > > Hello Tobias, > > > > Everything seems to work as expected! > > sorry for the late response, your emails are still going into Spam :((( > > > > On Fri, Jul 3, 2015 at 6:34 PM, Tobias Soloschenko < > > tobiassolosche...@googlemail.com> wrote: > > > >> @Maxim: Is there anything left to be done within the media components? > >> Otherwise I am going to vote +1 > >> > >> kind regards > >> > >> Tobias > >> > >>> Am 03.07.2015 um 07:43 schrieb Maxim Solodovnik >: > >>> > >>> OK, will try > >>> Thanks > >>> > >>> On Fri, Jul 3, 2015 at 11:38 AM, Martin Grigorov > > >>> wrote: > >>> > HI Maxim, > > This will lead to a big API break. > If we change this signature then we will have to change many more to > >> keep > it consistent, and this will lead to a lot of work for the application > developers to change AjaxRequestTarget with > IPartialPageRequestHandler. > > We may need to make this change for Wicket 8.x if there are many users > wanting this change, but for now I'd suggest you to create an adapter. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik < > solomax...@gmail.com> > wrote: > > > Hello Martin, > > > > I guess following method need to be additionally updated: > > > > org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer > > > > On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov < > mgrigo...@apache.org> > > wrote: > > > >> The change is rather big: > >> > https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af > >> I guess many other methods will need to be changed too if one needs > to > > use > >> them with WebSocket. > >> The improvement in the Wicket API looked so innocent ... > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik < > >> solomax...@gmail.com > > > >> wrote: > >> > >>> Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > >>> Sorry, forgot about Sebastians vacation :( > >>> > >>> On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov < > mgrigo...@apache.org> > >>> wrote: > >>> > @Maxim: Please create an issue at Wicket jQuery UI github. > Sebastien is on vacation. I can do it but first I need a good > reason > >> for > the change :-) > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < > >> solomax...@gmail.com> > wrote: > > > @Sebastian could you please modify AbstractDialog.open method to > be > > > > public final void open(IPartialPageRequestHandler target) > > instead of > > public final void open(AjaxRequestTarget target) > > > > Thanks in advance! > > > > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < > >> mgrigo...@apache.org> > > wrote: > > > >> Yes, another minor cleanup: there is now > >> > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > >> A base interface for Ajax and WebSocket. > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > solomax...@gmail.com> > >> wrote: > >> > >>> Additionally it looks like WebSocketRequestHandler can not be > >> used > >>> as AjaxRequestTarget any longer > >>> Previously it was possible to use WebSocketRequestHandler to > > push > > updated > >>> component . > >>> > >>> On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > solomax...@gmail.com > >> > >>> wrote: > >>> > Thanks a lot Tobias! > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > > > Hi Maxim, > > > > no problem I am going to add the getter this evening. > Thank > >
Re: Wicket7: MediaComponent and Source classes
May it helps when you add me to your contact list. kind regards Tobias > Am 05.07.2015 um 07:40 schrieb Maxim Solodovnik : > > Hello Tobias, > > Everything seems to work as expected! > sorry for the late response, your emails are still going into Spam :((( > > On Fri, Jul 3, 2015 at 6:34 PM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > >> @Maxim: Is there anything left to be done within the media components? >> Otherwise I am going to vote +1 >> >> kind regards >> >> Tobias >> >>> Am 03.07.2015 um 07:43 schrieb Maxim Solodovnik : >>> >>> OK, will try >>> Thanks >>> >>> On Fri, Jul 3, 2015 at 11:38 AM, Martin Grigorov >>> wrote: >>> HI Maxim, This will lead to a big API break. If we change this signature then we will have to change many more to >> keep it consistent, and this will lead to a lot of work for the application developers to change AjaxRequestTarget with IPartialPageRequestHandler. We may need to make this change for Wicket 8.x if there are many users wanting this change, but for now I'd suggest you to create an adapter. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik wrote: > Hello Martin, > > I guess following method need to be additionally updated: > > org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer > > On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov > wrote: > >> The change is rather big: >> https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af >> I guess many other methods will need to be changed too if one needs to > use >> them with WebSocket. >> The improvement in the Wicket API looked so innocent ... >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik < >> solomax...@gmail.com > >> wrote: >> >>> Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 >>> Sorry, forgot about Sebastians vacation :( >>> >>> On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov < mgrigo...@apache.org> >>> wrote: >>> @Maxim: Please create an issue at Wicket jQuery UI github. Sebastien is on vacation. I can do it but first I need a good reason >> for the change :-) Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < >> solomax...@gmail.com> wrote: > @Sebastian could you please modify AbstractDialog.open method to be > > public final void open(IPartialPageRequestHandler target) > instead of > public final void open(AjaxRequestTarget target) > > Thanks in advance! > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < >> mgrigo...@apache.org> > wrote: > >> Yes, another minor cleanup: there is now >> https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java >> A base interface for Ajax and WebSocket. >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < solomax...@gmail.com> >> wrote: >> >>> Additionally it looks like WebSocketRequestHandler can not be >> used >>> as AjaxRequestTarget any longer >>> Previously it was possible to use WebSocketRequestHandler to > push > updated >>> component . >>> >>> On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < solomax...@gmail.com >> >>> wrote: >>> Thanks a lot Tobias! On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Maxim, > > no problem I am going to add the getter this evening. Thank >> you for >> your > suggestions! :-) > > Maybe the SNAPSHOT isn't refreshed because of the downtime > of >>> the > buildbot server. However the build was triggered already. > > kind regards > > Tobias > >> Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < >> solomax...@gmail.com >>
Re: Wicket7: MediaComponent and Source classes
Hello Tobias, Everything seems to work as expected! sorry for the late response, your emails are still going into Spam :((( On Fri, Jul 3, 2015 at 6:34 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > @Maxim: Is there anything left to be done within the media components? > Otherwise I am going to vote +1 > > kind regards > > Tobias > > > Am 03.07.2015 um 07:43 schrieb Maxim Solodovnik : > > > > OK, will try > > Thanks > > > > On Fri, Jul 3, 2015 at 11:38 AM, Martin Grigorov > > wrote: > > > >> HI Maxim, > >> > >> This will lead to a big API break. > >> If we change this signature then we will have to change many more to > keep > >> it consistent, and this will lead to a lot of work for the application > >> developers to change AjaxRequestTarget with IPartialPageRequestHandler. > >> > >> We may need to make this change for Wicket 8.x if there are many users > >> wanting this change, but for now I'd suggest you to create an adapter. > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik > >> wrote: > >> > >>> Hello Martin, > >>> > >>> I guess following method need to be additionally updated: > >>> > >>> org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer > >>> > >>> On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov > >>> wrote: > >>> > The change is rather big: > >> > https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af > I guess many other methods will need to be changed too if one needs to > >>> use > them with WebSocket. > The improvement in the Wicket API looked so innocent ... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik < > solomax...@gmail.com > >>> > wrote: > > > Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > > Sorry, forgot about Sebastians vacation :( > > > > On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov < > >> mgrigo...@apache.org> > > wrote: > > > >> @Maxim: Please create an issue at Wicket jQuery UI github. > >> Sebastien is on vacation. I can do it but first I need a good > >> reason > for > >> the change :-) > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < > solomax...@gmail.com> > >> wrote: > >> > >>> @Sebastian could you please modify AbstractDialog.open method to > >> be > >>> > >>> public final void open(IPartialPageRequestHandler target) > >>> instead of > >>> public final void open(AjaxRequestTarget target) > >>> > >>> Thanks in advance! > >>> > >>> > >>> On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < > mgrigo...@apache.org> > >>> wrote: > >>> > Yes, another minor cleanup: there is now > >> > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > A base interface for Ajax and WebSocket. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > >> solomax...@gmail.com> > wrote: > > > Additionally it looks like WebSocketRequestHandler can not be > used > > as AjaxRequestTarget any longer > > Previously it was possible to use WebSocketRequestHandler to > >>> push > >>> updated > > component . > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > >> solomax...@gmail.com > > > wrote: > > > >> Thanks a lot Tobias! > >> > >> On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > >> tobiassolosche...@googlemail.com> wrote: > >> > >>> Hi Maxim, > >>> > >>> no problem I am going to add the getter this evening. > >> Thank > you > >> for > your > >>> suggestions! :-) > >>> > >>> Maybe the SNAPSHOT isn't refreshed because of the downtime > >>> of > > the > >>> buildbot server. However the build was triggered already. > >>> > >>> kind regards > >>> > >>> Tobias > >>> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > solomax...@gmail.com > >> : > > Thanks a lot for the changes Tobias, > Unfortunately I'm unable to test it due to latest > > 7.0.0-SNAPSHOT > seems > >>
Re: Wicket7: MediaComponent and Source classes
@Maxim: Is there anything left to be done within the media components? Otherwise I am going to vote +1 kind regards Tobias > Am 03.07.2015 um 07:43 schrieb Maxim Solodovnik : > > OK, will try > Thanks > > On Fri, Jul 3, 2015 at 11:38 AM, Martin Grigorov > wrote: > >> HI Maxim, >> >> This will lead to a big API break. >> If we change this signature then we will have to change many more to keep >> it consistent, and this will lead to a lot of work for the application >> developers to change AjaxRequestTarget with IPartialPageRequestHandler. >> >> We may need to make this change for Wicket 8.x if there are many users >> wanting this change, but for now I'd suggest you to create an adapter. >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik >> wrote: >> >>> Hello Martin, >>> >>> I guess following method need to be additionally updated: >>> >>> org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer >>> >>> On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov >>> wrote: >>> The change is rather big: >> https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af I guess many other methods will need to be changed too if one needs to >>> use them with WebSocket. The improvement in the Wicket API looked so innocent ... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik >> wrote: > Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > Sorry, forgot about Sebastians vacation :( > > On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov < >> mgrigo...@apache.org> > wrote: > >> @Maxim: Please create an issue at Wicket jQuery UI github. >> Sebastien is on vacation. I can do it but first I need a good >> reason for >> the change :-) >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < solomax...@gmail.com> >> wrote: >> >>> @Sebastian could you please modify AbstractDialog.open method to >> be >>> >>> public final void open(IPartialPageRequestHandler target) >>> instead of >>> public final void open(AjaxRequestTarget target) >>> >>> Thanks in advance! >>> >>> >>> On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < mgrigo...@apache.org> >>> wrote: >>> Yes, another minor cleanup: there is now >> https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java A base interface for Ajax and WebSocket. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < >> solomax...@gmail.com> wrote: > Additionally it looks like WebSocketRequestHandler can not be used > as AjaxRequestTarget any longer > Previously it was possible to use WebSocketRequestHandler to >>> push >>> updated > component . > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < >> solomax...@gmail.com > wrote: > >> Thanks a lot Tobias! >> >> On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < >> tobiassolosche...@googlemail.com> wrote: >> >>> Hi Maxim, >>> >>> no problem I am going to add the getter this evening. >> Thank you >> for your >>> suggestions! :-) >>> >>> Maybe the SNAPSHOT isn't refreshed because of the downtime >>> of > the >>> buildbot server. However the build was triggered already. >>> >>> kind regards >>> >>> Tobias >>> Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < solomax...@gmail.com >> : Thanks a lot for the changes Tobias, Unfortunately I'm unable to test it due to latest > 7.0.0-SNAPSHOT seems doesn't contain it :( And one more question: I would like to be able to modify > PageParameters passed to source, maybe it would be possible to add >> public >> getter for >>> it? Thanks in advance On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Maxim, > > hope the chang
Re: Wicket7: MediaComponent and Source classes
OK, will try Thanks On Fri, Jul 3, 2015 at 11:38 AM, Martin Grigorov wrote: > HI Maxim, > > This will lead to a big API break. > If we change this signature then we will have to change many more to keep > it consistent, and this will lead to a lot of work for the application > developers to change AjaxRequestTarget with IPartialPageRequestHandler. > > We may need to make this change for Wicket 8.x if there are many users > wanting this change, but for now I'd suggest you to create an adapter. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik > wrote: > > > Hello Martin, > > > > I guess following method need to be additionally updated: > > > > org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer > > > > On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov > > wrote: > > > > > The change is rather big: > > > > > > > > > https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af > > > I guess many other methods will need to be changed too if one needs to > > use > > > them with WebSocket. > > > The improvement in the Wicket API looked so innocent ... > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik > > > > wrote: > > > > > > > Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > > > > Sorry, forgot about Sebastians vacation :( > > > > > > > > On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov < > mgrigo...@apache.org> > > > > wrote: > > > > > > > > > @Maxim: Please create an issue at Wicket jQuery UI github. > > > > > Sebastien is on vacation. I can do it but first I need a good > reason > > > for > > > > > the change :-) > > > > > > > > > > Martin Grigorov > > > > > Freelancer. Available for hire! > > > > > Wicket Training and Consulting > > > > > https://twitter.com/mtgrigorov > > > > > > > > > > On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < > > > solomax...@gmail.com> > > > > > wrote: > > > > > > > > > > > @Sebastian could you please modify AbstractDialog.open method to > be > > > > > > > > > > > > public final void open(IPartialPageRequestHandler target) > > > > > > instead of > > > > > > public final void open(AjaxRequestTarget target) > > > > > > > > > > > > Thanks in advance! > > > > > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < > > > mgrigo...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Yes, another minor cleanup: there is now > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > > > > > > > A base interface for Ajax and WebSocket. > > > > > > > > > > > > > > Martin Grigorov > > > > > > > Freelancer. Available for hire! > > > > > > > Wicket Training and Consulting > > > > > > > https://twitter.com/mtgrigorov > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > > > > > solomax...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Additionally it looks like WebSocketRequestHandler can not be > > > used > > > > > > > > as AjaxRequestTarget any longer > > > > > > > > Previously it was possible to use WebSocketRequestHandler to > > push > > > > > > updated > > > > > > > > component . > > > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > > > > > solomax...@gmail.com > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Thanks a lot Tobias! > > > > > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > > > > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > > > > > > > > > > > >> Hi Maxim, > > > > > > > > >> > > > > > > > > >> no problem I am going to add the getter this evening. > Thank > > > you > > > > > for > > > > > > > your > > > > > > > > >> suggestions! :-) > > > > > > > > >> > > > > > > > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime > > of > > > > the > > > > > > > > >> buildbot server. However the build was triggered already. > > > > > > > > >> > > > > > > > > >> kind regards > > > > > > > > >> > > > > > > > > >> Tobias > > > > > > > > >> > > > > > > > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > > > > > > > solomax...@gmail.com > > > > > > > > >: > > > > > > > > >> > > > > > > > > > >> > Thanks a lot for the changes Tobias, > > > > > > > > >> > Unfortunately I'm unable to test it due to latest > > > > 7.0.0-SNAPSHOT > > > > > > > seems > > > > > > > > >> > doesn't contain it :( > > > > > > > > >> > > > > > > > > > >> > And one more question: I would like to be able to modify > > > > > > > > PageParameters > > > > > > > > >> > passed to source, maybe it would be possible to add > public > > > > > getter > > > > > >
Re: Wicket7: MediaComponent and Source classes
HI Maxim, This will lead to a big API break. If we change this signature then we will have to change many more to keep it consistent, and this will lead to a lot of work for the application developers to change AjaxRequestTarget with IPartialPageRequestHandler. We may need to make this change for Wicket 8.x if there are many users wanting this change, but for now I'd suggest you to create an adapter. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik wrote: > Hello Martin, > > I guess following method need to be additionally updated: > > org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer > > On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov > wrote: > > > The change is rather big: > > > > > https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af > > I guess many other methods will need to be changed too if one needs to > use > > them with WebSocket. > > The improvement in the Wicket API looked so innocent ... > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik > > wrote: > > > > > Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > > > Sorry, forgot about Sebastians vacation :( > > > > > > On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov > > > wrote: > > > > > > > @Maxim: Please create an issue at Wicket jQuery UI github. > > > > Sebastien is on vacation. I can do it but first I need a good reason > > for > > > > the change :-) > > > > > > > > Martin Grigorov > > > > Freelancer. Available for hire! > > > > Wicket Training and Consulting > > > > https://twitter.com/mtgrigorov > > > > > > > > On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < > > solomax...@gmail.com> > > > > wrote: > > > > > > > > > @Sebastian could you please modify AbstractDialog.open method to be > > > > > > > > > > public final void open(IPartialPageRequestHandler target) > > > > > instead of > > > > > public final void open(AjaxRequestTarget target) > > > > > > > > > > Thanks in advance! > > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < > > mgrigo...@apache.org> > > > > > wrote: > > > > > > > > > > > Yes, another minor cleanup: there is now > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > > > > > > A base interface for Ajax and WebSocket. > > > > > > > > > > > > Martin Grigorov > > > > > > Freelancer. Available for hire! > > > > > > Wicket Training and Consulting > > > > > > https://twitter.com/mtgrigorov > > > > > > > > > > > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > > > > solomax...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Additionally it looks like WebSocketRequestHandler can not be > > used > > > > > > > as AjaxRequestTarget any longer > > > > > > > Previously it was possible to use WebSocketRequestHandler to > push > > > > > updated > > > > > > > component . > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > > > > solomax...@gmail.com > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Thanks a lot Tobias! > > > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > > > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > > > > > > > > > >> Hi Maxim, > > > > > > > >> > > > > > > > >> no problem I am going to add the getter this evening. Thank > > you > > > > for > > > > > > your > > > > > > > >> suggestions! :-) > > > > > > > >> > > > > > > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime > of > > > the > > > > > > > >> buildbot server. However the build was triggered already. > > > > > > > >> > > > > > > > >> kind regards > > > > > > > >> > > > > > > > >> Tobias > > > > > > > >> > > > > > > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > > > > > > solomax...@gmail.com > > > > > > > >: > > > > > > > >> > > > > > > > > >> > Thanks a lot for the changes Tobias, > > > > > > > >> > Unfortunately I'm unable to test it due to latest > > > 7.0.0-SNAPSHOT > > > > > > seems > > > > > > > >> > doesn't contain it :( > > > > > > > >> > > > > > > > > >> > And one more question: I would like to be able to modify > > > > > > > PageParameters > > > > > > > >> > passed to source, maybe it would be possible to add public > > > > getter > > > > > > for > > > > > > > >> it? > > > > > > > >> > > > > > > > > >> > Thanks in advance > > > > > > > >> > > > > > > > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > > > > > >> > tobiassolosche...@googlemail.com> wrote: > > > > > > > >> > > > > > > > > >> >> Hi Maxim, > > > > > > > >> >> > > > > > > > >> >> hope the change is like you wanted it to be: > > > > > > > >> >> > > > > > > > >
Re: Wicket7: MediaComponent and Source classes
Hello Martin, I guess following method need to be additionally updated: org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov wrote: > The change is rather big: > > https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af > I guess many other methods will need to be changed too if one needs to use > them with WebSocket. > The improvement in the Wicket API looked so innocent ... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik > wrote: > > > Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > > Sorry, forgot about Sebastians vacation :( > > > > On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov > > wrote: > > > > > @Maxim: Please create an issue at Wicket jQuery UI github. > > > Sebastien is on vacation. I can do it but first I need a good reason > for > > > the change :-) > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < > solomax...@gmail.com> > > > wrote: > > > > > > > @Sebastian could you please modify AbstractDialog.open method to be > > > > > > > > public final void open(IPartialPageRequestHandler target) > > > > instead of > > > > public final void open(AjaxRequestTarget target) > > > > > > > > Thanks in advance! > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < > mgrigo...@apache.org> > > > > wrote: > > > > > > > > > Yes, another minor cleanup: there is now > > > > > > > > > > > > > > > > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > > > > > A base interface for Ajax and WebSocket. > > > > > > > > > > Martin Grigorov > > > > > Freelancer. Available for hire! > > > > > Wicket Training and Consulting > > > > > https://twitter.com/mtgrigorov > > > > > > > > > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > > > solomax...@gmail.com> > > > > > wrote: > > > > > > > > > > > Additionally it looks like WebSocketRequestHandler can not be > used > > > > > > as AjaxRequestTarget any longer > > > > > > Previously it was possible to use WebSocketRequestHandler to push > > > > updated > > > > > > component . > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > > > solomax...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > Thanks a lot Tobias! > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > > > > > > > >> Hi Maxim, > > > > > > >> > > > > > > >> no problem I am going to add the getter this evening. Thank > you > > > for > > > > > your > > > > > > >> suggestions! :-) > > > > > > >> > > > > > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of > > the > > > > > > >> buildbot server. However the build was triggered already. > > > > > > >> > > > > > > >> kind regards > > > > > > >> > > > > > > >> Tobias > > > > > > >> > > > > > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > > > > > solomax...@gmail.com > > > > > > >: > > > > > > >> > > > > > > > >> > Thanks a lot for the changes Tobias, > > > > > > >> > Unfortunately I'm unable to test it due to latest > > 7.0.0-SNAPSHOT > > > > > seems > > > > > > >> > doesn't contain it :( > > > > > > >> > > > > > > > >> > And one more question: I would like to be able to modify > > > > > > PageParameters > > > > > > >> > passed to source, maybe it would be possible to add public > > > getter > > > > > for > > > > > > >> it? > > > > > > >> > > > > > > > >> > Thanks in advance > > > > > > >> > > > > > > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > > > > >> > tobiassolosche...@googlemail.com> wrote: > > > > > > >> > > > > > > > >> >> Hi Maxim, > > > > > > >> >> > > > > > > >> >> hope the change is like you wanted it to be: > > > > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > > > > >> >> > > > > > > >> >> But again: The PackageResourceReference is best practice, > > > because > > > > > you > > > > > > >> also > > > > > > >> >> can use "readBuffered(false)" of it - with this option the > > > > resource > > > > > > is > > > > > > >> >> streamed directly without loading it into memory. For more > > > > > > information > > > > > > >> >> refer to the Javadoc of the method. > > > > > > >> >> > > > > > > >> >> kind regards > > > > > > >> >> > > > > > > >> >> Tobias > > > > > > >> >> > > > > > > >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > > > > >> >>> > > > > > > >> >>> Thanks a lot! > > > > > > >> >>> It was gmail SPAM filter :((( > > > >
Re: Wicket7: MediaComponent and Source classes
Hi, just wanted to mention that there are getter / setter for the PageParameters, now. kind regards Tobias Am 02.07.15 um 16:21 schrieb Maxim Solodovnik: I also doing this regularly :) WBR, Maxim (from mobile, sorry for the typos) On Jul 2, 2015 8:09 PM, "Ernesto Reinaldo Barreiro" wrote: Doing it all the time :-) On Thu, Jul 2, 2015 at 3:56 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: Hi, I send a request to the google forum and they answered that I have to bring enought users to unmark my Mails as Spam. So if all who receiving my mails please click at "this is not a Spam Mail" kind regards Tobias Am 02.07.2015 um 11:25 schrieb Ernesto Reinaldo Barreiro < reier...@gmail.com>: @Tobias, OT: For some obscure reason your massages always goo into my Span account at gmail... On Thu, Jul 2, 2015 at 9:03 AM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: Hi Maxim, no problem I am going to add the getter this evening. Thank you for your suggestions! :-) Maybe the SNAPSHOT isn't refreshed because of the downtime of the buildbot server. However the build was triggered already. kind regards Tobias Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < solomax...@gmail.com : Thanks a lot for the changes Tobias, Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems doesn't contain it :( And one more question: I would like to be able to modify PageParameters passed to source, maybe it would be possible to add public getter for it? Thanks in advance On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: Hi Maxim, hope the change is like you wanted it to be: https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 But again: The PackageResourceReference is best practice, because you also can use "readBuffered(false)" of it - with this option the resource is streamed directly without loading it into memory. For more information refer to the Javadoc of the method. kind regards Tobias Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: Thanks a lot! It was gmail SPAM filter :((( will do migration and examine examples On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < mgrigo...@apache.org wrote: For some reason Tobias' mails are marked as SPAM by GMail... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < solomax...@gmail.com wrote: sorry, most probably missed that email Thanks! On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < mgrigo...@apache.org> wrote: Tobias already explained that it was an oversight and he is going to improve it tonight. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < solomax...@gmail.com wrote: Thanks Martin :) will look through sources :) can you please tell me why PackageResourceReference is being used in MediaComponent and not ResourceReference? Or maybe Tobias can answer this question? On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < mgrigo...@apache.org wrote: Everything is possible. All I need is longer day. 24 hours are not enough... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < solomax...@gmail.com wrote: Is it possible update http://www.wicket-library.com/ to have wicket7 examples as well? I believe this might be very useful :) On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < an.delb...@gmail.com wrote: Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of improvements: 1) AbstractResource is now supports "content-range" and "accept-range" which is great! I'll remove my custom code for this :) 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) which is great :)) 3) MediaComponent requires *PackageResourceReference* as resourceReference :(( why it can't be ResourceReference? Are there any examples in wicket7 regarding new Video Component? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- WBR Maxim aka solomax -- WBR Maxim aka solomax -- WBR Maxim aka solomax - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- WBR Maxim aka solomax - To unsubscrib
Re: Wicket7: MediaComponent and Source classes
I also doing this regularly :) WBR, Maxim (from mobile, sorry for the typos) On Jul 2, 2015 8:09 PM, "Ernesto Reinaldo Barreiro" wrote: > Doing it all the time :-) > > On Thu, Jul 2, 2015 at 3:56 PM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > > > Hi, > > > > I send a request to the google forum and they answered that I have to > > bring enought users to unmark my Mails as Spam. > > > > So if all who receiving my mails please click at "this is not a Spam > Mail" > > > > kind regards > > > > Tobias > > > > > Am 02.07.2015 um 11:25 schrieb Ernesto Reinaldo Barreiro < > > reier...@gmail.com>: > > > > > > @Tobias, > > > > > > OT: For some obscure reason your massages always goo into my Span > account > > > at gmail... > > > > > > On Thu, Jul 2, 2015 at 9:03 AM, Tobias Soloschenko < > > > tobiassolosche...@googlemail.com> wrote: > > > > > >> Hi Maxim, > > >> > > >> no problem I am going to add the getter this evening. Thank you for > your > > >> suggestions! :-) > > >> > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the > > buildbot > > >> server. However the build was triggered already. > > >> > > >> kind regards > > >> > > >> Tobias > > >> > > >>> Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > solomax...@gmail.com > > >: > > >>> > > >>> Thanks a lot for the changes Tobias, > > >>> Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT > seems > > >>> doesn't contain it :( > > >>> > > >>> And one more question: I would like to be able to modify > PageParameters > > >>> passed to source, maybe it would be possible to add public getter for > > it? > > >>> > > >>> Thanks in advance > > >>> > > >>> On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > >>> tobiassolosche...@googlemail.com> wrote: > > >>> > > Hi Maxim, > > > > hope the change is like you wanted it to be: > > >> > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > > But again: The PackageResourceReference is best practice, because > you > > >> also > > can use "readBuffered(false)" of it - with this option the resource > is > > streamed directly without loading it into memory. For more > information > > refer to the Javadoc of the method. > > > > kind regards > > > > Tobias > > > > > Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > > > > Thanks a lot! > > > It was gmail SPAM filter :((( > > > will do migration and examine examples > > > > > > On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > > mgrigo...@apache.org > > >>> > > > wrote: > > > > > > For some reason Tobias' mails are marked as SPAM by GMail... > > >> > > >> Martin Grigorov > > >> Freelancer. Available for hire! > > >> Wicket Training and Consulting > > >> https://twitter.com/mtgrigorov > > >> > > >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > > >> solomax...@gmail.com > > >> wrote: > > >> > > >> sorry, most probably missed that email > > >>> Thanks! > > >>> > > >>> On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > > >> mgrigo...@apache.org> > > >>> wrote: > > >>> > > >>> Tobias already explained that it was an oversight and he is going > > to > > improve it tonight. > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > > >>> solomax...@gmail.com > > >> > > >>> wrote: > > > > Thanks Martin :) > > > will look through sources :) > > > > > > can you please tell me why PackageResourceReference is being > used > > >> in > > > MediaComponent and not ResourceReference? Or maybe Tobias can > > >> answer > > this > > >>> > > question? > > > > > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > > mgrigo...@apache.org > > >> > > >>> wrote: > > > > > > Everything is possible. > > >> All I need is longer day. 24 hours are not enough... > > >> > > >> Martin Grigorov > > >> Freelancer. Available for hire! > > >> Wicket Training and Consulting > > >> https://twitter.com/mtgrigorov > > >> > > >> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > > solomax...@gmail.com > > > > > wrote: > > >> > > >> Is it possible update http://www.wicket-library.com/ to have > > >> wicket7 > > >>> > > examples as well? > > >>> I believe this might be very useful :) > > >>> > > >>> On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > >> an.delb...@gmail.com > > > > > wrote: > > >>> > > >>> Hi, >
Re: Wicket7: MediaComponent and Source classes
Doing it all the time :-) On Thu, Jul 2, 2015 at 3:56 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi, > > I send a request to the google forum and they answered that I have to > bring enought users to unmark my Mails as Spam. > > So if all who receiving my mails please click at "this is not a Spam Mail" > > kind regards > > Tobias > > > Am 02.07.2015 um 11:25 schrieb Ernesto Reinaldo Barreiro < > reier...@gmail.com>: > > > > @Tobias, > > > > OT: For some obscure reason your massages always goo into my Span account > > at gmail... > > > > On Thu, Jul 2, 2015 at 9:03 AM, Tobias Soloschenko < > > tobiassolosche...@googlemail.com> wrote: > > > >> Hi Maxim, > >> > >> no problem I am going to add the getter this evening. Thank you for your > >> suggestions! :-) > >> > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the > buildbot > >> server. However the build was triggered already. > >> > >> kind regards > >> > >> Tobias > >> > >>> Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik >: > >>> > >>> Thanks a lot for the changes Tobias, > >>> Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems > >>> doesn't contain it :( > >>> > >>> And one more question: I would like to be able to modify PageParameters > >>> passed to source, maybe it would be possible to add public getter for > it? > >>> > >>> Thanks in advance > >>> > >>> On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > >>> tobiassolosche...@googlemail.com> wrote: > >>> > Hi Maxim, > > hope the change is like you wanted it to be: > >> > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > But again: The PackageResourceReference is best practice, because you > >> also > can use "readBuffered(false)" of it - with this option the resource is > streamed directly without loading it into memory. For more information > refer to the Javadoc of the method. > > kind regards > > Tobias > > > Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > > Thanks a lot! > > It was gmail SPAM filter :((( > > will do migration and examine examples > > > > On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > mgrigo...@apache.org > >>> > > wrote: > > > > For some reason Tobias' mails are marked as SPAM by GMail... > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > >> solomax...@gmail.com > >> wrote: > >> > >> sorry, most probably missed that email > >>> Thanks! > >>> > >>> On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > >> mgrigo...@apache.org> > >>> wrote: > >>> > >>> Tobias already explained that it was an oversight and he is going > to > improve it tonight. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > >>> solomax...@gmail.com > >> > >>> wrote: > > Thanks Martin :) > > will look through sources :) > > > > can you please tell me why PackageResourceReference is being used > >> in > > MediaComponent and not ResourceReference? Or maybe Tobias can > >> answer > this > >>> > question? > > > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > mgrigo...@apache.org > >> > >>> wrote: > > > > Everything is possible. > >> All I need is longer day. 24 hours are not enough... > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > solomax...@gmail.com > > > wrote: > >> > >> Is it possible update http://www.wicket-library.com/ to have > >> wicket7 > >>> > examples as well? > >>> I believe this might be very useful :) > >>> > >>> On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > >> an.delb...@gmail.com > > > wrote: > >>> > >>> Hi, > > in wicket-examples take a look at the project in > org.apache.wicket.examples.media > > Andrea. > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > Hello All, > > > > Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > found > >>> > lots > > > >> of > >>> > impro
Re: Wicket7: MediaComponent and Source classes
Hi, I send a request to the google forum and they answered that I have to bring enought users to unmark my Mails as Spam. So if all who receiving my mails please click at "this is not a Spam Mail" kind regards Tobias > Am 02.07.2015 um 11:25 schrieb Ernesto Reinaldo Barreiro : > > @Tobias, > > OT: For some obscure reason your massages always goo into my Span account > at gmail... > > On Thu, Jul 2, 2015 at 9:03 AM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > >> Hi Maxim, >> >> no problem I am going to add the getter this evening. Thank you for your >> suggestions! :-) >> >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the buildbot >> server. However the build was triggered already. >> >> kind regards >> >> Tobias >> >>> Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik : >>> >>> Thanks a lot for the changes Tobias, >>> Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems >>> doesn't contain it :( >>> >>> And one more question: I would like to be able to modify PageParameters >>> passed to source, maybe it would be possible to add public getter for it? >>> >>> Thanks in advance >>> >>> On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < >>> tobiassolosche...@googlemail.com> wrote: >>> Hi Maxim, hope the change is like you wanted it to be: >> https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 But again: The PackageResourceReference is best practice, because you >> also can use "readBuffered(false)" of it - with this option the resource is streamed directly without loading it into memory. For more information refer to the Javadoc of the method. kind regards Tobias > Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > Thanks a lot! > It was gmail SPAM filter :((( > will do migration and examine examples > > On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov >> > wrote: > > For some reason Tobias' mails are marked as SPAM by GMail... >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < >> solomax...@gmail.com >> wrote: >> >> sorry, most probably missed that email >>> Thanks! >>> >>> On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < >> mgrigo...@apache.org> >>> wrote: >>> >>> Tobias already explained that it was an oversight and he is going to improve it tonight. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < >>> solomax...@gmail.com >> >>> wrote: Thanks Martin :) > will look through sources :) > > can you please tell me why PackageResourceReference is being used >> in > MediaComponent and not ResourceReference? Or maybe Tobias can >> answer this >>> question? > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < mgrigo...@apache.org >> >>> wrote: > > Everything is possible. >> All I need is longer day. 24 hours are not enough... >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > solomax...@gmail.com > wrote: >> >> Is it possible update http://www.wicket-library.com/ to have >> wicket7 >>> examples as well? >>> I believe this might be very useful :) >>> >>> On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < >> an.delb...@gmail.com > wrote: >>> >>> Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, > > Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found >>> lots > >> of >>> improvements: > 1) AbstractResource is now supports "content-range" and "accept-range" > >> which is great! I'll remove my custom code for this :) > 2) HTML5 Video is supported by wicket itself (was removed from > wicketstuff) > which is great :)) > > 3) MediaComponent requires *PackageResourceReference* as resourceReference
Re: Wicket7: MediaComponent and Source classes
Thanks a million! Could you please publish SNAPSHOT so I can test it? On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov wrote: > The change is rather big: > > https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af > I guess many other methods will need to be changed too if one needs to use > them with WebSocket. > The improvement in the Wicket API looked so innocent ... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik > wrote: > > > Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > > Sorry, forgot about Sebastians vacation :( > > > > On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov > > wrote: > > > > > @Maxim: Please create an issue at Wicket jQuery UI github. > > > Sebastien is on vacation. I can do it but first I need a good reason > for > > > the change :-) > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik < > solomax...@gmail.com> > > > wrote: > > > > > > > @Sebastian could you please modify AbstractDialog.open method to be > > > > > > > > public final void open(IPartialPageRequestHandler target) > > > > instead of > > > > public final void open(AjaxRequestTarget target) > > > > > > > > Thanks in advance! > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov < > mgrigo...@apache.org> > > > > wrote: > > > > > > > > > Yes, another minor cleanup: there is now > > > > > > > > > > > > > > > > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > > > > > A base interface for Ajax and WebSocket. > > > > > > > > > > Martin Grigorov > > > > > Freelancer. Available for hire! > > > > > Wicket Training and Consulting > > > > > https://twitter.com/mtgrigorov > > > > > > > > > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > > > solomax...@gmail.com> > > > > > wrote: > > > > > > > > > > > Additionally it looks like WebSocketRequestHandler can not be > used > > > > > > as AjaxRequestTarget any longer > > > > > > Previously it was possible to use WebSocketRequestHandler to push > > > > updated > > > > > > component . > > > > > > > > > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > > > solomax...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > Thanks a lot Tobias! > > > > > > > > > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > > > > > > > >> Hi Maxim, > > > > > > >> > > > > > > >> no problem I am going to add the getter this evening. Thank > you > > > for > > > > > your > > > > > > >> suggestions! :-) > > > > > > >> > > > > > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of > > the > > > > > > >> buildbot server. However the build was triggered already. > > > > > > >> > > > > > > >> kind regards > > > > > > >> > > > > > > >> Tobias > > > > > > >> > > > > > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > > > > > solomax...@gmail.com > > > > > > >: > > > > > > >> > > > > > > > >> > Thanks a lot for the changes Tobias, > > > > > > >> > Unfortunately I'm unable to test it due to latest > > 7.0.0-SNAPSHOT > > > > > seems > > > > > > >> > doesn't contain it :( > > > > > > >> > > > > > > > >> > And one more question: I would like to be able to modify > > > > > > PageParameters > > > > > > >> > passed to source, maybe it would be possible to add public > > > getter > > > > > for > > > > > > >> it? > > > > > > >> > > > > > > > >> > Thanks in advance > > > > > > >> > > > > > > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > > > > >> > tobiassolosche...@googlemail.com> wrote: > > > > > > >> > > > > > > > >> >> Hi Maxim, > > > > > > >> >> > > > > > > >> >> hope the change is like you wanted it to be: > > > > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > > > > >> >> > > > > > > >> >> But again: The PackageResourceReference is best practice, > > > because > > > > > you > > > > > > >> also > > > > > > >> >> can use "readBuffered(false)" of it - with this option the > > > > resource > > > > > > is > > > > > > >> >> streamed directly without loading it into memory. For more > > > > > > information > > > > > > >> >> refer to the Javadoc of the method. > > > > > > >> >> > > > > > > >> >> kind regards > > > > > > >> >> > > > > > > >> >> Tobias > > > > > > >> >> > > > > > > >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > > > > >> >>> > > > > > > >> >>> Thanks a lot! > > > > > > >> >>> It was gmail SPAM filter :((( > > > > > > >> >>> will do migration and examine examples > > > > > >
Re: Wicket7: MediaComponent and Source classes
The change is rather big: https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af I guess many other methods will need to be changed too if one needs to use them with WebSocket. The improvement in the Wicket API looked so innocent ... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 2:28 PM, Maxim Solodovnik wrote: > Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 > Sorry, forgot about Sebastians vacation :( > > On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov > wrote: > > > @Maxim: Please create an issue at Wicket jQuery UI github. > > Sebastien is on vacation. I can do it but first I need a good reason for > > the change :-) > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik > > wrote: > > > > > @Sebastian could you please modify AbstractDialog.open method to be > > > > > > public final void open(IPartialPageRequestHandler target) > > > instead of > > > public final void open(AjaxRequestTarget target) > > > > > > Thanks in advance! > > > > > > > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov > > > wrote: > > > > > > > Yes, another minor cleanup: there is now > > > > > > > > > > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > > > > A base interface for Ajax and WebSocket. > > > > > > > > Martin Grigorov > > > > Freelancer. Available for hire! > > > > Wicket Training and Consulting > > > > https://twitter.com/mtgrigorov > > > > > > > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > > solomax...@gmail.com> > > > > wrote: > > > > > > > > > Additionally it looks like WebSocketRequestHandler can not be used > > > > > as AjaxRequestTarget any longer > > > > > Previously it was possible to use WebSocketRequestHandler to push > > > updated > > > > > component . > > > > > > > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > > solomax...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Thanks a lot Tobias! > > > > > > > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > > > > > >> Hi Maxim, > > > > > >> > > > > > >> no problem I am going to add the getter this evening. Thank you > > for > > > > your > > > > > >> suggestions! :-) > > > > > >> > > > > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of > the > > > > > >> buildbot server. However the build was triggered already. > > > > > >> > > > > > >> kind regards > > > > > >> > > > > > >> Tobias > > > > > >> > > > > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > > > > solomax...@gmail.com > > > > > >: > > > > > >> > > > > > > >> > Thanks a lot for the changes Tobias, > > > > > >> > Unfortunately I'm unable to test it due to latest > 7.0.0-SNAPSHOT > > > > seems > > > > > >> > doesn't contain it :( > > > > > >> > > > > > > >> > And one more question: I would like to be able to modify > > > > > PageParameters > > > > > >> > passed to source, maybe it would be possible to add public > > getter > > > > for > > > > > >> it? > > > > > >> > > > > > > >> > Thanks in advance > > > > > >> > > > > > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > > > >> > tobiassolosche...@googlemail.com> wrote: > > > > > >> > > > > > > >> >> Hi Maxim, > > > > > >> >> > > > > > >> >> hope the change is like you wanted it to be: > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> > > > > > > > > > > > > > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > > > >> >> > > > > > >> >> But again: The PackageResourceReference is best practice, > > because > > > > you > > > > > >> also > > > > > >> >> can use "readBuffered(false)" of it - with this option the > > > resource > > > > > is > > > > > >> >> streamed directly without loading it into memory. For more > > > > > information > > > > > >> >> refer to the Javadoc of the method. > > > > > >> >> > > > > > >> >> kind regards > > > > > >> >> > > > > > >> >> Tobias > > > > > >> >> > > > > > >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > > > >> >>> > > > > > >> >>> Thanks a lot! > > > > > >> >>> It was gmail SPAM filter :((( > > > > > >> >>> will do migration and examine examples > > > > > >> >>> > > > > > >> >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > > > > > >> mgrigo...@apache.org> > > > > > >> >>> wrote: > > > > > >> >>> > > > > > >> >>> For some reason Tobias' mails are marked as SPAM by GMail... > > > > > >> > > > > > >> Martin Grigorov > > > > > >> Freelancer. Available for hire! > > > > > >> Wicket Training and Consulting > > > > > >> https://twitter.com/mtgrigorov > > > > > >> > > > > > >> On Mon, Jun 29, 2
Re: Wicket7: MediaComponent and Source classes
Done: https://github.com/sebfz1/wicket-jquery-ui/issues/177 Sorry, forgot about Sebastians vacation :( On Thu, Jul 2, 2015 at 5:23 PM, Martin Grigorov wrote: > @Maxim: Please create an issue at Wicket jQuery UI github. > Sebastien is on vacation. I can do it but first I need a good reason for > the change :-) > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik > wrote: > > > @Sebastian could you please modify AbstractDialog.open method to be > > > > public final void open(IPartialPageRequestHandler target) > > instead of > > public final void open(AjaxRequestTarget target) > > > > Thanks in advance! > > > > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov > > wrote: > > > > > Yes, another minor cleanup: there is now > > > > > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > > > A base interface for Ajax and WebSocket. > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik < > solomax...@gmail.com> > > > wrote: > > > > > > > Additionally it looks like WebSocketRequestHandler can not be used > > > > as AjaxRequestTarget any longer > > > > Previously it was possible to use WebSocketRequestHandler to push > > updated > > > > component . > > > > > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik < > solomax...@gmail.com > > > > > > > wrote: > > > > > > > > > Thanks a lot Tobias! > > > > > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > > > >> Hi Maxim, > > > > >> > > > > >> no problem I am going to add the getter this evening. Thank you > for > > > your > > > > >> suggestions! :-) > > > > >> > > > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the > > > > >> buildbot server. However the build was triggered already. > > > > >> > > > > >> kind regards > > > > >> > > > > >> Tobias > > > > >> > > > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > > > solomax...@gmail.com > > > > >: > > > > >> > > > > > >> > Thanks a lot for the changes Tobias, > > > > >> > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT > > > seems > > > > >> > doesn't contain it :( > > > > >> > > > > > >> > And one more question: I would like to be able to modify > > > > PageParameters > > > > >> > passed to source, maybe it would be possible to add public > getter > > > for > > > > >> it? > > > > >> > > > > > >> > Thanks in advance > > > > >> > > > > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > > >> > tobiassolosche...@googlemail.com> wrote: > > > > >> > > > > > >> >> Hi Maxim, > > > > >> >> > > > > >> >> hope the change is like you wanted it to be: > > > > >> >> > > > > >> >> > > > > >> >> > > > > >> > > > > > > > > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > > >> >> > > > > >> >> But again: The PackageResourceReference is best practice, > because > > > you > > > > >> also > > > > >> >> can use "readBuffered(false)" of it - with this option the > > resource > > > > is > > > > >> >> streamed directly without loading it into memory. For more > > > > information > > > > >> >> refer to the Javadoc of the method. > > > > >> >> > > > > >> >> kind regards > > > > >> >> > > > > >> >> Tobias > > > > >> >> > > > > >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > > >> >>> > > > > >> >>> Thanks a lot! > > > > >> >>> It was gmail SPAM filter :((( > > > > >> >>> will do migration and examine examples > > > > >> >>> > > > > >> >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > > > > >> mgrigo...@apache.org> > > > > >> >>> wrote: > > > > >> >>> > > > > >> >>> For some reason Tobias' mails are marked as SPAM by GMail... > > > > >> > > > > >> Martin Grigorov > > > > >> Freelancer. Available for hire! > > > > >> Wicket Training and Consulting > > > > >> https://twitter.com/mtgrigorov > > > > >> > > > > >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > > > > >> solomax...@gmail.com > > > > >> > > > > > >> wrote: > > > > >> > > > > >> sorry, most probably missed that email > > > > >> > Thanks! > > > > >> > > > > > >> > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > > > > >> mgrigo...@apache.org> > > > > >> > wrote: > > > > >> > > > > > >> > Tobias already explained that it was an oversight and he is > > > going > > > > to > > > > >> >> improve it tonight. > > > > >> >> > > > > >> >> Martin Grigorov > > > > >> >> Freelancer. Available for hire! > > > > >> >> Wicket Training and Consulting > > > > >> >> https://twitter.com/mtgrigorov > > > > >> >> > > > > >>
Re: Wicket7: MediaComponent and Source classes
@Maxim: Please create an issue at Wicket jQuery UI github. Sebastien is on vacation. I can do it but first I need a good reason for the change :-) Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 12:33 PM, Maxim Solodovnik wrote: > @Sebastian could you please modify AbstractDialog.open method to be > > public final void open(IPartialPageRequestHandler target) > instead of > public final void open(AjaxRequestTarget target) > > Thanks in advance! > > > On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov > wrote: > > > Yes, another minor cleanup: there is now > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > > A base interface for Ajax and WebSocket. > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik > > wrote: > > > > > Additionally it looks like WebSocketRequestHandler can not be used > > > as AjaxRequestTarget any longer > > > Previously it was possible to use WebSocketRequestHandler to push > updated > > > component . > > > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik > > > > wrote: > > > > > > > Thanks a lot Tobias! > > > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > >> Hi Maxim, > > > >> > > > >> no problem I am going to add the getter this evening. Thank you for > > your > > > >> suggestions! :-) > > > >> > > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the > > > >> buildbot server. However the build was triggered already. > > > >> > > > >> kind regards > > > >> > > > >> Tobias > > > >> > > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > > solomax...@gmail.com > > > >: > > > >> > > > > >> > Thanks a lot for the changes Tobias, > > > >> > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT > > seems > > > >> > doesn't contain it :( > > > >> > > > > >> > And one more question: I would like to be able to modify > > > PageParameters > > > >> > passed to source, maybe it would be possible to add public getter > > for > > > >> it? > > > >> > > > > >> > Thanks in advance > > > >> > > > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > >> > tobiassolosche...@googlemail.com> wrote: > > > >> > > > > >> >> Hi Maxim, > > > >> >> > > > >> >> hope the change is like you wanted it to be: > > > >> >> > > > >> >> > > > >> >> > > > >> > > > > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > >> >> > > > >> >> But again: The PackageResourceReference is best practice, because > > you > > > >> also > > > >> >> can use "readBuffered(false)" of it - with this option the > resource > > > is > > > >> >> streamed directly without loading it into memory. For more > > > information > > > >> >> refer to the Javadoc of the method. > > > >> >> > > > >> >> kind regards > > > >> >> > > > >> >> Tobias > > > >> >> > > > >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > >> >>> > > > >> >>> Thanks a lot! > > > >> >>> It was gmail SPAM filter :((( > > > >> >>> will do migration and examine examples > > > >> >>> > > > >> >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > > > >> mgrigo...@apache.org> > > > >> >>> wrote: > > > >> >>> > > > >> >>> For some reason Tobias' mails are marked as SPAM by GMail... > > > >> > > > >> Martin Grigorov > > > >> Freelancer. Available for hire! > > > >> Wicket Training and Consulting > > > >> https://twitter.com/mtgrigorov > > > >> > > > >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > > > >> solomax...@gmail.com > > > >> > > > > >> wrote: > > > >> > > > >> sorry, most probably missed that email > > > >> > Thanks! > > > >> > > > > >> > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > > > >> mgrigo...@apache.org> > > > >> > wrote: > > > >> > > > > >> > Tobias already explained that it was an oversight and he is > > going > > > to > > > >> >> improve it tonight. > > > >> >> > > > >> >> Martin Grigorov > > > >> >> Freelancer. Available for hire! > > > >> >> Wicket Training and Consulting > > > >> >> https://twitter.com/mtgrigorov > > > >> >> > > > >> >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > > > >> >> > > > >> > solomax...@gmail.com > > > >> > > > >> > wrote: > > > >> >> > > > >> >> Thanks Martin :) > > > >> >>> will look through sources :) > > > >> >>> > > > >> >>> can you please tell me why PackageResourceReference is being > > > used > > > >> in > > > >> >>> MediaComponent and not ResourceReference? Or maybe Tobias > can > > > >> answer > > > >> >>> > > > >> >> this > > > >> > > > > >> >
Re: Wicket7: MediaComponent and Source classes
@Sebastian could you please modify AbstractDialog.open method to be public final void open(IPartialPageRequestHandler target) instead of public final void open(AjaxRequestTarget target) Thanks in advance! On Thu, Jul 2, 2015 at 2:58 PM, Martin Grigorov wrote: > Yes, another minor cleanup: there is now > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java > A base interface for Ajax and WebSocket. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik > wrote: > > > Additionally it looks like WebSocketRequestHandler can not be used > > as AjaxRequestTarget any longer > > Previously it was possible to use WebSocketRequestHandler to push updated > > component . > > > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik > > wrote: > > > > > Thanks a lot Tobias! > > > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > > tobiassolosche...@googlemail.com> wrote: > > > > > >> Hi Maxim, > > >> > > >> no problem I am going to add the getter this evening. Thank you for > your > > >> suggestions! :-) > > >> > > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the > > >> buildbot server. However the build was triggered already. > > >> > > >> kind regards > > >> > > >> Tobias > > >> > > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > solomax...@gmail.com > > >: > > >> > > > >> > Thanks a lot for the changes Tobias, > > >> > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT > seems > > >> > doesn't contain it :( > > >> > > > >> > And one more question: I would like to be able to modify > > PageParameters > > >> > passed to source, maybe it would be possible to add public getter > for > > >> it? > > >> > > > >> > Thanks in advance > > >> > > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > >> > tobiassolosche...@googlemail.com> wrote: > > >> > > > >> >> Hi Maxim, > > >> >> > > >> >> hope the change is like you wanted it to be: > > >> >> > > >> >> > > >> >> > > >> > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > >> >> > > >> >> But again: The PackageResourceReference is best practice, because > you > > >> also > > >> >> can use "readBuffered(false)" of it - with this option the resource > > is > > >> >> streamed directly without loading it into memory. For more > > information > > >> >> refer to the Javadoc of the method. > > >> >> > > >> >> kind regards > > >> >> > > >> >> Tobias > > >> >> > > >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > >> >>> > > >> >>> Thanks a lot! > > >> >>> It was gmail SPAM filter :((( > > >> >>> will do migration and examine examples > > >> >>> > > >> >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > > >> mgrigo...@apache.org> > > >> >>> wrote: > > >> >>> > > >> >>> For some reason Tobias' mails are marked as SPAM by GMail... > > >> > > >> Martin Grigorov > > >> Freelancer. Available for hire! > > >> Wicket Training and Consulting > > >> https://twitter.com/mtgrigorov > > >> > > >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > > >> solomax...@gmail.com > > >> > > > >> wrote: > > >> > > >> sorry, most probably missed that email > > >> > Thanks! > > >> > > > >> > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > > >> mgrigo...@apache.org> > > >> > wrote: > > >> > > > >> > Tobias already explained that it was an oversight and he is > going > > to > > >> >> improve it tonight. > > >> >> > > >> >> Martin Grigorov > > >> >> Freelancer. Available for hire! > > >> >> Wicket Training and Consulting > > >> >> https://twitter.com/mtgrigorov > > >> >> > > >> >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > > >> >> > > >> > solomax...@gmail.com > > >> > > >> > wrote: > > >> >> > > >> >> Thanks Martin :) > > >> >>> will look through sources :) > > >> >>> > > >> >>> can you please tell me why PackageResourceReference is being > > used > > >> in > > >> >>> MediaComponent and not ResourceReference? Or maybe Tobias can > > >> answer > > >> >>> > > >> >> this > > >> > > > >> >> question? > > >> >>> > > >> >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > > >> >>> > > >> >> mgrigo...@apache.org > > >> > > >> > wrote: > > >> >>> > > >> >>> Everything is possible. > > >> All I need is longer day. 24 hours are not enough... > > >> > > >> Martin Grigorov > > >> Freelancer. Available for hire! > > >> Wicket Training and Consulting > > >> https://twitter.com/mtgrigorov > > >> > > >> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > >> > > >> >>> solomax...@gmail.co
Re: Wicket7: MediaComponent and Source classes
@Tobias, OT: For some obscure reason your massages always goo into my Span account at gmail... On Thu, Jul 2, 2015 at 9:03 AM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Maxim, > > no problem I am going to add the getter this evening. Thank you for your > suggestions! :-) > > Maybe the SNAPSHOT isn't refreshed because of the downtime of the buildbot > server. However the build was triggered already. > > kind regards > > Tobias > > > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik : > > > > Thanks a lot for the changes Tobias, > > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems > > doesn't contain it :( > > > > And one more question: I would like to be able to modify PageParameters > > passed to source, maybe it would be possible to add public getter for it? > > > > Thanks in advance > > > > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > tobiassolosche...@googlemail.com> wrote: > > > >> Hi Maxim, > >> > >> hope the change is like you wanted it to be: > >> > >> > >> > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > >> > >> But again: The PackageResourceReference is best practice, because you > also > >> can use "readBuffered(false)" of it - with this option the resource is > >> streamed directly without loading it into memory. For more information > >> refer to the Javadoc of the method. > >> > >> kind regards > >> > >> Tobias > >> > >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > >>> > >>> Thanks a lot! > >>> It was gmail SPAM filter :((( > >>> will do migration and examine examples > >>> > >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov > > >>> wrote: > >>> > >>> For some reason Tobias' mails are marked as SPAM by GMail... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > solomax...@gmail.com > > > wrote: > > sorry, most probably missed that email > > Thanks! > > > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > mgrigo...@apache.org> > > wrote: > > > > Tobias already explained that it was an oversight and he is going to > >> improve it tonight. > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > >> > > solomax...@gmail.com > > > wrote: > >> > >> Thanks Martin :) > >>> will look through sources :) > >>> > >>> can you please tell me why PackageResourceReference is being used > in > >>> MediaComponent and not ResourceReference? Or maybe Tobias can > answer > >>> > >> this > > > >> question? > >>> > >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > >>> > >> mgrigo...@apache.org > > > wrote: > >>> > >>> Everything is possible. > All I need is longer day. 24 hours are not enough... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > >>> solomax...@gmail.com > >> > >>> wrote: > > Is it possible update http://www.wicket-library.com/ to have > > > wicket7 > > > >> examples as well? > > I believe this might be very useful :) > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > > an.delb...@gmail.com > >> > >>> wrote: > > > > Hi, > >> > >> in wicket-examples take a look at the project in > >> org.apache.wicket.examples.media > >> > >> Andrea. > >> > >> > >> On 29/06/2015 06:47, Maxim Solodovnik wrote: > >> > >> Hello All, > >>> > >>> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > >>> > >> found > > > >> lots > >>> > of > > > >> improvements: > >>> 1) AbstractResource is now supports "content-range" and > >>> > >> "accept-range" > >>> > which is great! I'll remove my custom code for this :) > >>> 2) HTML5 Video is supported by wicket itself (was removed from > >>> wicketstuff) > >>> which is great :)) > >>> > >>> 3) MediaComponent requires *PackageResourceReference* as > >>> > >> resourceReference > > > >> :(( why it can't be ResourceReference? > >>> > >>> Are there any examples in wicket7 regarding new Video > >>> > >> Component? > > > Thanks in advance! > >>> > >>> > >
Re: Wicket7: MediaComponent and Source classes
Yes, another minor cleanup: there is now https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/request/handler/IPartialPageRequestHandler.java A base interface for Ajax and WebSocket. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 11:45 AM, Maxim Solodovnik wrote: > Additionally it looks like WebSocketRequestHandler can not be used > as AjaxRequestTarget any longer > Previously it was possible to use WebSocketRequestHandler to push updated > component . > > On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik > wrote: > > > Thanks a lot Tobias! > > > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > > tobiassolosche...@googlemail.com> wrote: > > > >> Hi Maxim, > >> > >> no problem I am going to add the getter this evening. Thank you for your > >> suggestions! :-) > >> > >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the > >> buildbot server. However the build was triggered already. > >> > >> kind regards > >> > >> Tobias > >> > >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik >: > >> > > >> > Thanks a lot for the changes Tobias, > >> > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems > >> > doesn't contain it :( > >> > > >> > And one more question: I would like to be able to modify > PageParameters > >> > passed to source, maybe it would be possible to add public getter for > >> it? > >> > > >> > Thanks in advance > >> > > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > >> > tobiassolosche...@googlemail.com> wrote: > >> > > >> >> Hi Maxim, > >> >> > >> >> hope the change is like you wanted it to be: > >> >> > >> >> > >> >> > >> > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > >> >> > >> >> But again: The PackageResourceReference is best practice, because you > >> also > >> >> can use "readBuffered(false)" of it - with this option the resource > is > >> >> streamed directly without loading it into memory. For more > information > >> >> refer to the Javadoc of the method. > >> >> > >> >> kind regards > >> >> > >> >> Tobias > >> >> > >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > >> >>> > >> >>> Thanks a lot! > >> >>> It was gmail SPAM filter :((( > >> >>> will do migration and examine examples > >> >>> > >> >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > >> mgrigo...@apache.org> > >> >>> wrote: > >> >>> > >> >>> For some reason Tobias' mails are marked as SPAM by GMail... > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > >> solomax...@gmail.com > >> > > >> wrote: > >> > >> sorry, most probably missed that email > >> > Thanks! > >> > > >> > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > >> mgrigo...@apache.org> > >> > wrote: > >> > > >> > Tobias already explained that it was an oversight and he is going > to > >> >> improve it tonight. > >> >> > >> >> Martin Grigorov > >> >> Freelancer. Available for hire! > >> >> Wicket Training and Consulting > >> >> https://twitter.com/mtgrigorov > >> >> > >> >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > >> >> > >> > solomax...@gmail.com > >> > >> > wrote: > >> >> > >> >> Thanks Martin :) > >> >>> will look through sources :) > >> >>> > >> >>> can you please tell me why PackageResourceReference is being > used > >> in > >> >>> MediaComponent and not ResourceReference? Or maybe Tobias can > >> answer > >> >>> > >> >> this > >> > > >> >> question? > >> >>> > >> >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > >> >>> > >> >> mgrigo...@apache.org > >> > >> > wrote: > >> >>> > >> >>> Everything is possible. > >> All I need is longer day. 24 hours are not enough... > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > >> > >> >>> solomax...@gmail.com > >> >> > >> >>> wrote: > >> > >> Is it possible update http://www.wicket-library.com/ to have > >> > > >> wicket7 > >> > > >> >> examples as well? > >> > I believe this might be very useful :) > >> > > >> > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > >> > > >> an.delb...@gmail.com > >> >> > >> >>> wrote: > >> > > >> > Hi, > >> >> > >> >> in wicket-examples take a look at the project in > >> >> org.apache.wicket.examples.media > >> >> > >
Re: Wicket7: MediaComponent and Source classes
Please see http://markmail.org/message/ji4nixgscvnbgi7z Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 11:41 AM, Maxim Solodovnik wrote: > Thanks for the clarifications Martin > This seems to be caching issue on my side > > Could you please answer additional question regarding ListView > It seems to be impossible in latest snapshot to create ListView("list", > new List()) > It was working as expected in M6 and previous versions > > On Thu, Jul 2, 2015 at 1:14 PM, Martin Grigorov > wrote: > > > There is a new build. The snapshots should be updated. > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Thu, Jul 2, 2015 at 10:03 AM, Tobias Soloschenko < > > tobiassolosche...@googlemail.com> wrote: > > > > > Hi Maxim, > > > > > > no problem I am going to add the getter this evening. Thank you for > your > > > suggestions! :-) > > > > > > Maybe the SNAPSHOT isn't refreshed because of the downtime of the > > buildbot > > > server. However the build was triggered already. > > > > > > kind regards > > > > > > Tobias > > > > > > > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik < > solomax...@gmail.com > > >: > > > > > > > > Thanks a lot for the changes Tobias, > > > > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT > seems > > > > doesn't contain it :( > > > > > > > > And one more question: I would like to be able to modify > PageParameters > > > > passed to source, maybe it would be possible to add public getter for > > it? > > > > > > > > Thanks in advance > > > > > > > > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > > tobiassolosche...@googlemail.com> wrote: > > > > > > > >> Hi Maxim, > > > >> > > > >> hope the change is like you wanted it to be: > > > >> > > > >> > > > >> > > > > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > >> > > > >> But again: The PackageResourceReference is best practice, because > you > > > also > > > >> can use "readBuffered(false)" of it - with this option the resource > is > > > >> streamed directly without loading it into memory. For more > information > > > >> refer to the Javadoc of the method. > > > >> > > > >> kind regards > > > >> > > > >> Tobias > > > >> > > > >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > >>> > > > >>> Thanks a lot! > > > >>> It was gmail SPAM filter :((( > > > >>> will do migration and examine examples > > > >>> > > > >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > > mgrigo...@apache.org > > > > > > > >>> wrote: > > > >>> > > > >>> For some reason Tobias' mails are marked as SPAM by GMail... > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > > > solomax...@gmail.com > > > > > > > wrote: > > > > > > sorry, most probably missed that email > > > > Thanks! > > > > > > > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > > > mgrigo...@apache.org> > > > > wrote: > > > > > > > > Tobias already explained that it was an oversight and he is going > > to > > > >> improve it tonight. > > > >> > > > >> Martin Grigorov > > > >> Freelancer. Available for hire! > > > >> Wicket Training and Consulting > > > >> https://twitter.com/mtgrigorov > > > >> > > > >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > > > >> > > > > solomax...@gmail.com > > > > > > > wrote: > > > >> > > > >> Thanks Martin :) > > > >>> will look through sources :) > > > >>> > > > >>> can you please tell me why PackageResourceReference is being > used > > > in > > > >>> MediaComponent and not ResourceReference? Or maybe Tobias can > > > answer > > > >>> > > > >> this > > > > > > > >> question? > > > >>> > > > >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > > > >>> > > > >> mgrigo...@apache.org > > > > > > > wrote: > > > >>> > > > >>> Everything is possible. > > > All I need is longer day. 24 hours are not enough... > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > > > > > >>> solomax...@gmail.com > > > >> > > > >>> wrote: > > > > > > Is it possible update http://www.wicket-library.com/ to have > > > > > > > wicket7 > > > > > > > >> examples as well? > > > > I believe this might be very useful :) > > > > > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea de
Re: Wicket7: MediaComponent and Source classes
Additionally it looks like WebSocketRequestHandler can not be used as AjaxRequestTarget any longer Previously it was possible to use WebSocketRequestHandler to push updated component . On Thu, Jul 2, 2015 at 2:42 PM, Maxim Solodovnik wrote: > Thanks a lot Tobias! > > On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > >> Hi Maxim, >> >> no problem I am going to add the getter this evening. Thank you for your >> suggestions! :-) >> >> Maybe the SNAPSHOT isn't refreshed because of the downtime of the >> buildbot server. However the build was triggered already. >> >> kind regards >> >> Tobias >> >> > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik : >> > >> > Thanks a lot for the changes Tobias, >> > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems >> > doesn't contain it :( >> > >> > And one more question: I would like to be able to modify PageParameters >> > passed to source, maybe it would be possible to add public getter for >> it? >> > >> > Thanks in advance >> > >> > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < >> > tobiassolosche...@googlemail.com> wrote: >> > >> >> Hi Maxim, >> >> >> >> hope the change is like you wanted it to be: >> >> >> >> >> >> >> https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 >> >> >> >> But again: The PackageResourceReference is best practice, because you >> also >> >> can use "readBuffered(false)" of it - with this option the resource is >> >> streamed directly without loading it into memory. For more information >> >> refer to the Javadoc of the method. >> >> >> >> kind regards >> >> >> >> Tobias >> >> >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: >> >>> >> >>> Thanks a lot! >> >>> It was gmail SPAM filter :((( >> >>> will do migration and examine examples >> >>> >> >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < >> mgrigo...@apache.org> >> >>> wrote: >> >>> >> >>> For some reason Tobias' mails are marked as SPAM by GMail... >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < >> solomax...@gmail.com >> > >> wrote: >> >> sorry, most probably missed that email >> > Thanks! >> > >> > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < >> mgrigo...@apache.org> >> > wrote: >> > >> > Tobias already explained that it was an oversight and he is going to >> >> improve it tonight. >> >> >> >> Martin Grigorov >> >> Freelancer. Available for hire! >> >> Wicket Training and Consulting >> >> https://twitter.com/mtgrigorov >> >> >> >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < >> >> >> > solomax...@gmail.com >> >> > wrote: >> >> >> >> Thanks Martin :) >> >>> will look through sources :) >> >>> >> >>> can you please tell me why PackageResourceReference is being used >> in >> >>> MediaComponent and not ResourceReference? Or maybe Tobias can >> answer >> >>> >> >> this >> > >> >> question? >> >>> >> >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < >> >>> >> >> mgrigo...@apache.org >> >> > wrote: >> >>> >> >>> Everything is possible. >> All I need is longer day. 24 hours are not enough... >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < >> >> >>> solomax...@gmail.com >> >> >> >>> wrote: >> >> Is it possible update http://www.wicket-library.com/ to have >> > >> wicket7 >> > >> >> examples as well? >> > I believe this might be very useful :) >> > >> > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < >> > >> an.delb...@gmail.com >> >> >> >>> wrote: >> > >> > Hi, >> >> >> >> in wicket-examples take a look at the project in >> >> org.apache.wicket.examples.media >> >> >> >> Andrea. >> >> >> >> >> >> On 29/06/2015 06:47, Maxim Solodovnik wrote: >> >> >> >> Hello All, >> >>> >> >>> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and >> >>> >> >> found >> > >> >> lots >> >>> >> of >> > >> >> improvements: >> >>> 1) AbstractResource is now supports "content-range" and >> >>> >> >> "accept-range" >> >>> >> which is great! I'll remove my custom code for this :) >> >>> 2) HTML5 Video is supported by wicket itself (was removed from >> >>> wicketstuff) >> >>> which is great :)) >> >>>
Re: Wicket7: MediaComponent and Source classes
Thanks a lot Tobias! On Thu, Jul 2, 2015 at 1:03 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Maxim, > > no problem I am going to add the getter this evening. Thank you for your > suggestions! :-) > > Maybe the SNAPSHOT isn't refreshed because of the downtime of the buildbot > server. However the build was triggered already. > > kind regards > > Tobias > > > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik : > > > > Thanks a lot for the changes Tobias, > > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems > > doesn't contain it :( > > > > And one more question: I would like to be able to modify PageParameters > > passed to source, maybe it would be possible to add public getter for it? > > > > Thanks in advance > > > > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > tobiassolosche...@googlemail.com> wrote: > > > >> Hi Maxim, > >> > >> hope the change is like you wanted it to be: > >> > >> > >> > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > >> > >> But again: The PackageResourceReference is best practice, because you > also > >> can use "readBuffered(false)" of it - with this option the resource is > >> streamed directly without loading it into memory. For more information > >> refer to the Javadoc of the method. > >> > >> kind regards > >> > >> Tobias > >> > >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > >>> > >>> Thanks a lot! > >>> It was gmail SPAM filter :((( > >>> will do migration and examine examples > >>> > >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov > > >>> wrote: > >>> > >>> For some reason Tobias' mails are marked as SPAM by GMail... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > solomax...@gmail.com > > > wrote: > > sorry, most probably missed that email > > Thanks! > > > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > mgrigo...@apache.org> > > wrote: > > > > Tobias already explained that it was an oversight and he is going to > >> improve it tonight. > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > >> > > solomax...@gmail.com > > > wrote: > >> > >> Thanks Martin :) > >>> will look through sources :) > >>> > >>> can you please tell me why PackageResourceReference is being used > in > >>> MediaComponent and not ResourceReference? Or maybe Tobias can > answer > >>> > >> this > > > >> question? > >>> > >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > >>> > >> mgrigo...@apache.org > > > wrote: > >>> > >>> Everything is possible. > All I need is longer day. 24 hours are not enough... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > >>> solomax...@gmail.com > >> > >>> wrote: > > Is it possible update http://www.wicket-library.com/ to have > > > wicket7 > > > >> examples as well? > > I believe this might be very useful :) > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > > an.delb...@gmail.com > >> > >>> wrote: > > > > Hi, > >> > >> in wicket-examples take a look at the project in > >> org.apache.wicket.examples.media > >> > >> Andrea. > >> > >> > >> On 29/06/2015 06:47, Maxim Solodovnik wrote: > >> > >> Hello All, > >>> > >>> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > >>> > >> found > > > >> lots > >>> > of > > > >> improvements: > >>> 1) AbstractResource is now supports "content-range" and > >>> > >> "accept-range" > >>> > which is great! I'll remove my custom code for this :) > >>> 2) HTML5 Video is supported by wicket itself (was removed from > >>> wicketstuff) > >>> which is great :)) > >>> > >>> 3) MediaComponent requires *PackageResourceReference* as > >>> > >> resourceReference > > > >> :(( why it can't be ResourceReference? > >>> > >>> Are there any examples in wicket7 regarding new Video > >>> > >> Component? > > > Thanks in advance! > >>> > >>> > >>> > >> > >> >
Re: Wicket7: MediaComponent and Source classes
Thanks for the clarifications Martin This seems to be caching issue on my side Could you please answer additional question regarding ListView It seems to be impossible in latest snapshot to create ListView("list", new List()) It was working as expected in M6 and previous versions On Thu, Jul 2, 2015 at 1:14 PM, Martin Grigorov wrote: > There is a new build. The snapshots should be updated. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Jul 2, 2015 at 10:03 AM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > > > Hi Maxim, > > > > no problem I am going to add the getter this evening. Thank you for your > > suggestions! :-) > > > > Maybe the SNAPSHOT isn't refreshed because of the downtime of the > buildbot > > server. However the build was triggered already. > > > > kind regards > > > > Tobias > > > > > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik >: > > > > > > Thanks a lot for the changes Tobias, > > > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems > > > doesn't contain it :( > > > > > > And one more question: I would like to be able to modify PageParameters > > > passed to source, maybe it would be possible to add public getter for > it? > > > > > > Thanks in advance > > > > > > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > > tobiassolosche...@googlemail.com> wrote: > > > > > >> Hi Maxim, > > >> > > >> hope the change is like you wanted it to be: > > >> > > >> > > >> > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > >> > > >> But again: The PackageResourceReference is best practice, because you > > also > > >> can use "readBuffered(false)" of it - with this option the resource is > > >> streamed directly without loading it into memory. For more information > > >> refer to the Javadoc of the method. > > >> > > >> kind regards > > >> > > >> Tobias > > >> > > >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > >>> > > >>> Thanks a lot! > > >>> It was gmail SPAM filter :((( > > >>> will do migration and examine examples > > >>> > > >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov < > mgrigo...@apache.org > > > > > >>> wrote: > > >>> > > >>> For some reason Tobias' mails are marked as SPAM by GMail... > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > > solomax...@gmail.com > > > > > wrote: > > > > sorry, most probably missed that email > > > Thanks! > > > > > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > > mgrigo...@apache.org> > > > wrote: > > > > > > Tobias already explained that it was an oversight and he is going > to > > >> improve it tonight. > > >> > > >> Martin Grigorov > > >> Freelancer. Available for hire! > > >> Wicket Training and Consulting > > >> https://twitter.com/mtgrigorov > > >> > > >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > > >> > > > solomax...@gmail.com > > > > > wrote: > > >> > > >> Thanks Martin :) > > >>> will look through sources :) > > >>> > > >>> can you please tell me why PackageResourceReference is being used > > in > > >>> MediaComponent and not ResourceReference? Or maybe Tobias can > > answer > > >>> > > >> this > > > > > >> question? > > >>> > > >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > > >>> > > >> mgrigo...@apache.org > > > > > wrote: > > >>> > > >>> Everything is possible. > > All I need is longer day. 24 hours are not enough... > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > > > >>> solomax...@gmail.com > > >> > > >>> wrote: > > > > Is it possible update http://www.wicket-library.com/ to have > > > > > wicket7 > > > > > >> examples as well? > > > I believe this might be very useful :) > > > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > > > > an.delb...@gmail.com > > >> > > >>> wrote: > > > > > > Hi, > > >> > > >> in wicket-examples take a look at the project in > > >> org.apache.wicket.examples.media > > >> > > >> Andrea. > > >> > > >> > > >> On 29/06/2015 06:47, Maxim Solodovnik wrote: > > >> > > >> Hello All, > > >>> > > >>> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > > >>> > > >> found > > > > > >> lots > >
Re: Wicket7: MediaComponent and Source classes
There is a new build. The snapshots should be updated. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jul 2, 2015 at 10:03 AM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Maxim, > > no problem I am going to add the getter this evening. Thank you for your > suggestions! :-) > > Maybe the SNAPSHOT isn't refreshed because of the downtime of the buildbot > server. However the build was triggered already. > > kind regards > > Tobias > > > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik : > > > > Thanks a lot for the changes Tobias, > > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems > > doesn't contain it :( > > > > And one more question: I would like to be able to modify PageParameters > > passed to source, maybe it would be possible to add public getter for it? > > > > Thanks in advance > > > > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > > tobiassolosche...@googlemail.com> wrote: > > > >> Hi Maxim, > >> > >> hope the change is like you wanted it to be: > >> > >> > >> > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > >> > >> But again: The PackageResourceReference is best practice, because you > also > >> can use "readBuffered(false)" of it - with this option the resource is > >> streamed directly without loading it into memory. For more information > >> refer to the Javadoc of the method. > >> > >> kind regards > >> > >> Tobias > >> > >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > >>> > >>> Thanks a lot! > >>> It was gmail SPAM filter :((( > >>> will do migration and examine examples > >>> > >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov > > >>> wrote: > >>> > >>> For some reason Tobias' mails are marked as SPAM by GMail... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > solomax...@gmail.com > > > wrote: > > sorry, most probably missed that email > > Thanks! > > > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > mgrigo...@apache.org> > > wrote: > > > > Tobias already explained that it was an oversight and he is going to > >> improve it tonight. > >> > >> Martin Grigorov > >> Freelancer. Available for hire! > >> Wicket Training and Consulting > >> https://twitter.com/mtgrigorov > >> > >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > >> > > solomax...@gmail.com > > > wrote: > >> > >> Thanks Martin :) > >>> will look through sources :) > >>> > >>> can you please tell me why PackageResourceReference is being used > in > >>> MediaComponent and not ResourceReference? Or maybe Tobias can > answer > >>> > >> this > > > >> question? > >>> > >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > >>> > >> mgrigo...@apache.org > > > wrote: > >>> > >>> Everything is possible. > All I need is longer day. 24 hours are not enough... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > >>> solomax...@gmail.com > >> > >>> wrote: > > Is it possible update http://www.wicket-library.com/ to have > > > wicket7 > > > >> examples as well? > > I believe this might be very useful :) > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > > an.delb...@gmail.com > >> > >>> wrote: > > > > Hi, > >> > >> in wicket-examples take a look at the project in > >> org.apache.wicket.examples.media > >> > >> Andrea. > >> > >> > >> On 29/06/2015 06:47, Maxim Solodovnik wrote: > >> > >> Hello All, > >>> > >>> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > >>> > >> found > > > >> lots > >>> > of > > > >> improvements: > >>> 1) AbstractResource is now supports "content-range" and > >>> > >> "accept-range" > >>> > which is great! I'll remove my custom code for this :) > >>> 2) HTML5 Video is supported by wicket itself (was removed from > >>> wicketstuff) > >>> which is great :)) > >>> > >>> 3) MediaComponent requires *PackageResourceReference* as > >>> > >> resourceReference > > > >> :(( why it can't be ResourceReference? > >>> > >>> Are there any examples in wicket7 regarding new Video > >>> > >> Component
Re: Wicket7: MediaComponent and Source classes
Hi Maxim, no problem I am going to add the getter this evening. Thank you for your suggestions! :-) Maybe the SNAPSHOT isn't refreshed because of the downtime of the buildbot server. However the build was triggered already. kind regards Tobias > Am 02.07.2015 um 08:45 schrieb Maxim Solodovnik : > > Thanks a lot for the changes Tobias, > Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems > doesn't contain it :( > > And one more question: I would like to be able to modify PageParameters > passed to source, maybe it would be possible to add public getter for it? > > Thanks in advance > > On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > >> Hi Maxim, >> >> hope the change is like you wanted it to be: >> >> >> https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 >> >> But again: The PackageResourceReference is best practice, because you also >> can use "readBuffered(false)" of it - with this option the resource is >> streamed directly without loading it into memory. For more information >> refer to the Javadoc of the method. >> >> kind regards >> >> Tobias >> >>> Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: >>> >>> Thanks a lot! >>> It was gmail SPAM filter :((( >>> will do migration and examine examples >>> >>> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov >>> wrote: >>> >>> For some reason Tobias' mails are marked as SPAM by GMail... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik wrote: sorry, most probably missed that email > Thanks! > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov > wrote: > > Tobias already explained that it was an oversight and he is going to >> improve it tonight. >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < >> > solomax...@gmail.com > wrote: >> >> Thanks Martin :) >>> will look through sources :) >>> >>> can you please tell me why PackageResourceReference is being used in >>> MediaComponent and not ResourceReference? Or maybe Tobias can answer >>> >> this > >> question? >>> >>> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < >>> >> mgrigo...@apache.org > wrote: >>> >>> Everything is possible. All I need is longer day. 24 hours are not enough... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < >>> solomax...@gmail.com >> >>> wrote: Is it possible update http://www.wicket-library.com/ to have > wicket7 > >> examples as well? > I believe this might be very useful :) > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > an.delb...@gmail.com >> >>> wrote: > > Hi, >> >> in wicket-examples take a look at the project in >> org.apache.wicket.examples.media >> >> Andrea. >> >> >> On 29/06/2015 06:47, Maxim Solodovnik wrote: >> >> Hello All, >>> >>> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and >>> >> found > >> lots >>> of > >> improvements: >>> 1) AbstractResource is now supports "content-range" and >>> >> "accept-range" >>> which is great! I'll remove my custom code for this :) >>> 2) HTML5 Video is supported by wicket itself (was removed from >>> wicketstuff) >>> which is great :)) >>> >>> 3) MediaComponent requires *PackageResourceReference* as >>> >> resourceReference > >> :(( why it can't be ResourceReference? >>> >>> Are there any examples in wicket7 regarding new Video >>> >> Component? > Thanks in advance! >>> >>> >>> >> >> - >> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> > -- > WBR > Maxim aka solomax > > >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >>> > > -- > WBR > Maxim aka solomax > > >>> >>> >> >>
Re: Wicket7: MediaComponent and Source classes
Thanks a lot for the changes Tobias, Unfortunately I'm unable to test it due to latest 7.0.0-SNAPSHOT seems doesn't contain it :( And one more question: I would like to be able to modify PageParameters passed to source, maybe it would be possible to add public getter for it? Thanks in advance On Mon, Jun 29, 2015 at 9:41 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Maxim, > > hope the change is like you wanted it to be: > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > But again: The PackageResourceReference is best practice, because you also > can use "readBuffered(false)" of it - with this option the resource is > streamed directly without loading it into memory. For more information > refer to the Javadoc of the method. > > kind regards > > Tobias > > Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > >> Thanks a lot! >> It was gmail SPAM filter :((( >> will do migration and examine examples >> >> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov >> wrote: >> >> For some reason Tobias' mails are marked as SPAM by GMail... >>> >>> Martin Grigorov >>> Freelancer. Available for hire! >>> Wicket Training and Consulting >>> https://twitter.com/mtgrigorov >>> >>> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik >> > >>> wrote: >>> >>> sorry, most probably missed that email Thanks! On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov wrote: Tobias already explained that it was an oversight and he is going to > improve it tonight. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > solomax...@gmail.com >>> wrote: > > Thanks Martin :) >> will look through sources :) >> >> can you please tell me why PackageResourceReference is being used in >> MediaComponent and not ResourceReference? Or maybe Tobias can answer >> > this > question? >> >> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < >> > mgrigo...@apache.org >>> wrote: >> >> Everything is possible. >>> All I need is longer day. 24 hours are not enough... >>> >>> Martin Grigorov >>> Freelancer. Available for hire! >>> Wicket Training and Consulting >>> https://twitter.com/mtgrigorov >>> >>> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < >>> >> solomax...@gmail.com > >> wrote: >>> >>> Is it possible update http://www.wicket-library.com/ to have >>> wicket7 > examples as well? I believe this might be very useful :) On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < >>> an.delb...@gmail.com > >> wrote: Hi, > > in wicket-examples take a look at the project in > org.apache.wicket.examples.media > > Andrea. > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > Hello All, >> >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and >> > found > lots >> >>> of > improvements: >> 1) AbstractResource is now supports "content-range" and >> > "accept-range" >> >>> which is great! I'll remove my custom code for this :) >> 2) HTML5 Video is supported by wicket itself (was removed from >> wicketstuff) >> which is great :)) >> >> 3) MediaComponent requires *PackageResourceReference* as >> > resourceReference > :(( why it can't be ResourceReference? >> >> Are there any examples in wicket7 regarding new Video >> > Component? >>> Thanks in advance! >> >> >> > > - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- WBR Maxim aka solomax >> >> -- >> WBR >> Maxim aka solomax >> >> -- WBR Maxim aka solomax >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- WBR Maxim aka solomax
Re: Wicket7: MediaComponent and Source classes
We already using external storage :) This is why this issue is arise :) Thanks for the fix! I asked my only question on GitHub :) On Tue, Jun 30, 2015 at 1:59 AM, Martin Grigorov wrote: > Hi, > > On Mon, Jun 29, 2015 at 6:41 PM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > > > Hi Maxim, > > > > hope the change is like you wanted it to be: > > > > > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > > > But again: The PackageResourceReference is best practice, because you > also > > can use "readBuffered(false)" of it - with this option the resource is > > streamed directly > > > I wouldn't recommend to use PackageResRef for bigger files which should be > streamed. > PackageResRef loads its resource with the class loader. That means you have > to put the big resource in your .war/.ear. > For bigger files I'd recommend to use external storage, not the application > archive. > > > > without loading it into memory. For more information refer to the Javadoc > > of the method. > > > > kind regards > > > > Tobias > > > > Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > > > Thanks a lot! > >> It was gmail SPAM filter :((( > >> will do migration and examine examples > >> > >> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov > >> wrote: > >> > >> For some reason Tobias' mails are marked as SPAM by GMail... > >>> > >>> Martin Grigorov > >>> Freelancer. Available for hire! > >>> Wicket Training and Consulting > >>> https://twitter.com/mtgrigorov > >>> > >>> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik < > solomax...@gmail.com > >>> > > >>> wrote: > >>> > >>> sorry, most probably missed that email > Thanks! > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov < > mgrigo...@apache.org> > wrote: > > Tobias already explained that it was an oversight and he is going to > > improve it tonight. > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > > > solomax...@gmail.com > >>> > wrote: > > > > Thanks Martin :) > >> will look through sources :) > >> > >> can you please tell me why PackageResourceReference is being used in > >> MediaComponent and not ResourceReference? Or maybe Tobias can answer > >> > > this > > > question? > >> > >> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > >> > > mgrigo...@apache.org > >>> > wrote: > >> > >> Everything is possible. > >>> All I need is longer day. 24 hours are not enough... > >>> > >>> Martin Grigorov > >>> Freelancer. Available for hire! > >>> Wicket Training and Consulting > >>> https://twitter.com/mtgrigorov > >>> > >>> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > >>> > >> solomax...@gmail.com > > > >> wrote: > >>> > >>> Is it possible update http://www.wicket-library.com/ to have > > >>> wicket7 > > > examples as well? > I believe this might be very useful :) > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > >>> an.delb...@gmail.com > > > >> wrote: > > Hi, > > > > in wicket-examples take a look at the project in > > org.apache.wicket.examples.media > > > > Andrea. > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > > Hello All, > >> > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > >> > > found > > > lots > >> > >>> of > > > improvements: > >> 1) AbstractResource is now supports "content-range" and > >> > > "accept-range" > >> > >>> which is great! I'll remove my custom code for this :) > >> 2) HTML5 Video is supported by wicket itself (was removed from > >> wicketstuff) > >> which is great :)) > >> > >> 3) MediaComponent requires *PackageResourceReference* as > >> > > resourceReference > > > :(( why it can't be ResourceReference? > >> > >> Are there any examples in wicket7 regarding new Video > >> > > Component? > >>> > Thanks in advance! > >> > >> > >> > > > > - > > > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > -- > WBR > Maxim aka solomax > > > >> > >> -- > >> WBR > >> Maxim aka solomax > >> > >> > > -- > WBR > Maxim a
Re: Wicket7: MediaComponent and Source classes
Hi, On Mon, Jun 29, 2015 at 6:41 PM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Maxim, > > hope the change is like you wanted it to be: > > > https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 > > But again: The PackageResourceReference is best practice, because you also > can use "readBuffered(false)" of it - with this option the resource is > streamed directly I wouldn't recommend to use PackageResRef for bigger files which should be streamed. PackageResRef loads its resource with the class loader. That means you have to put the big resource in your .war/.ear. For bigger files I'd recommend to use external storage, not the application archive. > without loading it into memory. For more information refer to the Javadoc > of the method. > > kind regards > > Tobias > > Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: > > Thanks a lot! >> It was gmail SPAM filter :((( >> will do migration and examine examples >> >> On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov >> wrote: >> >> For some reason Tobias' mails are marked as SPAM by GMail... >>> >>> Martin Grigorov >>> Freelancer. Available for hire! >>> Wicket Training and Consulting >>> https://twitter.com/mtgrigorov >>> >>> On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik >> > >>> wrote: >>> >>> sorry, most probably missed that email Thanks! On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov wrote: Tobias already explained that it was an oversight and he is going to > improve it tonight. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > solomax...@gmail.com >>> wrote: > > Thanks Martin :) >> will look through sources :) >> >> can you please tell me why PackageResourceReference is being used in >> MediaComponent and not ResourceReference? Or maybe Tobias can answer >> > this > question? >> >> On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < >> > mgrigo...@apache.org >>> wrote: >> >> Everything is possible. >>> All I need is longer day. 24 hours are not enough... >>> >>> Martin Grigorov >>> Freelancer. Available for hire! >>> Wicket Training and Consulting >>> https://twitter.com/mtgrigorov >>> >>> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < >>> >> solomax...@gmail.com > >> wrote: >>> >>> Is it possible update http://www.wicket-library.com/ to have >>> wicket7 > examples as well? I believe this might be very useful :) On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < >>> an.delb...@gmail.com > >> wrote: Hi, > > in wicket-examples take a look at the project in > org.apache.wicket.examples.media > > Andrea. > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > Hello All, >> >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and >> > found > lots >> >>> of > improvements: >> 1) AbstractResource is now supports "content-range" and >> > "accept-range" >> >>> which is great! I'll remove my custom code for this :) >> 2) HTML5 Video is supported by wicket itself (was removed from >> wicketstuff) >> which is great :)) >> >> 3) MediaComponent requires *PackageResourceReference* as >> > resourceReference > :(( why it can't be ResourceReference? >> >> Are there any examples in wicket7 regarding new Video >> > Component? >>> Thanks in advance! >> >> >> > > - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- WBR Maxim aka solomax >> >> -- >> WBR >> Maxim aka solomax >> >> -- WBR Maxim aka solomax >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Wicket7: MediaComponent and Source classes
Hi Maxim, hope the change is like you wanted it to be: https://github.com/apache/wicket/commit/e20bfa738aa64f35b668f05866e0c0b7ca71c1f4 But again: The PackageResourceReference is best practice, because you also can use "readBuffered(false)" of it - with this option the resource is streamed directly without loading it into memory. For more information refer to the Javadoc of the method. kind regards Tobias Am 29.06.15 um 10:22 schrieb Maxim Solodovnik: Thanks a lot! It was gmail SPAM filter :((( will do migration and examine examples On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov wrote: For some reason Tobias' mails are marked as SPAM by GMail... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik wrote: sorry, most probably missed that email Thanks! On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov wrote: Tobias already explained that it was an oversight and he is going to improve it tonight. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < solomax...@gmail.com wrote: Thanks Martin :) will look through sources :) can you please tell me why PackageResourceReference is being used in MediaComponent and not ResourceReference? Or maybe Tobias can answer this question? On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < mgrigo...@apache.org wrote: Everything is possible. All I need is longer day. 24 hours are not enough... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < solomax...@gmail.com wrote: Is it possible update http://www.wicket-library.com/ to have wicket7 examples as well? I believe this might be very useful :) On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < an.delb...@gmail.com wrote: Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of improvements: 1) AbstractResource is now supports "content-range" and "accept-range" which is great! I'll remove my custom code for this :) 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) which is great :)) 3) MediaComponent requires *PackageResourceReference* as resourceReference :(( why it can't be ResourceReference? Are there any examples in wicket7 regarding new Video Component? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- WBR Maxim aka solomax -- WBR Maxim aka solomax -- WBR Maxim aka solomax - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
Juergen Donnerstag owns it. He gave me the credentials several years ago. So far it is as simple as deploy the new version and restart Tomcat 6.x. I've tried before to use Tomcat 7.x but it seems there are some (cron?!) scripts by the hosting provider which start Tomcat 6.x no matter what. I'll have to debug these scripts and see whether there is Tomcat 8.x installation because Wicket 7.x needs Servlet 3.0. So, it will take a while... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:47 AM, andrea del bene wrote: > > I could do it if I knew what to do. Who is maintaining the examples site > (in addition to you Martin)? > > Everything is possible. >> All I need is longer day. 24 hours are not enough... >> >> Martin Grigorov >> Freelancer. Available for hire! >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik >> wrote: >> >> Is it possible update http://www.wicket-library.com/ to have wicket7 >>> examples as well? >>> I believe this might be very useful :) >>> >>> On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene >>> wrote: >>> >>> Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, > > Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots > of >>> improvements: > 1) AbstractResource is now supports "content-range" and "accept-range" > which is great! I'll remove my custom code for this :) > 2) HTML5 Video is supported by wicket itself (was removed from > wicketstuff) > which is great :)) > > 3) MediaComponent requires *PackageResourceReference* as > resourceReference >>> :(( why it can't be ResourceReference? > > Are there any examples in wicket7 regarding new Video Component? > > Thanks in advance! > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org >>> -- >>> WBR >>> Maxim aka solomax >>> >>> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Wicket7: MediaComponent and Source classes
I could do it if I knew what to do. Who is maintaining the examples site (in addition to you Martin)? Everything is possible. All I need is longer day. 24 hours are not enough... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik wrote: Is it possible update http://www.wicket-library.com/ to have wicket7 examples as well? I believe this might be very useful :) On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene wrote: Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of improvements: 1) AbstractResource is now supports "content-range" and "accept-range" which is great! I'll remove my custom code for this :) 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) which is great :)) 3) MediaComponent requires *PackageResourceReference* as resourceReference :(( why it can't be ResourceReference? Are there any examples in wicket7 regarding new Video Component? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- WBR Maxim aka solomax - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
Thanks a lot! It was gmail SPAM filter :((( will do migration and examine examples On Mon, Jun 29, 2015 at 2:18 PM, Martin Grigorov wrote: > For some reason Tobias' mails are marked as SPAM by GMail... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik > wrote: > > > sorry, most probably missed that email > > Thanks! > > > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov > > wrote: > > > > > Tobias already explained that it was an oversight and he is going to > > > improve it tonight. > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik < > solomax...@gmail.com > > > > > > wrote: > > > > > > > Thanks Martin :) > > > > will look through sources :) > > > > > > > > can you please tell me why PackageResourceReference is being used in > > > > MediaComponent and not ResourceReference? Or maybe Tobias can answer > > this > > > > question? > > > > > > > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov < > mgrigo...@apache.org > > > > > > > wrote: > > > > > > > > > Everything is possible. > > > > > All I need is longer day. 24 hours are not enough... > > > > > > > > > > Martin Grigorov > > > > > Freelancer. Available for hire! > > > > > Wicket Training and Consulting > > > > > https://twitter.com/mtgrigorov > > > > > > > > > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > > solomax...@gmail.com > > > > > > > > > > wrote: > > > > > > > > > > > Is it possible update http://www.wicket-library.com/ to have > > wicket7 > > > > > > examples as well? > > > > > > I believe this might be very useful :) > > > > > > > > > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > > an.delb...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > in wicket-examples take a look at the project in > > > > > > > org.apache.wicket.examples.media > > > > > > > > > > > > > > Andrea. > > > > > > > > > > > > > > > > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > > > > > > > > > > > >> Hello All, > > > > > > >> > > > > > > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > > found > > > > lots > > > > > > of > > > > > > >> improvements: > > > > > > >> 1) AbstractResource is now supports "content-range" and > > > > "accept-range" > > > > > > >> which is great! I'll remove my custom code for this :) > > > > > > >> 2) HTML5 Video is supported by wicket itself (was removed from > > > > > > >> wicketstuff) > > > > > > >> which is great :)) > > > > > > >> > > > > > > >> 3) MediaComponent requires *PackageResourceReference* as > > > > > > resourceReference > > > > > > >> :(( why it can't be ResourceReference? > > > > > > >> > > > > > > >> Are there any examples in wicket7 regarding new Video > Component? > > > > > > >> > > > > > > >> Thanks in advance! > > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > WBR > > > > > > Maxim aka solomax > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > WBR > > > > Maxim aka solomax > > > > > > > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > -- WBR Maxim aka solomax
Re: Wicket7: MediaComponent and Source classes
For some reason Tobias' mails are marked as SPAM by GMail... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:15 AM, Maxim Solodovnik wrote: > sorry, most probably missed that email > Thanks! > > On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov > wrote: > > > Tobias already explained that it was an oversight and he is going to > > improve it tonight. > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik > > > wrote: > > > > > Thanks Martin :) > > > will look through sources :) > > > > > > can you please tell me why PackageResourceReference is being used in > > > MediaComponent and not ResourceReference? Or maybe Tobias can answer > this > > > question? > > > > > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov > > > > wrote: > > > > > > > Everything is possible. > > > > All I need is longer day. 24 hours are not enough... > > > > > > > > Martin Grigorov > > > > Freelancer. Available for hire! > > > > Wicket Training and Consulting > > > > https://twitter.com/mtgrigorov > > > > > > > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > > solomax...@gmail.com > > > > > > > > wrote: > > > > > > > > > Is it possible update http://www.wicket-library.com/ to have > wicket7 > > > > > examples as well? > > > > > I believe this might be very useful :) > > > > > > > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > > an.delb...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > in wicket-examples take a look at the project in > > > > > > org.apache.wicket.examples.media > > > > > > > > > > > > Andrea. > > > > > > > > > > > > > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > > > > > > > > > >> Hello All, > > > > > >> > > > > > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and > found > > > lots > > > > > of > > > > > >> improvements: > > > > > >> 1) AbstractResource is now supports "content-range" and > > > "accept-range" > > > > > >> which is great! I'll remove my custom code for this :) > > > > > >> 2) HTML5 Video is supported by wicket itself (was removed from > > > > > >> wicketstuff) > > > > > >> which is great :)) > > > > > >> > > > > > >> 3) MediaComponent requires *PackageResourceReference* as > > > > > resourceReference > > > > > >> :(( why it can't be ResourceReference? > > > > > >> > > > > > >> Are there any examples in wicket7 regarding new Video Component? > > > > > >> > > > > > >> Thanks in advance! > > > > > >> > > > > > >> > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > WBR > > > > > Maxim aka solomax > > > > > > > > > > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > > > -- > WBR > Maxim aka solomax >
Re: Wicket7: MediaComponent and Source classes
sorry, most probably missed that email Thanks! On Mon, Jun 29, 2015 at 2:14 PM, Martin Grigorov wrote: > Tobias already explained that it was an oversight and he is going to > improve it tonight. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik > wrote: > > > Thanks Martin :) > > will look through sources :) > > > > can you please tell me why PackageResourceReference is being used in > > MediaComponent and not ResourceReference? Or maybe Tobias can answer this > > question? > > > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov > > wrote: > > > > > Everything is possible. > > > All I need is longer day. 24 hours are not enough... > > > > > > Martin Grigorov > > > Freelancer. Available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik < > solomax...@gmail.com > > > > > > wrote: > > > > > > > Is it possible update http://www.wicket-library.com/ to have wicket7 > > > > examples as well? > > > > I believe this might be very useful :) > > > > > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene < > an.delb...@gmail.com > > > > > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > in wicket-examples take a look at the project in > > > > > org.apache.wicket.examples.media > > > > > > > > > > Andrea. > > > > > > > > > > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > > > > > > > >> Hello All, > > > > >> > > > > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found > > lots > > > > of > > > > >> improvements: > > > > >> 1) AbstractResource is now supports "content-range" and > > "accept-range" > > > > >> which is great! I'll remove my custom code for this :) > > > > >> 2) HTML5 Video is supported by wicket itself (was removed from > > > > >> wicketstuff) > > > > >> which is great :)) > > > > >> > > > > >> 3) MediaComponent requires *PackageResourceReference* as > > > > resourceReference > > > > >> :(( why it can't be ResourceReference? > > > > >> > > > > >> Are there any examples in wicket7 regarding new Video Component? > > > > >> > > > > >> Thanks in advance! > > > > >> > > > > >> > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > > > > > > > > > > -- > > > > WBR > > > > Maxim aka solomax > > > > > > > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > -- WBR Maxim aka solomax
Re: Wicket7: MediaComponent and Source classes
Tobias already explained that it was an oversight and he is going to improve it tonight. Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 11:10 AM, Maxim Solodovnik wrote: > Thanks Martin :) > will look through sources :) > > can you please tell me why PackageResourceReference is being used in > MediaComponent and not ResourceReference? Or maybe Tobias can answer this > question? > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov > wrote: > > > Everything is possible. > > All I need is longer day. 24 hours are not enough... > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik > > > wrote: > > > > > Is it possible update http://www.wicket-library.com/ to have wicket7 > > > examples as well? > > > I believe this might be very useful :) > > > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene > > > > wrote: > > > > > > > Hi, > > > > > > > > in wicket-examples take a look at the project in > > > > org.apache.wicket.examples.media > > > > > > > > Andrea. > > > > > > > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > > > > > >> Hello All, > > > >> > > > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found > lots > > > of > > > >> improvements: > > > >> 1) AbstractResource is now supports "content-range" and > "accept-range" > > > >> which is great! I'll remove my custom code for this :) > > > >> 2) HTML5 Video is supported by wicket itself (was removed from > > > >> wicketstuff) > > > >> which is great :)) > > > >> > > > >> 3) MediaComponent requires *PackageResourceReference* as > > > resourceReference > > > >> :(( why it can't be ResourceReference? > > > >> > > > >> Are there any examples in wicket7 regarding new Video Component? > > > >> > > > >> Thanks in advance! > > > >> > > > >> > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > > > -- > WBR > Maxim aka solomax >
Re: Wicket7: MediaComponent and Source classes
Hi, I answered already: http://apache-wicket.1842946.n4.nabble.com/Wicket7-MediaComponent-and-Source-classes-tp4671386p4671387.html kind regards Tobias P.S.: Maybe it went into the SPAM-Filter. 2015-06-29 10:10 GMT+02:00 Maxim Solodovnik : > Thanks Martin :) > will look through sources :) > > can you please tell me why PackageResourceReference is being used in > MediaComponent and not ResourceReference? Or maybe Tobias can answer this > question? > > On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov > wrote: > > > Everything is possible. > > All I need is longer day. 24 hours are not enough... > > > > Martin Grigorov > > Freelancer. Available for hire! > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik > > > wrote: > > > > > Is it possible update http://www.wicket-library.com/ to have wicket7 > > > examples as well? > > > I believe this might be very useful :) > > > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene > > > > wrote: > > > > > > > Hi, > > > > > > > > in wicket-examples take a look at the project in > > > > org.apache.wicket.examples.media > > > > > > > > Andrea. > > > > > > > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > > > > > >> Hello All, > > > >> > > > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found > lots > > > of > > > >> improvements: > > > >> 1) AbstractResource is now supports "content-range" and > "accept-range" > > > >> which is great! I'll remove my custom code for this :) > > > >> 2) HTML5 Video is supported by wicket itself (was removed from > > > >> wicketstuff) > > > >> which is great :)) > > > >> > > > >> 3) MediaComponent requires *PackageResourceReference* as > > > resourceReference > > > >> :(( why it can't be ResourceReference? > > > >> > > > >> Are there any examples in wicket7 regarding new Video Component? > > > >> > > > >> Thanks in advance! > > > >> > > > >> > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > > > -- > WBR > Maxim aka solomax >
Re: Wicket7: MediaComponent and Source classes
Thanks Martin :) will look through sources :) can you please tell me why PackageResourceReference is being used in MediaComponent and not ResourceReference? Or maybe Tobias can answer this question? On Mon, Jun 29, 2015 at 2:00 PM, Martin Grigorov wrote: > Everything is possible. > All I need is longer day. 24 hours are not enough... > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik > wrote: > > > Is it possible update http://www.wicket-library.com/ to have wicket7 > > examples as well? > > I believe this might be very useful :) > > > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene > > wrote: > > > > > Hi, > > > > > > in wicket-examples take a look at the project in > > > org.apache.wicket.examples.media > > > > > > Andrea. > > > > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > > > >> Hello All, > > >> > > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots > > of > > >> improvements: > > >> 1) AbstractResource is now supports "content-range" and "accept-range" > > >> which is great! I'll remove my custom code for this :) > > >> 2) HTML5 Video is supported by wicket itself (was removed from > > >> wicketstuff) > > >> which is great :)) > > >> > > >> 3) MediaComponent requires *PackageResourceReference* as > > resourceReference > > >> :(( why it can't be ResourceReference? > > >> > > >> Are there any examples in wicket7 regarding new Video Component? > > >> > > >> Thanks in advance! > > >> > > >> > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > -- WBR Maxim aka solomax
Re: Wicket7: MediaComponent and Source classes
Everything is possible. All I need is longer day. 24 hours are not enough... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik wrote: > Is it possible update http://www.wicket-library.com/ to have wicket7 > examples as well? > I believe this might be very useful :) > > On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene > wrote: > > > Hi, > > > > in wicket-examples take a look at the project in > > org.apache.wicket.examples.media > > > > Andrea. > > > > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > > > >> Hello All, > >> > >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots > of > >> improvements: > >> 1) AbstractResource is now supports "content-range" and "accept-range" > >> which is great! I'll remove my custom code for this :) > >> 2) HTML5 Video is supported by wicket itself (was removed from > >> wicketstuff) > >> which is great :)) > >> > >> 3) MediaComponent requires *PackageResourceReference* as > resourceReference > >> :(( why it can't be ResourceReference? > >> > >> Are there any examples in wicket7 regarding new Video Component? > >> > >> Thanks in advance! > >> > >> > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > -- > WBR > Maxim aka solomax >
Re: Wicket7: MediaComponent and Source classes
Is it possible update http://www.wicket-library.com/ to have wicket7 examples as well? I believe this might be very useful :) On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene wrote: > Hi, > > in wicket-examples take a look at the project in > org.apache.wicket.examples.media > > Andrea. > > > On 29/06/2015 06:47, Maxim Solodovnik wrote: > >> Hello All, >> >> Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of >> improvements: >> 1) AbstractResource is now supports "content-range" and "accept-range" >> which is great! I'll remove my custom code for this :) >> 2) HTML5 Video is supported by wicket itself (was removed from >> wicketstuff) >> which is great :)) >> >> 3) MediaComponent requires *PackageResourceReference* as resourceReference >> :(( why it can't be ResourceReference? >> >> Are there any examples in wicket7 regarding new Video Component? >> >> Thanks in advance! >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- WBR Maxim aka solomax
Re: Wicket7: MediaComponent and Source classes
Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of improvements: 1) AbstractResource is now supports "content-range" and "accept-range" which is great! I'll remove my custom code for this :) 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) which is great :)) 3) MediaComponent requires *PackageResourceReference* as resourceReference :(( why it can't be ResourceReference? Are there any examples in wicket7 regarding new Video Component? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
Hi Maxim, there are some examples in the wicket-examples project, which will be released on http://www.wicket-library.com when wicket 7 reaches the final state. You can have a look at the examples on github for now: https://github.com/apache/wicket/tree/master/wicket-examples/src/main/java/org/apache/wicket/examples/media To answer your question about the requirement of PackageResourceReference: Good hint - the functionality is implemented in AbstractResource which is used by the different resource types in the PackageResourceReference. We can use ResourceReference as class member and not PackageResourceReference, because it is only used for URL generation and "urlFor" of the RequestCycle accepts ResourceReferences. Sorry for this unwanted limitation at the current Milestone. I am going to change it this evening. One thing to mention: If you write your own ResourceReference or use some other ResourceReference's you have to implement the Content-Range support by your own. See: https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/resource/PackageResource.java#L332 For the chunk-wise writing of data you can use PartWriterCallback: https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/resource/PartWriterCallback.java kind regards Tobias 2015-06-29 6:47 GMT+02:00 Maxim Solodovnik : > Hello All, > > Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of > improvements: > 1) AbstractResource is now supports "content-range" and "accept-range" > which is great! I'll remove my custom code for this :) > 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) > which is great :)) > > 3) MediaComponent requires *PackageResourceReference* as resourceReference > :(( why it can't be ResourceReference? > > Are there any examples in wicket7 regarding new Video Component? > > Thanks in advance! > > -- > WBR > Maxim aka solomax >
Wicket7: MediaComponent and Source classes
Hello All, Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of improvements: 1) AbstractResource is now supports "content-range" and "accept-range" which is great! I'll remove my custom code for this :) 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) which is great :)) 3) MediaComponent requires *PackageResourceReference* as resourceReference :(( why it can't be ResourceReference? Are there any examples in wicket7 regarding new Video Component? Thanks in advance! -- WBR Maxim aka solomax