| [20:35:52] | <frakman1[m]> | ACTION uploaded an image: (119KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/pbjxVIsnDqrappiw... > |
| [20:36:07] | <frakman1[m]> | ACTION uploaded an image: (117KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/eATbtLUdltoZaJVo... > |
| [20:36:23] | <frakman1[m]> | OK, I built the `base` and `dev` with multi-arch support. |
| [20:55:57] | <mstenta[m]> | Awesome! |
| [21:05:36] | <frakman1[m]> | Phew finally! I got docker compose to work on the pi by just changing the docker images. |
| [21:05:43] | <frakman1[m]> | ACTION posted a file: (0KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/woLIXxsLJsIdrVPj... > |
| [21:09:02] | <frakman1[m]> | I can make a pull request with that change if you want. |
| [21:20:43] | <frakman1[m]> | https://github.com/farmOS/farmOS/pull/420 |
| [22:36:59] | <symbioquine[m]> | <paul121[m] "we need behavior settings for fa"> What did you mean by this paul121 ? |
| [23:17:07] | <paul121[m]> | Right now we have some "patterns" where farmOS-map behaviors in Drupal will use the global `drupalSettings.*` JS variable to configure their behavior |
| [23:17:42] | <paul121[m]> | * Right now we have some "patterns" where farmOS-map behaviors in Drupal will use the global `drupalSettings.farm_map.behaviors.*` JS variable to configure their behavior |
| [23:18:04] | <paul121[m]> | the WKT is one that does this |
| [23:18:11] | <paul121[m]> | * the WKT behavior is one that does this |
| [23:20:12] | <paul121[m]> | also things like the `popup` behavior modify the map whenever they are loaded on the page, so the method for controlling the behavior is essentially configuring if the JS script is included on the page |
| [23:21:04] | <paul121[m]> | I'd like to see the map behaviors become a bit more "reusable" - meaning a single map behavior could be *configured* for the specific map/context it's being used in |
| [23:22:28] | <paul121[m]> | instead of using the global `drupalSettings` for this, it would nice if farmOS-map instances could have a "settings state" for behaviors. Something like `instance.settings.get/set('behaviorName'...)` |
| [23:22:45] | <paul121[m]> | * instead of using the global `drupalSettings` for this, it would be nice if farmOS-map instances could have a "settings state" for behaviors. Something like `instance.settings.get/set('behaviorName'...)` |
| [23:23:49] | <paul121[m]> | I think this could allow behaviors to "configure" each other too |
| [23:26:03] | <paul121[m]> | a neat use case might be an abstract `geojson` layer behavior - it could be configured to use a specific URL, parameters, etc... in 2.x we have the ability to define these in configuration yml, and even build the configuration via the UI... so folks could potentially configure custom geojson layers (or really any layer type) from the UI without any PHP code! |
| [23:32:04] | <paul121[m]> | this could almost decouple behaviors from the Drupal JS side of things too... so the same JS code could be used by other apps using farmOS-map (like FK) |
| [00:56:37] | <symbioquine[m]> | Awesome, thanks for explaining! |
| [00:57:58] | <symbioquine[m]> | I assume you mentioned it because that would be one option for controlling the whether something like this "touch drawing" functionality is enabled? |
| [00:58:42] | <paul121[m]> | yep! |
| [00:59:25] | <paul121[m]> | so perhaps the "bed generator behavior" could use that "touch drawing" behavior and configure for its needs |
| [01:01:08] | <symbioquine[m]> | Yeah, that's an option. |
| [01:01:20] | <symbioquine[m]> | I was thinking about making it like the tools in photoshop/gimp where you right click (or hold on mobile) to change from the normal drawing tool to a touch version... |
| [01:02:13] | <paul121[m]> | ah yea. that might be better anyways |
| [01:04:03] | <symbioquine[m]> | ACTION uploaded an image: (12KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/uOtKyDdepZEisVcg... > |
| [01:04:41] | <symbioquine[m]> | The tools that support different "modes" have those little carrots at the corner to indicate that you can right click to switch between them. |
| [01:05:38] | <symbioquine[m]> | That said, I don't know whether it's a ubiquitous enough UX paridigm. |
| [01:16:50] | <paul121[m]> | ah hmmm... yeah would be nice to have a standard button type for that |
| [07:13:24] | <jgaehring[m]> | farmOS-map should have a fuzzy select tool |
| [07:33:51] | <mstenta[m]> | That's a cool idea! For selecting areas of similar color? Like fields? :-) |
| [07:58:45] | <jgaehring[m]> | yea, for image tiles select against certain color ranges, although it might be cool if you could also select for other attributes too |
| [11:43:17] | * farmBOT has joined #farmos |
