[jira] Commented: (WICKET-237) Constructor change, Component#add

["Teerapong Suksuwan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479227 ] 

Teerapong Suksuwan commented on WICKET-237:
-------------------------------------------

If component's parent cannot be switched. Then, how to implement this requirement:
        I would like to build web application that look like Eclipse IDE. It divide windows into multiple work region. Each region is a tabs of views. Each view can be dragged from one tabs to another. That's mean this view instance will be moved from 1 parent to another parent without reconstruction.

Sorry for weak English skill, wish you all could understand.

> Constructor change, Component#add
> ---------------------------------
>
>                 Key: WICKET-237
>                 URL: https://issues.apache.org/jira/browse/WICKET-237
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 2.0
>            Reporter: Flavius Burca
>         Assigned To: Johan Compagner
>            Priority: Blocker
>
> By removing the Component#add function, the component-based architecture of Wicket is compromised. 
> A component-based architecture relies on component reuse and with this Constructor change you cannot have reusability of components.  
> - How could you create a dynamic component hierarchy without a Component#add method ?
> - How could you allow later binding of components without a Component#add method ?
> - What if you want to reuse a previously created component ?
> - What if you want to create the child component before the parent component and link them at a later time ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.