- 🇺🇸United States m.stenta
We just opened the official 3.x branch of farmOS, so I'm going through and closing/updating old issues. I think we can close this meta issue and follow up in individual issues as necessary.
Field Kit is farmOS's mobile app. It is a decoupled progressive web app (PWA) that works offline and communicates with farmOS via the API. It's primary goal is to make data entry easy for common tasks, so that they can be recorded "in the field" with/without internet, and "synced" back to farmOS when an internet connection is available.
Because Field Kit is written in JavaScript, the other hope is that we can attract more developers/tinkerers who are interested in building farmOS features, but who may be less familiar with Drupal/PHP/server-side development. There has also been some discussion around including parts of Field Kit's Vue.js UI in farmOS itself, to create a "progressively decoupled" experience in the server side UI as well.
One of the ideas we've been talking about is converting the "Quick Forms" that farmOS currently provides to "Field Modules" in Field Kit. So instead of the quick forms being written in PHP / Drupal Form API, they would be written in Vue.js. This moves some of that UI/UX responsibility out of farmOS server and into the client app, where they can benefit from more modern client-side JavaScript features.
Most of the Field Kit discussion/issue tracking is done in GitHub: https://github.com/farmOS/farmOS-client
This issue can serve as a place to organize links to those, as well as server-related work that is needed to support it in 2.x.
GitHub issue for farmOS 2.x support in Field Kit: https://github.com/farmOS/farmOS-client/issues/419
farm_client OAuth client (see
https://www.drupal.org/project/farm/issues/3185721#comment-13923153 →
)farm_client to the list of "default" modules in farm.profileNot all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
We just opened the official 3.x branch of farmOS, so I'm going through and closing/updating old issues. I think we can close this meta issue and follow up in individual issues as necessary.