You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ryan Dearing (JIRA)" <ji...@apache.org> on 2008/11/11 18:41:44 UTC
[jira] Created: (WICKET-1929)
PagingNavigator.newPagingNavigationIncrementLink and
PagingNavigator.newPagingNavigationLink should return AbstractLink
PagingNavigator.newPagingNavigationIncrementLink and PagingNavigator.newPagingNavigationLink should return AbstractLink
-------------------------------------------------------------------------------------------------------------------------
Key: WICKET-1929
URL: https://issues.apache.org/jira/browse/WICKET-1929
Project: Wicket
Issue Type: Improvement
Affects Versions: 1.3.5
Reporter: Ryan Dearing
Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1929)
PagingNavigator.newPagingNavigationIncrementLink and
PagingNavigator.newPagingNavigationLink should return AbstractLink
Posted by "Ryan Dearing (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Dearing updated WICKET-1929:
---------------------------------
Description:
Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
This was discussed back in Jan 08 ( http://markmail.org/message/dfgnis2rc7ysjlhj ), but I could not find a JIRA issue for it.
For now using Behaviors may work and avoids duplicating a lot of the code.
was:
Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
This was discussed back in Jan 08 (http://markmail.org/message/dfgnis2rc7ysjlhj), but I could not find a JIRA issue for it.
For now using Behaviors may work and avoids duplicating a lot of the code.
> PagingNavigator.newPagingNavigationIncrementLink and PagingNavigator.newPagingNavigationLink should return AbstractLink
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1929
> URL: https://issues.apache.org/jira/browse/WICKET-1929
> Project: Wicket
> Issue Type: Improvement
> Affects Versions: 1.3.0-final, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4-M1, 1.4-M2, 1.4-M3
> Reporter: Ryan Dearing
>
> Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
> This was discussed back in Jan 08 ( http://markmail.org/message/dfgnis2rc7ysjlhj ), but I could not find a JIRA issue for it.
> For now using Behaviors may work and avoids duplicating a lot of the code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1929)
PagingNavigator.newPagingNavigationIncrementLink and
PagingNavigator.newPagingNavigationLink should return AbstractLink
Posted by "Ryan Dearing (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Dearing updated WICKET-1929:
---------------------------------
Description:
Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
This was discussed back in Jan 08 (http://markmail.org/message/dfgnis2rc7ysjlhj), but I could not find a JIRA issue for it.
For now using Behaviors may work and avoids duplicating a lot of the code.
was:Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
Affects Version/s: 1.3.0-final
1.3.1
1.3.2
1.3.3
1.3.4
1.4-M1
1.4-M2
1.4-M3
> PagingNavigator.newPagingNavigationIncrementLink and PagingNavigator.newPagingNavigationLink should return AbstractLink
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1929
> URL: https://issues.apache.org/jira/browse/WICKET-1929
> Project: Wicket
> Issue Type: Improvement
> Affects Versions: 1.3.0-final, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4-M1, 1.4-M2, 1.4-M3
> Reporter: Ryan Dearing
>
> Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
> This was discussed back in Jan 08 (http://markmail.org/message/dfgnis2rc7ysjlhj), but I could not find a JIRA issue for it.
> For now using Behaviors may work and avoids duplicating a lot of the code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1929)
PagingNavigator.newPagingNavigationIncrementLink and
PagingNavigator.newPagingNavigationLink should return AbstractLink
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-1929.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC2
Assignee: Igor Vaynberg
1.4rc2 only due to api break
> PagingNavigator.newPagingNavigationIncrementLink and PagingNavigator.newPagingNavigationLink should return AbstractLink
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1929
> URL: https://issues.apache.org/jira/browse/WICKET-1929
> Project: Wicket
> Issue Type: Improvement
> Affects Versions: 1.3.0-final, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4-M1, 1.4-M2, 1.4-M3
> Reporter: Ryan Dearing
> Assignee: Igor Vaynberg
> Fix For: 1.4-RC2
>
>
> Currently newPagingNavigationLink and newPagingNavigationIncrementLink in PagingNavigator return Link objects. It would be nice if they returned AbstractLink objects to allow more flexibility. This would make using SubmitLink and custom Link components with PagingNavigator much easier.
> This was discussed back in Jan 08 ( http://markmail.org/message/dfgnis2rc7ysjlhj ), but I could not find a JIRA issue for it.
> For now using Behaviors may work and avoids duplicating a lot of the code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.