You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Dilger (JIRA)" <ji...@apache.org> on 2011/09/03 18:04:09 UTC
[jira] [Created] (WICKET-4024) Provide a Convenience API for usage
of Ajax Channels
Provide a Convenience API for usage of Ajax Channels
----------------------------------------------------
Key: WICKET-4024
URL: https://issues.apache.org/jira/browse/WICKET-4024
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 1.5-RC7
Reporter: Martin Dilger
The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
Javadoc, so more people may find this feature.
WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4024) Provide a Convenience API for
usage of Ajax Channels
Posted by "Martin Dilger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096696#comment-13096696 ]
Martin Dilger commented on WICKET-4024:
---------------------------------------
Maybe this should be seen together with WICKET-4023, that I just opened before this one.
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4024) Provide a Convenience API for usage
of Ajax Channels
Posted by "Martin Dilger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Dilger updated WICKET-4024:
----------------------------------
Attachment: 0001-Wicket-4024-Provide-a-convenience-API-for-AjaxChanne.patch
correct patch
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Fix For: 1.6.0
>
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch, 0001-Wicket-4024-Provide-a-convenience-API-for-AjaxChanne.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4024) Provide a Convenience API for
usage of Ajax Channels
Posted by "Martin Dilger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098006#comment-13098006 ]
Martin Dilger commented on WICKET-4024:
---------------------------------------
oh no! you are right, this is the wrong patch, sorry...
I´ll add the correct patch this evening, its on my other laptop.
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Fix For: 1.6.0
>
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4024) Provide a Convenience API for usage
of Ajax Channels
Posted by "Martin Dilger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Dilger updated WICKET-4024:
----------------------------------
Attachment: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4024) Provide a Convenience API for usage
of Ajax Channels
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4024.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.6.0)
1.5.1
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Assignee: Martin Grigorov
> Fix For: 1.5.1
>
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch, 0001-Wicket-4024-Provide-a-convenience-API-for-AjaxChanne.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4024) Provide a Convenience API for
usage of Ajax Channels
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097969#comment-13097969 ]
Martin Grigorov commented on WICKET-4024:
-----------------------------------------
You attached the same patch for both tickets. From the description in this ticket I expect another patch here.
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (WICKET-4024) Provide a Convenience API for usage
of Ajax Channels
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reassigned WICKET-4024:
---------------------------------------
Assignee: Martin Grigorov
I see how this can be introduced in 1.5.x
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Assignee: Martin Grigorov
> Fix For: 1.6.0
>
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch, 0001-Wicket-4024-Provide-a-convenience-API-for-AjaxChanne.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4024) Provide a Convenience API for
usage of Ajax Channels
Posted by "Martin Dilger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099034#comment-13099034 ]
Martin Dilger commented on WICKET-4024:
---------------------------------------
Great, thanks!
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Assignee: Martin Grigorov
> Fix For: 1.5.1
>
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch, 0001-Wicket-4024-Provide-a-convenience-API-for-AjaxChanne.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4024) Provide a Convenience API for usage
of Ajax Channels
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-4024:
------------------------------------
Fix Version/s: 1.6.0
Changing APIs cannot be done in 1.5.x anymore.
I don't like to use Object. It will be better to have AjaxChannel(name, type) or something similar.
> Provide a Convenience API for usage of Ajax Channels
> ----------------------------------------------------
>
> Key: WICKET-4024
> URL: https://issues.apache.org/jira/browse/WICKET-4024
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Martin Dilger
> Fix For: 1.6.0
>
> Attachments: 0001-WICKET-4023-Allow-Ajax-Link-to-assign-its-Ajax-Chann.patch
>
>
> The Usage of Wicket Ajax Channels is currently rarely documented and pretty low-level.
> You have to build the Name of the Channel with a certain Format (name|d for DropChannels, name|s for Stackable Channels).
> I don't know why this is so, but this feature is pretty cool, and I think we should provide a little convenience api for the usage of Channels.
> I attached a patch that shows the idea - its pretty simple, lets just not use a String but an Objects that encapsulates the behavior with a little
> Javadoc, so more people may find this feature.
> WIth the Patch, all works as before, but one could provide an AjaxChannel for its Behavior and must not fiddle with Strings.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira