| [20:24:47] | <symbioquine[m]> | I was curious about the current state of 2.x development so I started playing around with the 2.x branch following these [setup instructions](http://2x.farmos.org/development/environment/)... I see there are more fields defined in the source, have I set it up wrong or is there more development work needed for those fields to be editable through the UI? |
| [20:24:51] | <symbioquine[m]> | ACTION uploaded an image: image.png (74KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/sJPiJhTNYgBCcywb... > |
| [20:25:22] | <mstenta[m]> | aha! i'm actually working on that at this very moment :-) |
| [20:25:47] | <symbioquine[m]> | oh, cool |
| [20:26:13] | <mstenta[m]> | basically: in D9, you create fields as config files, but then you organize the "form display" and "view display" as a config file itself |
| [20:26:35] | <mstenta[m]> | so i've been adding fields, just haven't added the form/view display config yet... so all the fields are hidden by default in the form and display |
| [20:27:17] | <symbioquine[m]> | figured it might be something like that :) |
| [20:27:40] | <mstenta[m]> | the form/view display config is a bit trickier, because it's all in one file per log/asset type... and i want to allow the "Equipment" field to be optional... which means that config needs to be somewhat dynamically generated/altered |
| [20:28:30] | <mstenta[m]> | the fields themselves are easy because they are one YML config file per field - so the equipment field can be added without needing to modify any existing config |
| [20:29:50] | <symbioquine[m]> | When you say "optional" you mean only present when the equipment module is enabled right? |
| [20:29:55] | <mstenta[m]> | yea |
| [20:30:14] | <mstenta[m]> | you're familiar with the "dynamic field" module in farmOS 1.x right? |
| [20:30:22] | <mstenta[m]> | i think i remember you looking at that :-) |
| [20:30:59] | <mstenta[m]> | so... that's not needed in D9 anymore - because fields can pretty easily be added just by providing a YML file in the module that wants to add it... the only tricky part is adding it to the form/display config |
| [20:31:28] | <symbioquine[m]> | Interesting |
| [20:31:50] | <symbioquine[m]> | So you need some sort of hook mechanism so that the other module can extend the form/display of the core module for the asset? |
| [20:31:56] | <paul121[m]> | Enable the Field UI module, then go to admin -> structure -> asset/log types -> manage display/form display |
| [20:31:57] | <paul121[m]> | That will allow you to poke around if you want! |
| [20:32:10] | <mstenta[m]> | yea still thinking through what the best approach will be, and what the options are... |
| [20:33:11] | <mstenta[m]> | the drupal 9 config system is really really slick |
| [20:33:22] | <paul121[m]> | * Enable the Field UI module, then go to admin -> structure -> asset/log types -> manage display/form edit display (something like that) |
| [20:33:22] | <paul121[m]> | That will allow you to poke around if you want! |
| [20:34:09] | <mstenta[m]> | but our use case as a distro is somewhat unique, so figuring out the best ways to manage config has been fun :-) |
| [20:34:52] | <mstenta[m]> | FYI big picture: we have NOT been doing much with the 2.x UI yet... sort of focusing on data model + API + migration to start |
| [20:35:03] | <mstenta[m]> | so you'll find it very lacking in that regard :-) |
| [20:35:11] | <symbioquine[m]> | No worries |
| [20:35:55] | <symbioquine[m]> | Just trying to get my feet under me to see 1) what it will take to port my custom stuff over 2) where it might make sense to help out |
| [20:36:10] | <mstenta[m]> | awesome! yea excited to have you poke around! |
| [20:36:37] | <mstenta[m]> | feel free to ask questions... the roadmap/issues are taking shape, but could use some updating/additions |
| [20:37:14] | <mstenta[m]> | in general, the big data model pieces left are: areas/movements/location (i'm working on), quantities (Paul is wokring on), inventory, group membership |
| [20:37:43] | <mstenta[m]> | we're thinking about making inventory part of the quantity fields... |
| [20:37:50] | <mstenta[m]> | and i'm thinking about approaching group membership similar to location |
| [20:38:02] | <mstenta[m]> | so i'm optimistic that things will fall together pretty quickly |
| [20:38:19] | <symbioquine[m]> | <mstenta[m] "feel free to ask questions... th"> Thanks, will do! |
| [20:39:02] | <mstenta[m]> | oh and plans |
| [20:39:37] | <mstenta[m]> | we will be starting on some of the ui/ux stuff before data model is 100% complete too... pcambra and I are going to be porting the forest plan module to 2.x, and will be trying to focus on some of the main things that needs (including maps) |
| [20:40:02] | <mstenta[m]> | lots of moving pieces, but moving along! :-) |
| [20:40:28] | <symbioquine[m]> | <mstenta[m] "we're thinking about making inve"> Abstractly, that makes a lot of sense since I've observed that having two ways of tracking "amounts" of things can be confusing to new users - and inventory could benefit from a concept of units. Naturally, getting the details right is a little harder :) |
| [20:41:24] | <mstenta[m]> | yes! that's exactly the reasoning... eg: recording an input that applies a certain amount of material to a field... you don't want to have to enter the same value in two places on the log (one for the quantity and one for the inventory adjustment) |
| [20:41:26] | <symbioquine[m]> | I take it https://www.drupal.org/project/issues/farm is the main place where the outstanding work is being tracked? |
| [20:42:08] | <mstenta[m]> | so i think we'll just essentially add a checkbox to quantities "adjust inventory" or something, which then shows two more fields: an asset reference, and dropdown "increment/decrement/reset" options |
| [20:42:36] | <mstenta[m]> | yes! here is the main roadmap issue: https://www.drupal.org/project/farm/issues/3092830 |
| [20:42:44] | <mstenta[m]> | that branches into child issues... |
| [20:43:17] | <mstenta[m]> | the roadmap is pretty well organized... definitely a work in progress |
| [20:43:40] | <mstenta[m]> | the high level meta issues cover all the main areas of work |
| [20:43:53] | <mstenta[m]> | the lower level tasks are more sparse |
| [20:44:29] | <mstenta[m]> | i need to go through and give them a pass to update |
| [04:00:04] | * canadrian[m] has quit (Quit: Idle for 30+ days) |
| [10:59:16] | * cpm has joined #farmos |
| [11:00:04] | * munjoma[m] has quit (Quit: Idle for 30+ days) |
| [11:00:04] | * wombat83[m] has quit (Quit: Idle for 30+ days) |
| [13:14:19] | * cpm has quit (Quit: Leaving) |
