Status of visural-wicket - update
Richard Nichols
It is past time that I should provide some communication re: the status of the visural-wicket project.
Q. Is the project abandoned?
A. No, but I have not had time to work on it in the past 6+ months.
Q. Will there be a version coming for Wicket 6?
A. Possibly, but I can't make any promises right now. Thus if you really need it, I'd recommend to looking elsewhere (i.e. develop your own, fork it, or choose a different component library).
Q. Should the project be merged/folded into wicket-stuff or [insert other wicket component library]?
A. If anyone wants to fork the code and continue working on it elsewhere, I would not be upset. Please just change the name of the project to avoid confusion.
The explanation for this situation is that I don't work with Wicket on a daily basis anymore. I changed primary jobs/contracts this year and am no longer working on paid Wicket work, and in addition my "out of hours" projects have all been using different technology (e.g. Javascript/REST).
That said, I have a couple of possible projects coming up that may be implemented in Wicket, and if that was to occur I would most likely resume work on visural-wicket.
I am sorry for not providing communication sooner both in terms of support and with regards to roadmap. It's not that I don't care, but more that I have been unsure on whether I would be returning to Wicket soon, and therefore indecisive as to whether to continue trying to develop this project in the interim despite the fact I no longer am actively using Wicket.
However I think it would be a mistake to continue trying to anticipate what features to add to the project when I am no longer scratching any personal itch in doing so and can not guarantee when (if at all) I return to actively working with Wicket.
If anyone has any further questions / comments, please go ahead and let me know.
cheers,
Richard.