Hi, I will be adding your dashboard to one of my projects - this is a matter of weeks (customer is really, really excited ;)). I have some suggestions, I would divide the project into seperate modules:
- wicket-dashboard-core: module with dashboard itself, simply juest the component and needed interfaces (jar as an output) - wicket-dashboard-widgets: module were some standard widgets would be implemented (jar as an output) - wicket-dashboard-demo: module with demo useage (war as an output) This way to use dashboard one must simply add wicket-dashboard-core as dependency. He can now develop his own widgets or use standard widgets. To use standard widgets, he must also add wicket-dashboard-widgets as dependency to his project. What do you think about it? Paul Szulc On Mon, Oct 1, 2012 at 10:29 AM, Decebal Suiu <decebal.s...@asf.ro> wrote: > Hi > > Thanks Paul for the nice words. wicket-dashboard code is used in production > in NextReports server (see > > http://apache-wicket.1842946.n4.nabble.com/How-to-create-a-dashboard-with-draggable-widgets-tp4652210p4652218.html > ) > but with some additional features (multiple dashboards, detached widgets, > ...). > > If you have any questions, ideas or suggestions, please do not hesitate to > contact me. > > Best regards, > Decebal > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Announce-wicket-dashboard-tp4652308p4652565.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
