I'm also not actively working with Wicket anymore (a shame), but we made extensive use of the `ISortableDataProvider` and `DataTable`. It should not be to hard to create a `BeanSortableDataProvider<T>` and a class that generated the `AbstractColumn<T, S>` from the beans?
On Wed, Apr 16, 2025 at 12:56 PM andrew goh <gohand...@yahoo.com.invalid> wrote: > I think some of these stuff may be good to be added in > https://wicketstuff.org/ > > But for now this is very rough and 'only about works'. > > Back in the 'early' days of GUI development, there has been lots of > re-usable GUI data components, e.g. the old Powerbuilder data windows > > > https://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc00044_0250/html/dwprgnet/CHDHFGCJ.htm > > For some reasons, that art is 'lost' and it became 'scripting in > templates' jsp/etc, yup there is MVC and all, but that 'scripting in > templates' seemed to become an 'accepted norm' for web development. It > starts to get on my nerves when I realised that I'm copying lots of > (HTML+script) codes between forms, the HTML is verbose often much more > so than the java codes and error prone, missing tags / closures, they > are very state dependent (e.g. after you 'display' an error, forget to > 'hide' it etc) upon submit etc. > Hence, I looked elsewhere for a solution and I stumbled into Apache Wicket. > > Apache Wicket and its components based design alleviates a lot of that. > And I think it'd be good to explore further e.g. like what I'm trying > out currently give the forms or pages a Java Bean and the components > handle it fully. It can make database web apps a lot less verbose to write > > Cheers, > Andrew > > On 16/04/2025 18:26, Jonathan Locke wrote: > > Hi Andrew, > > > > Interesting idea. I’ve been mostly away from Wicket for about 10 years > as a committer, but I’m drawn back to the project again by some things I’d > like to see done that would provide more automation like this and also > improve support for CSS and JavaScript and more concise syntax for fluency > in building UIs (I know this is one of Martian’s wishlist items). I also > have some curiosity about whether Wicket could have core features that > might make integrations with client-side frameworks like React and Angular > easy. The pipe dream there is that you might build a Wicket app where there > are some richer client side components you’d like to work with in a small > portion of the site. > > > > I have a client right now that I’m working with on a system for viewing > and editing models automatically, kind of like your bean table project, but > for individual beans. > > > > I think you’re thinking along the right lines in general. My client and > I would ideally like to find one or two other companies with a financial > interest in conquering some of these complexities. I think for some very > complex apps, what we’re working on could yield significant cost savings. > It would be a further good if our project were sufficiently useful to other > parties that it would make a good, solid addition to wicket core or wicket > extensions. > > > > If we can find some other interested parties, I might be able to work on > these problems full time. Additionally, we would have more perspectives and > possibly some assistance with implementing some of these design I am > flushing out now. > > > > Let me know if you know of any interested parties and please keep us > posted on your bean table project. I’m interested in how that goes and what > design you come up with. > > > > Best, > > > > Jon > > > > Sent from my iPhone > > > >> On Apr 16, 2025, at 3:26 AM, andrew goh <gohand...@yahoo.com.invalid> > wrote: > >> > >> While I'm learning the ropes of Apache Wicket currently and I'm > exploring making reusable components. > >> > >> I tried making An Apache Wicket reusable Data List > >> > >> This component displays a list of JavaBeans as a html table > >> > >> DataListPanel takes as input in the constructor : > >> > >> the wicket:id of the component > >> itemclass The java class of the JavaBean > >> List items the list of JavaBeans > >> > >> https://gist.github.com/ag88/a0232510c28b4c45b82943527b7ea87e > >> > >> This version is pretty rough as I'm trying out a 'proof of concept' > test. > >> it actually works, rendering the list of JavaBeans as a html table. > >> > >> I used an often 'neglected' java package java.beans, technology > Javabeans > >> https://en.wikipedia.org/wiki/JavaBeans > >> > https://download.oracle.com/otndocs/jcp/7224-javabeans-1.01-fr-spec-oth-JSpec/ > >> practically as 'old' as Java itself. > >> > >> It is probably quite interesting as many database interfaces basically > use JavaBeans to represent the records and as well used in forms. > >> This practically makes the task of displaying records in a (html) table > done using a reusable component. > >> > >> It is likely possible to implement similar setup say with > spring-framework, spring-boot and templates, but that Apache Wicket makes > the codes and templates very concise. > >> The magic is implemented by the repeating views > >> > https://nightlies.apache.org/wicket/guide/9.x/single.html#_the_repeatingview_component > >> and java.beans itself which I get the 'field' (beaninfo) names and java > reflection retrieval. > >> > >> I think it is likely feasible to implement such reusable pages as form > components too, i.e. give a form a JavaBean it renders it and > handles/process it with database CRUD and all. > >> > >> Cheers, > >> Andrew > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> >
