On Mon, Aug 3, 2015 at 11:34 AM, Martin Grigorov <[email protected]> wrote: > AFAIR several people said that we don't want to make WicketStuff a > graveyard of such code thus I put it in a separate project.
Well, the code is done, complete, finished. I don't see a future where the tree/treetable will become a javascript client side component, however the code itself has value for existing projects that already use it. The component itself doesn't have many bugs if any, so I don't see a problem with it staying in wicketstuff. Swarm/Wasp have the same status. Wicket proper has some unmaintained modules and/or components as well: Wicket Velocity comes to mind, the Rating component, YUI DatePicker? > The code is deprecated because it won't be maintained too. I'm actually thinking about removing the deprecation warnings. It is my intention to keep the code compiling and working, but not improving it (we have better components for that). > It is available just to make migration to Wicket 7 easier. And to not throw away valuable code for our users. At least at my day job we use these components in 2 places, where there's no business case to rewrite those pages at this moment. Given the nature of these tables and custom column implementations, the investment would be prohibitive. Of course we can move the code internally, but I guess we are not the only company using these components. Martijn
