| [21:16:12] | <NewAdvert[m]> | https://t.me/+NKDMM2esA74xMWQx |
| [21:20:44] | <symbioquine[m]> | Welp, that was predictable... |
| [21:20:55] | <symbioquine[m]> | ACTION uploaded an image: (49KiB) < https://matrix.org/oftc/media/v1/media/download/AU712q8NheHD3ZQAyjyR6nvJ... > |
| [23:29:16] | * farmBOT has joined #farmos |
| [11:52:37] | <Greg[m]> | Question... I can't quite seem to be 100% confident I got this... |
| [11:52:37] | <Greg[m]> | Imagine I have a land asset (with a geometry). Then I do a seeding in that land asset (plant asset with it with seeding, so both end up with geometries). Now imagine I create a log and associate it only with the plant asset... should the business logic copy the plant asset geometry into the log when it's saved? Right now, I'm noticing my logs lack geometries and I can't tell if that's expected or not. Anyone know? |
| [11:58:45] | <symbioquine[m]> | <Greg[m]> "Question... I can't quite seem..." <- I seem to remember it copies the location(s) geometry, but not the asset(s) geometry. |
| [12:10:03] | <Greg[m]> | <symbioquine[m]> "I seem to remember it copies the..." <- Thanks - that's helpful. that seems like that's what's happening. I'll need to think about my intended behavior in this case. |
| [12:18:38] | <mstenta[m]> | <Greg[m]> "Thanks - that's helpful. that..." <- yea it doesn't copy asset geometry |
| [12:18:53] | <mstenta[m]> | mstenta[m]: but that's something i've wanted too |
| [12:19:34] | <mstenta[m]> | mstenta[m]: that's not always what you'd want, though, so it would need to be configurable |
| [14:25:52] | <Greg[m]> | <mstenta[m]> "that's not always what you'd..." <- Yes, agreed... not sure if copy once or calculate is better here... or maybe just don't worry about it and allow the UI to deal with it (like... you can just dig back into any related references to see where they are, and display if/when needed)... dunno. |
| [15:41:18] | <mstenta[m]> | <Greg[m]> "Yes, agreed... not sure if..." <- I thought maybe a button to manually copy geometry in the log edit form might be the best option |
| [15:43:40] | <Greg[m]> | mstenta[m]: I like that. I've thought about having a UI element that searches through related asset locations and pulls them forward for view. Gives you a sense of what's connected without actually changing the data structure, and reassures a user "yeah... this log is actually talking about Field A" if they think in terms of Fields and not Plant assets (which many folks do) |
| [15:44:12] | <Greg[m]> | Greg[m]: I might trial it on the quickforms actually, it's a nice little testbed for it |
| [19:12:24] | * Advert[m] has joined #farmos |