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

2019-02-06
2019-02-08
TimeNickMessage
[19:05:27]<mstenta[m]>@jgaehring:matrix.org: oh weird. I just experienced the issue again I think, but this time a new log showed up without me going to the log form at all
[19:06:06]<mstenta[m]>All I did was open the app and click the "synced" link next to a previous log I had synced earlier today
[19:06:32]<mstenta[m]>And then:
[19:06:38]<mstenta[m]>ACTION uploaded an image: Screenshot_20190206-190616.png (87KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/yvEKHAXvzWjTskZz... >
[19:06:49]<mstenta[m]>Notice the second one
[19:07:01]<mstenta[m]>That showed up without going to the log edit screen at all
[19:14:35]<jgaehring[m]>Whoa
[19:15:06]<jgaehring[m]>Are you taking a lot of pictures?
[19:19:18]<jgaehring[m]>Hehe, trying a bunch of things to break it... This did it:
[19:19:25]<jgaehring[m]>ACTION uploaded an image: Screenshot_20190206-191841.png (108KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/hFVKLVJJtRrBimtp... >
[19:20:52]<jgaehring[m]>Although I blame the backend :-P
[19:46:19]* bodie1[m] has joined #farmos
[19:58:26]<mstenta[m]>No only the first log I made has a picture
[19:58:32]<mstenta[m]>Oh how did you do it?
[19:58:54]<mstenta[m]>It seems to happen inconsistently for me so it's hard to replicate
[19:59:57]<mstenta[m]>Oh nm you were testing something else I see :-)
[20:01:44]<mstenta[m]>Yeah that could be backend related
[20:01:58]<mstenta[m]>File a bug report
[20:02:49]<mstenta[m]>Might be the same thing that breaks farmBOT
[20:13:22]* Marflutter has joined #farmos
[20:13:23]* Marflutter has left #farmos ()
[20:37:10]<mstenta[m]>"farmOS Scout" seems to be in the lead :-)
[22:08:26]* bathrobinson has joined #farmos
[22:08:27]* bathrobinson has left #farmos ()
[22:33:48]* JustTB has quit (Ping timeout: 245 seconds)
[22:39:05]* Noktaeds has joined #farmos
[22:39:06]* Noktaeds has left #farmos ()
[22:49:04]* JustTB has joined #farmos
[05:48:26]* JustTB has quit (Quit: Leaving.)
[07:13:53]* JustTB has joined #farmos
[09:17:24]* JustTB has quit (Quit: Leaving.)
[10:59:36]* JustTB has joined #farmos
[11:33:54]<jgaehring[m]>cool!
[11:39:01]<jgaehring[m]>mstenta: have you cleared the app cache? I'm still not able to reproduce that bug, wondering if it's a problem with the SQL schema or something like that
[12:11:39]<mstenta[m]>jgaehring: I haven't. I'll try that and see if it happens again.
[13:33:28]<mstenta[m]>jgaehring: Great feedback on the poll so far!
[13:33:56]<mstenta[m]>Looks like "farmOS Scout" is the favorite still.
[13:34:22]<mstenta[m]>I like sudokita 's justification that she described in https://riot.im/app/#/room/#goatech:matrix.org
[13:35:42]<mstenta[m]>And I've been giving more thought to the thoughts I expressed over there:
[13:35:44]<mstenta[m]>> I like the other ones two (lite, scout, field kit) but I also worry that they are too narrow to encompass the future vision of it becoming a core part of normal farmOS (essentially allowing a simplified offline-first experience the you can then optionally toggle into "advanced" mode)
[13:36:23]<mstenta[m]>(Here are sudokita 's thoughts for cross-post:)
[13:36:38]<mstenta[m]>> Given what you're describing I am inclined to say nay to mobile, client, and lite. Client does make the most sense but I would worry that it isn't descriptive enough. Lite makes it seem likes it's missing "pro" functionality so I would also say nay to that. I do like scout and field kit though because it does make give the impression that the tool is meant for in-field use regardless of the slimmed down functionality for
[13:36:39]<mstenta[m]>now, or the optional advanced mode
[13:37:05]<mstenta[m]>I'm thinking: we could still call it "Scout" when we think about it in the context of including it directly in farmOS too...
[13:37:11]<mstenta[m]>or even "Scout Mode" :-)
[13:37:22]<mstenta[m]>So I can envision using farmOS in a browser, and then toggling "Scout Mode" so you can take it offline
[13:37:25]<jgaehring[m]>Haha, nice!
[13:39:51]<mstenta[m]>So question: do you think we should rename the repo to farmOS-scout as well? (in combination with merging farmOS-native and farmOS-client)
[13:40:06]<mstenta[m]>Or do you think it make sense to still use the name farmOS-client internally for dev purposes
[13:40:11]<sudokita[m]>ooo i like scout mode
[13:40:17]<mstenta[m]>And just name the app "farmOS Scout" when it is published to the app stores
[13:41:23]<mstenta[m]>(eg: the native app would be based on the farmOS-client codebase, but the app would be called "farmOS Scout"... and in the web context, farmOS would just pull in the farmOS-client library JS during build)
[13:43:30]<mstenta[m]>This question also helps to decide what to call the module that's included with farmOS... we've been referring to it as farm_offline... but maybe farm_client or farm_scout is a better choice (the main things it would do are 1) pull in the farmOS-client JS library, 2) add it to farmOS (either on a new path, or embedded on all pages somehow), 3) add a service worker to help trigger it when offline
[14:00:52]<mstenta[m]>Maybe I'll start a GitHub thread to document all this stuff, along with a link to the poll and a summary of the results
[14:01:05]<mstenta[m]>Be good to have for referring people to in the future if we are ever asked "why is it called this" :-)
[14:02:21]<jgaehring[m]>oh good idea!
[14:03:44]<mstenta[m]>should i do that in farmOS-client? or native?
[14:09:03]<jgaehring[m]>Haha, hmm, I still keep thinking of native as the main repo
[14:10:15]<mstenta[m]>Ok either way... we'll be transferring all the issues regardless
[14:10:32]<mstenta[m]>I'll do it in native, since the "Scout" name will apply to the iOS/Android app store apps, at the very least
[14:11:40]<jgaehring[m]>Cool
[14:11:45]<jgaehring[m]>Thanks!
[14:12:46]<mstenta[m]>I'll also create one for the "older version of android" warning - so we have something to point to for documentation purposes
[14:13:03]<mstenta[m]>(i don't think we have an open issue for that already, do we?)
[14:23:01]<jgaehring[m]>pretty sure that's b/c of this: https://cordova.apache.org/docs/en/latest/guide/platforms/android/index....
[14:23:01]<jgaehring[m]>you're running Pie, right?
[14:23:21]<mstenta[m]>Oh ok great - I'll refer to that
[14:23:26]<jgaehring[m]>PhoneGap Build uses cordova-android Version 6.x.x
[14:23:28]<mstenta[m]>Yes I think so
[14:23:43]<jgaehring[m]>so good to have an open issue, but there may be nothing we can do about it
[14:24:00]<mstenta[m]>Oh so it's a PhoneGap Build issue specifically
[14:24:05]<mstenta[m]>Not Cordova
[14:24:24]<jgaehring[m]>both, really
[14:24:56]<mstenta[m]>Oooh.. because Pie is Android 9
[14:24:58]<jgaehring[m]>even if we used cordova-android 7.x.x, it would only give us Android 8.1
[14:25:03]<jgaehring[m]>right
[14:25:05]<mstenta[m]>Yea gotcha
[14:25:06]<mstenta[m]>Womp
[14:25:30]<mstenta[m]>Oh hey: https://cordova.apache.org/announcements/2018/11/23/cordova-android-7.1....
[14:25:57]<mstenta[m]>> Update android-versions to 1.4.0, with added support for Android Pie (#573)
[14:26:02]<mstenta[m]>So maybe those other docs are outdated?
[14:26:20]<mstenta[m]>https://github.com/apache/cordova-android/pull/573
[14:26:40]<mstenta[m]>> * (seems to add support for Android Pie)
[14:28:56]<jgaehring[m]>oh i'll try it
[14:29:03]<jgaehring[m]>oh no i won't
[14:29:25]<jgaehring[m]>still gotta fix android studio i think
[14:29:38]<jgaehring[m]>then i can do it with the cli, instead of PGB
[14:30:30]<mstenta[m]>are you sure PGB doesn't support it? is that documented somewhere?
[14:31:01]<mstenta[m]>oh right you said it uses 6.x.x
[14:31:40]<mstenta[m]>hmm yea looks like that's right: https://build.phonegap.com/current-support
[16:24:42]* JustTB has quit (Quit: Leaving.)
[16:25:05]* JustTB has joined #farmos
[16:30:56]* JustTB has quit (Quit: Leaving.)
[16:31:17]* JustTB has joined #farmos