dunbarx wrote: ↑Tue Aug 23, 2022 5:12 pm
But a table field should often be at least considered first.
My old boss used to say 'use the right tool for the job'.
Just not sure which jobs would actually make me choose the tableField over the DG
Even for simpler tables, the DG just makes life easier with it's very rich API - but that is also the difficulty, as learning the API is a modest learning curve. But for
new users, there is
also a learning curve for tableField that is not straightforward either.
Just to illustrate the counterpoint view - again influenced by familiarity (but in the opposite direction):
I personally feel the TableField is like a hack that cobbles stuff together to emulate a table that doesn't look that good by default, but it also doesn't make life easier (other than in very simple instances).
Yes, you
can get it looking nice and you
can get it to do more complex stuff, but that involves a whole lot of code, and for stuff that is given 'for free' in the data grid. I have yet to use a tableField and feel "ah, this was the right thing to use and it's so easy". I have used it on occasion, but each time it involved a whole lot of head-scratching, searching online and the API on how to bend it to my will... tabStops: ughhh...
Which is probably what others feel about the data grid
Case in point: I'm sure it's doable, but could someone post an example where a cell (note:
not the backgroundColor of the cell's text, but the whole cell) is coloured conditionally? It would be interesting (to me anyway) to compare code...
dunbarx wrote: ↑Tue Aug 23, 2022 5:12 pm
New users are often attracted to the DG early on.
This is an often repeated view here.
My take on this, as a 'newcomer' of two years (never mind when the forum says i joined, i only really started using LC in lockdown

), is that this is the view often expressed by those who were using LC long before the data grid came along.
Familiarity with the tableField probably influences these comparisons quite heavily - much in the same way i would favour the DG.
But remember: For new users there is a learning curve for both - and yes the DG has a more extensive API but is also better documented with more examples online. And once learned, the API gives you access to many conveniences. What we really need to be asking is how much more difficult it is using the data grid than a tableField for a
new user who is unfamiliar with both.
The tableField basically draws lines around tab-separated text; but then so does the data grid in the default table mode. For basic usage there is actually little difference between the two, except you already get draggable and sortable column headers with the DG, which you'd need to code for the tableField. Beyond (very) basic usage, tableField makes me work harder to achieve my goals and cramps my style
Having said that i'm rather enjoying the new grids as well that came with the megabundle; but both polyList and polyGrid have fewer features than the DG but are very good in what the do. In particular, polyList has a couple of sweet features not available in the data grid as seen on the blog:
https://livecode.com/building-an-airbnb ... -livecode/
So for me, it's now a choice between DG, PL and PG - i have no love for the TF!
Obviously this is
my preference and does and should not apply to anyone else - whatever makes you happy and productive is the right way to do it. Just sharing my views...
S.