Hi Maybe it's time to say what I think about this feature.
I read with interest all posts that talk about component queuing. I don't know if the name is correct and I don't care about this aspect. The problem is that are some application types (for example SaaS - software as a service) where the logic for each instance is the same but the layout is not. In fact I have the same application but with multiple layouts and for this reason I must coding to change the hierarchy. My personal experience with this kind of problem is related to an ecommerce platform (based of wicket). My first approach for the home page (by example) was to split the page in small panels that are self explainable: HeaderPanel, ContentPanel, FooterPanel. In HeaderPanel I put some components: search, login, logout, menu, ... After I finished my application two friends of mine want to use my platform. In that moment I realized that the splitting process of home page give me a nice and clean separation of concerts, but it is artificially. I ended to move all components from *Panel in a big page because I can't move the position of search box in my page without touching my java code. I learned a lesson: you must using panels only if you want to reuse that code (as a component) in many parts of application. I must admit that many wicket developers work on applications that does't require a such scenario. In a non SaaS (I don't find a term now) applications if the client wants the search box on the right sidebar it's not a big deal for me to move that component in my java code. For that developers that have one application on many instances, each instance with a different layout, it's a big deal. I see some people on this forum that try to achieve this non trivial functionality, I see that Igor try to find a solution but encounters some issues. Maybe the misfortune is that the core developers are not involved in SaaS applications :) In the end, for me, the missing component queueing is not a stopper, it's not a must have but it's a nice to have feature. It's enough an incomplete (limited) implementation (but clean) than nothing. That's just my two cents. Best regards, Decebal -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Queueing-components-tp4549759p4663131.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
