IRC logs for #farmOS, 2019-02-12 (GMT)

2019-02-11
2019-02-13
TimeNickMessage
[19:14:44]* JustTB has quit (Quit: Leaving.)
[19:15:41]* JustTB has joined #farmos
[22:29:10]* JustTB has quit (Ping timeout: 268 seconds)
[22:43:39]* JustTB has joined #farmos
[04:26:33]* apm has joined #farmos
[04:27:38]* apm has quit (Client Quit)
[05:09:54]* JustTB has quit (Ping timeout: 250 seconds)
[05:46:07]* JustTB has joined #farmos
[07:53:44]* JustTB has quit (Quit: Leaving.)
[07:54:18]* JustTB has joined #farmos
[09:52:29]* robcert[m] has joined #farmos
[11:22:39]<jgaehring[m]>hey mstenta and alexasbeet
[11:22:39]* alexasbeet[m] has joined #farmos
[11:22:40]<alexasbeet[m]>Hey!
[11:22:40]<farmBOT>bonjour
[11:22:44]<mstenta[m]>Hiya!
[11:23:07]<jgaehring[m]>oh hi farmbot
[11:23:12]<mstenta[m]>Thanks - better to centralize and document some of this discussion whenever possible :-)
[11:23:25]<jgaehring[m]>[eye-roll emoji]
[11:23:41]<mstenta[m]>FYI: this room is logged to http://irc.farmos.org/
[11:23:46]<mstenta[m]>Haha
[11:24:15]<jgaehring[m]>so here's what i was thinking re: specializing forms in the native/client/scout app....
[11:24:29]<alexasbeet[m]>yes!
[11:24:37]<jgaehring[m]>we think of the generic edit log form as being uniform for ever type of log...
[11:25:08]<jgaehring[m]>and maybe in the future we adapt the "quick forms" approach for specific type of entries
[11:25:25]<jgaehring[m]>and create links to those quick forms in the menu
[11:25:50]<alexasbeet[m]>OK, I like that pretty well
[11:25:52]<jgaehring[m]>perhaps phase out the "New Input", "New Observation" links if users don't seem to have much use for them
[11:26:29]<alexasbeet[m]>So would we just go back to 'new log' with a selector for log type?
[11:26:48]<jgaehring[m]>possibly
[11:26:50]<mstenta[m]>> perhaps phase out the "New Input", "New Observation" links if users don't seem to have much use for them
[11:26:51]<mstenta[m]>Not sure I understand this
[11:27:02]<mstenta[m]>But I agree with everything else, generally
[11:27:04]<jgaehring[m]>just a possibility
[11:27:08]<alexasbeet[m]>I'd be OK with that, but I think we would need the quick forms sooner rather than later. Folks are gonna want their UI pretty streamlined when doing field work
[11:27:26]<jgaehring[m]>i agree
[11:27:37]<jgaehring[m]>i want to see some options like that soon
[11:29:09]<alexasbeet[m]>Maybe that is something we can discuss with Angela. We could create one or two quick forms based on her common needs
[11:29:21]<alexasbeet[m]>They would be pretty easy to make
[11:29:33]<alexasbeet[m]>Just a pairing-down of what we already have
[11:29:59]<jgaehring[m]>mstenta: i meant the menu options in the drawer, "New Input", "New Observation", etc
[11:30:32]<alexasbeet[m]>So what I'm imagining in the menu is something like "new log", "quick observation", "quick input",
[11:30:48]<mstenta[m]>jgaehring: yea, didn't understand why you would remove those two... but leave activity and harvest? seems inconsistent
[11:30:58]<mstenta[m]>or maybe you meant all four
[11:31:03]<jgaehring[m]>oh, i meant maybe we remove all four
[11:31:04]<jgaehring[m]>yea, sorry
[11:31:10]<mstenta[m]>ah gotcha
[11:31:14]<jgaehring[m]>if they don't prove to provide much utility
[11:31:16]<mstenta[m]>yea ok i follow :-)
[11:31:17]<mstenta[m]>makes sense
[11:31:19]<jgaehring[m]>compared to quick forms
[11:31:24]<mstenta[m]>yup
[11:32:34]<alexasbeet[m]>So do you think we should mock up a quick input at this point, or wait an let Angela pick out what she would like in one
[11:34:36]<jgaehring[m]>i think it's good to get inputs working in a generic log entry first
[11:35:12]<jgaehring[m]>since there's a lot of additional work that just that will require, like pulling in logs from the server, etc
[11:35:48]<mstenta[m]>Yea I also wonder how that might relate to the bigger question of quick forms that are site-specific
[11:36:02]<mstenta[m]>eg: farmOS can have quick forms provided by optional modules
[11:36:06]<mstenta[m]>So not everyone has/needs them
[11:36:36]<mstenta[m]>jgaehring and I had brainstormed some ideas for handling that in the app too... but that's still going to require more design/discussion
[11:36:43]<mstenta[m]>Which is probably outside the scope of the project with Angela
[11:37:20]<alexasbeet[m]>I like that as a future goal, but in the short term it might make sense to have some pre-fab quick forms for creating common kinds of records. I really think it would make the app more usable and attractive
[11:38:12]<mstenta[m]>Sure, i like that idea too
[11:38:30]<alexasbeet[m]>My vote would be to offer to make Angela one or two simplified forms based on her common needs, and plan to offer those as our first built-in quickforms when we release the app to the public.
[11:38:40]<mstenta[m]>And with inputs in particular, all sites will have that
[11:39:46]<mstenta[m]>The challenge with a "simplified" form is always: how many use-cases are we NOT taking into account?
[11:40:02]<jgaehring[m]>yea, i think more and more, that modularizing the client will require us having a working web-based implementation (with full offline functionality)... i think for the near term we can play around with this stuff in the app, but we should be mindful that what we do for one user is not necessarily going to have universal appeal
[11:40:15]<mstenta[m]>And thus how might we end up "un-simplifying" this in the future if/when people complain
[11:40:27]<mstenta[m]>And does that lead us right back to the general "Add log" form?
[11:40:32]<alexasbeet[m]>Very true - but we can always re-design them later. Since we're offering the full new log view alongside, we're not leaving anyone out in the cold entirely
[11:41:00]<jgaehring[m]>i think of the native version still as very much a prototype
[11:41:00]<mstenta[m]>yea true
[11:41:20]<jgaehring[m]>well, i think we have to be cautious about just saying "well, we can remove that in the future"
[11:41:33]<mstenta[m]>yea, that's true too... easier to add than to remove
[11:41:39]<alexasbeet[m]>Fair enough
[11:41:51]<jgaehring[m]>which is why i like the idea of sticking with the generic form for now
[11:41:52]<mstenta[m]>just something to be considering alongside everything
[11:42:41]<mstenta[m]>that's a big consideration with farmOS itself, of course... because as soon as something is included (esp in the database), we have to assume that it will have data in it... so any changes need to either migrate that data or leave it alone
[11:42:41]<alexasbeet[m]>I've gotta take off for a bit in a few minutes - is there anything we should touch on quickly while we're all here?
[11:43:30]<alexasbeet[m]>RE the forms, do we want to bring up with Angela that making a simplified data entry form is something we COULD do, and let her decide if it's important to her?
[11:43:54]<jgaehring[m]>i think we're pretty good with the mockup we have, alex, we don't need to get too crazy with it, i'll work on the styles and maybe see if i can finish adding autocomplete easily enough
[11:44:26]<jgaehring[m]>switching over to Hangouts for Knuth Farm info...
[11:44:35]<alexasbeet[m]>OK, good, I'm glad that worked out
[12:00:42]<mstenta[m]>> I can help with testing on iOS. My Apple ID is simbiso[at]gmail
[12:01:01]<mstenta[m]>jgaehring: can you add munjoma to testflight
[12:01:14]<mstenta[m]>(or wait... i might have that ability too)
[12:01:22]<jgaehring[m]>sure!
[12:01:25]<mstenta[m]>Also, Franklin at PASA wanted to be a beta tester
[12:02:09]<mstenta[m]>awesome! i'll DM you Franklin's email as well...
[12:06:15]<jgaehring[m]>great, I just added munjoma and Franklin!
[12:06:24]<jgaehring[m]>anyone else who's interested, let me know!
[18:12:03]* ntropy[m] has joined #farmos