I was going to answer sooner but due to a series of unfortunate and unforeseen events I find myself on call 26 out of 30 consecutive days, and I’m only 10 days in
I only presume they must have purchased these widgets. PolyGrid was announced on these forums my FerrusLogic some months before being sold by LC ; they then pulled it and it suddenly appeared in the summer megabundle some months later.
Similarly the button widget is pretty much a carbon copy of an existing opensource offering - but of course they may have just not paid that developer.
All widgets have very sparse documentation with wildly different naming conventions (for example the array data of polyGrid is referred to with
pgData while the same for polyList is named
dataContent).
PolyGrid, as I’m sure you discovered, offers a subset of features the extremely capable DataGrid offers but is faster and more portable in the sense you can just copy/paste between stacks freely, because it doesn’t have the DG’s drawback of using a behaviour substack - it’s completely encapsulated.
DG still offers a much larger feature set and has its role, especially if you want the “form” rather than the “table” version. PolyList again offers a different subset (more of a “form” style grid) but also a new feature: you can have columns of rows.
But other than that, the DG can do everything these two widgets offer and has the benefit of letting us lay out row and column prototypes using the standard IDE and can use any available widget.
I don’t think buying widgets and distributing them is a bad thing though. A thriving ecosystem does need independent widget builders and so on, And if LC purchased these then good on them for supporting indie developers. I would find this reassuring and pleasing.
But they could have done a much better job with documentation of these new widgets…