| [09:44:31] | <mstenta[m]> | Thanks for sharing edbob! |
| [09:45:27] | <mstenta[m]> | I think it's a great exercise to learn the farmOS data model by "mirroring" it in another system. |
| [09:46:12] | <mstenta[m]> | This is something we've talked about before... thinking about the "farmOS data model" as an independent piece from the "farmOS software" |
| [09:46:18] | <mstenta[m]> | And the current implementation (in Drupal) is the "reference implementation" |
| [09:46:59] | <mstenta[m]> | Different systems can benefit from the data model, while focusing on the things that matter to them. |
| [09:47:49] | <symbioquine[m]> | The biggest flaw IMHO in the current reference implementation (not farmOS' fault, but core Drupal's) is the weird lack of transactions when committing database changes. |
| [09:48:36] | <symbioquine[m]> | I mean flaw, relative to the ideal of what the data model could be. |
| [09:49:23] | <symbioquine[m]> | Though I personally would prefer more things to be immutable and function as a ledger of sorts - which could obviate many of the race conditions that the lack of useful commit transactions creates. |
| [09:50:38] | <symbioquine[m]> | All that said, I'm not sure if it's likely to be a real problem or just a theoretical one so that's why I haven't tried to work on it. |
| [09:52:56] | <mstenta[m]> | > this can be thought of as "farmOS lite" in a way... (full message at <https://matrix.org/oftc/media/v1/media/download/AV_j3hkqq3e4uIOBhW3fMiAp...) |
| [09:53:31] | <mstenta[m]> | I think the power of a shared data model is best leveraged when the systems built for it compliment each other, and solve unique/distinct problems. |
| [09:53:49] | <mstenta[m]> | So that's what I would be most excited to see. :-) |
| [09:57:32] | <mstenta[m]> | > I have found a couple of limitations (IIUC) with the API which prevent the "wrapper" mode from being *quite* as good |
| [09:57:32] | <mstenta[m]> | edbob I'd love to hear what you're finding too! |
| [10:01:44] | <mstenta[m]> | edbob: Also curious if you have decided how to deal with farmOS's modularity. eg: If someone installs a module in their farmOS server which extends the data model, does this get replicated? Or are you targeting a specific module set? |
| [11:45:22] | <edbob[m]> | hey thanks for the comments! i'll hop on today's call, maybe discuss some of the points raised. and/or i'll add more thoughts here afterward |
| [11:46:10] | <mstenta[m]> | Cool! |
| [11:46:36] | <mstenta[m]> | Good seque... |
| [11:47:02] | <mstenta[m]> | @room: The farmOS weekly dev call starts in ~13 minutes. All are welcome! https://meet.jit.si/farmos-dev |
| [11:47:34] | <mstenta[m]> | symbioquine: if we have some time maybe we can talk about SVGs :-) |
| [11:47:59] | <mstenta[m]> | I'm also working on https://www.drupal.org/project/farm/issues/2513056 if anyone's interested in seeing that |