| [07:21:37] | <farmBOT> | @farmOS@fosstodon.org => #farmOS 3.1.1 has been released! https://github.com/farmOS/farmOS/releases/3.1.1 => https://fosstodon.org/@farmOS/111895748939346046 |
| [11:52:03] | <mstenta[m]> | Sneak peak of the v3 crop plan module at the Pasa Conference booth... ;-) |
| [11:52:18] | <mstenta[m]> | ACTION uploaded an image: (100KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/CxpfpTDsPXgeszqx... > |
| [11:59:39] | <paul121[m]> | Dev call in a few minutes! https://meet.jit.si/farmos-dev |
| [11:59:55] | <paul121[m]> | We might be able to pull up the same demo ^ ;-) |
| [12:00:15] | <mstenta[m]> | I won't be able to attend, but take notes if you do! |
| [12:56:51] | <symbioquine[m]> | jgaehring: I guess this is actually as close as I needed to get to modeling an explicit state machine: https://github.com/symbioquine/ol-touch-draw/blob/a709fcc9e3858b6f632da9... |
| [12:57:13] | <symbioquine[m]> | Lots of implicit ones of a similar complexity though I think. |
| [13:04:35] | * jgaehring[m] has joined #farmos |
| [13:04:36] | <jgaehring[m]> | <symbioquine[m]> "Lots of implicit ones of a..." <- ah, cool, yea one of the nice things about a state machine is how it can help structure your code and make those implicit state relations more explicit |
| [13:04:41] | <jgaehring[m]> | this is the one I was referring to: |
| [13:04:41] | <jgaehring[m]> | https://github.com/jgaehring/geotrace/blob/fabe4de7b800b8509d2ce157c1324... |
| [13:07:15] | <symbioquine[m]> | <mstenta[m]> "I won't be able to attend, but..." <- I don't know if Paul took notes, but we looked over the crop planning module and discussed the Gantt chart library. I mentioned that for the demo it would be nice to see an example of multiple plantings with overlapping/consecutive timing in the same location - when viewing by location. We also discussed the color choices and whether those should be modeled such that they can be used |
| [13:07:15] | <jgaehring[m]> | then the stepState() function below is what actually runs the state machine |
| [13:07:15] | <symbioquine[m]> | in more places in farmOS - like coloring the "log type" column in the logs views. |
| [13:11:54] | <symbioquine[m]> | symbioquine[m]: We also touched on broader use of Svelte, and how builds happen on Drupal.org. |
| [13:11:54] | <symbioquine[m]> | Did I missed anything... paul121 jgaehring fosten ? |
| [13:13:35] | <jgaehring[m]> | what were the server-side components that pcambra mentioned? |
| [13:32:07] | <pcambra[m]> | https://herchel.com/articles/single-directory-components-core |
| [13:33:04] | <pcambra[m]> | you can now define a template with props and attached js/styles |
| [13:33:10] | <pcambra[m]> | all in the same directory as it is a plugin |
| [13:33:56] | <pcambra[m]> | storybook integration is also there https://video.mateuaguilo.com/w/cKsHjwRLvW5bK2TawNrDdN so it is quite a cool improvement |
| [14:22:20] | <mstenta[m]> | Cool! Sounds like a great discussion! |
| [18:54:19] | <mstenta[m]> | > it would be nice to see an example of multiple plantings with overlapping/consecutive timing in the same location - when viewing by location. |
| [18:54:19] | <mstenta[m]> | symbioquine: Yea! There are still some bugs to iron out with the "by location" display (and "by plant type" for that matter), but they will basically just display as separate rows - nothing preventing you from having the same thing in the same place |
| [18:54:45] | <mstenta[m]> | Although maybe it would be useful to offer a warning/highlight option if you want to prevent that |
| [18:55:51] | <mstenta[m]> | > We also discussed the color choices and whether those should be modeled such that they can be used in more places in farmOS - like coloring the "log type" column in the logs views. |
| [18:55:52] | <mstenta[m]> | Yes! I actually copied the log colors from the calendar module, but it would be great to formalize them in core somehow. |
| [18:56:04] | <mstenta[m]> | Love the idea of using them in the log lists too! |
| [18:57:22] | <mstenta[m]> | In the calendar module I basically just hard coded colors for some of the core log types, but IMO we could let each log type module define them |
| [18:57:34] | <mstenta[m]> | We do something similar with map layer colors already |
| [18:58:43] | <mstenta[m]> | This crop planning module is definitely opening up many cans of worms... and I'm really excited about all of them 😄 |
