Hi, You can refactor fragments into panel (and should do this, it is easy). I use fragments only if i want to hide components to the outside or reduce the count of files i have to open to solve something.. this happens only if i build some kind of prototype. If you have nothing to "hide" just use panels instead.
If you want to avoid switching, you can make them invisible.. but it depends on your usecase.. Michael:) Am 21.01.2015 um 12:10 schrieb ChambreNoire: > Hello, > > I'm going over some old code and I have noticed that some devs are using > fragments to slice up views. For instance, one Panel only has a single > 'content' div and then the 3 different views are displayed by switching > between 3 Fragments with replaceWith(). This seems to me to break the 'avoid > changing the component hierarchy' best practice. My understanding was that > Fragments were mostly of use in ListView scenarios. > > Any thoughts on this and appropriate Fragment use in general? > > Thanks, > > CN > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/When-should-one-use-fragments-tp4669062.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
