| [20:36:57] | * MiniMia has joined #farmos |
| [20:39:38] | * MiniMia has quit (Client Quit) |
| [00:10:49] | * ClaudiaSamp has joined #farmos |
| [00:13:13] | * ClaudiaSamp has quit (Client Quit) |
| [02:43:51] | * AnnaNystrom has joined #farmos |
| [02:43:52] | * AnnaNystrom has quit (Client Quit) |
| [06:14:54] | * SarahStep has joined #farmos |
| [06:17:18] | * SarahStep has quit (Client Quit) |
| [07:47:28] | * AmyGoal has joined #farmos |
| [07:49:47] | * AmyGoal has quit (Client Quit) |
| [10:32:01] | <symbioquine[m]> | Does https://github.com/paradise-berries/growroomOS look like a bulk copy of farmOS (without attribution) to anybody else? |
| [10:33:40] | <mstenta[m]> | It does! :-) |
| [10:34:14] | <mstenta[m]> | But I do see this: https://github.com/paradise-berries/growroomOS/issues/1 |
| [10:35:50] | <symbioquine[m]> | I didn't see that. |
| [10:36:01] | <mstenta[m]> | Seems like an inefficient way to go about it. Could have just added their modules on top of farmOS instead of copying and maintaining the whole distro |
| [10:36:12] | <symbioquine[m]> | yeah |
| [10:36:20] | <mstenta[m]> | Doesn't look like much has happened in the past year though |
| [10:36:53] | <mstenta[m]> | Curious how'd you find it @symbioquine:matrix.org ? |
| [10:37:23] | <symbioquine[m]> | Combing through examples of various drupal hook usage. |
| [10:38:28] | <mstenta[m]> | Ah cool! |
| [10:39:11] | <symbioquine[m]> | Most recently, trying to understand how `farm_fields_dynamic` and `farm_asset_property` are being used by folks. |
| [10:42:56] | <mstenta[m]> | Oh jeez |
| [10:42:58] | <mstenta[m]> | Haha |
| [10:45:04] | <symbioquine[m]> | I'm trying to make a module that will allow admins to curate a set of fields to be associated with logs/assets by querying standard crop/genetic ontologies from http://planteome.org |
| [10:46:16] | <symbioquine[m]> | e.g. I want to be able to gather data on awn characteristics for wheat/rice/etc in a way that is interoperable with other scientific datasets |
| [10:48:38] | <mstenta[m]> | Oh wow interesting |
| [10:48:48] | <mstenta[m]> | So the dynamic fields thing... |
| [10:48:56] | <mstenta[m]> | It was kind of an experiment I'm trying |
| [10:49:01] | <mstenta[m]> | I'm not sure about it |
| [10:49:23] | <mstenta[m]> | (also haven't looked at it in a long time) |
| [10:49:31] | <mstenta[m]> | So just FYI |
| [10:49:39] | <mstenta[m]> | It works fine |
| [10:50:10] | <mstenta[m]> | But one of the disadvantages is that when you export a Features module it includes the new field |
| [10:50:26] | <mstenta[m]> | Shrug emoji |
| [10:50:27] | <symbioquine[m]> | oh, yeah that would make sense |
| [10:52:02] | <symbioquine[m]> | Maybe that could be mitigated slightly by injecting some sort of metadata into the field description so it's clearer it shouldn't be checked in along with the rest of an exported feature's code. |
| [10:52:48] | <symbioquine[m]> | Similar to the way a lot of auto-generated files have a banner at the top saying they shouldn't be edited manually - it doesn't stop manual editing, but at least removes some of the confusion. |
| [10:53:05] | <mstenta[m]> | Oh yea perhaps |
| [10:53:34] | <mstenta[m]> | I'm sort of of the mind "this is all changing in D8 so let's figure out how it should work there" |
| [10:53:53] | <mstenta[m]> | Kinda just hoping that there's a better way in D8 |
| [10:54:10] | <symbioquine[m]> | Makes sense |
| [10:54:15] | <mstenta[m]> | But maybe that's wishful thinking |
| [10:54:24] | <mstenta[m]> | We'll see |
| [11:00:42] | * mmn has quit (*.net *.split) |
| [11:01:40] | * mmn has joined #farmos |
| [11:31:53] | <symbioquine[m]> | Another nuance of dynamic fields is that they don't seem to get removed if you uninstall the module that declared them. |
| [11:49:02] | <mstenta[m]> | Oh yea that makes sense |
| [11:49:32] | <mstenta[m]> | I'm not 100% sure how Features itself handles that |
| [11:49:48] | <mstenta[m]> | It might not delete the fields also |
| [11:49:59] | <mstenta[m]> | And leave it up to the site admin to do so |
| [11:50:10] | <mstenta[m]> | Safer assumption to avoid potential data loss |
| [11:53:36] | <symbioquine[m]> | agreed |
| [11:54:08] | <symbioquine[m]> | I also don't see a way to configure the field groupings for dynamic fields |
| [12:08:58] | <mstenta[m]> | Oh yea I think that's a little harder to do |
| [12:09:29] | <mstenta[m]> | It's easy to add fields (and new field groups) at the root entity level |
| [12:09:55] | <mstenta[m]> | But in order to put them in an existing field group you need to alter the group and the weights of fields within it |
| [12:10:22] | <mstenta[m]> | Probably doable but I avoided that complexity with the two dynamic fields I needed |
| [12:51:49] | * LisaMarie has joined #farmos |
| [12:54:04] | * LisaMarie has quit (Client Quit) |
| [18:14:03] | * ElizabethTu has joined #farmos |
| [18:14:06] | * ElizabethTu has quit (Client Quit) |