| [22:35:22] | * JustTB has quit (Ping timeout: 250 seconds) |
| [22:50:22] | * JustTB has joined #farmos |
| [05:21:40] | * JustTB has left #farmos () |
| [12:27:46] | * mstenta has joined #farmos |
| [12:30:24] | * mstenta has quit (Client Quit) |
| [12:36:00] | <jgaehring[m]> | mstenta: ping... is this where you want to chat? |
| [12:36:19] | <mstenta[m]> | jgaehring: Yes! |
| [12:36:40] | <mstenta[m]> | That way our convo gets logged to http://irc.farmos.org/ |
| [12:36:56] | <mstenta[m]> | (And others can see and chime in) |
| [12:38:40] | <jgaehring[m]> | cool! |
| [12:39:59] | <jgaehring[m]> | so as i was starting to say, about the client app, I'm wondering how we want to promote it, and even, just for starters, what we call it |
| [12:40:37] | <jgaehring[m]> | it could just be "farmOS", but on the app stores, but I wondered if we wanted some kind of name to denote that, at least for now, this is just a subset of farmOS's functionality |
| [12:41:39] | <jgaehring[m]> | both for users migrating over from the Drupal farmOS, and for new users who perhaps stumble on the app w/o realizing it's a part of something bigger |
| [12:41:59] | <jgaehring[m]> | like "farmOS Field Kit" or something like that |
| [12:42:42] | <mstenta[m]> | Yea good question |
| [12:42:49] | <mstenta[m]> | I think it does make sense to differentiate it, because I think there's already a lot of potential for confusion |
| [12:43:03] | <jgaehring[m]> | right |
| [12:43:05] | <mstenta[m]> | I personally like "farmOS Client", but I'm not sure if that makes any sense outside of our circle |
| [12:43:13] | <jgaehring[m]> | avoiding confusion === priority 1 |
| [12:44:08] | <mstenta[m]> | Aside from the name, we should be sure to have a clear and concise description |
| [12:44:18] | <jgaehring[m]> | right |
| [12:44:40] | <jgaehring[m]> | perhaps that would be sufficient |
| [12:44:43] | <mstenta[m]> | Like: "This app connects to your existing farmOS system to provide some useful shortcuts and offline capabilities." |
| [12:45:16] | <mstenta[m]> | Part of me thinks "farmOS Offline" would be the most intuitive - and would clearly define what it's useful for right now |
| [12:45:25] | <mstenta[m]> | But I also know that might not be a good long-term choice |
| [12:45:46] | <mstenta[m]> | "Client" really seems to be the best, to encompass the future plans |
| [12:45:59] | <mstenta[m]> | Especially with the thought that it will merge into farmOS itself |
| [12:47:04] | <dornawcox[m]> | mabe FarmOS lite or FarmOS mobile? or FarmOS field? |
| [12:47:15] | <mstenta[m]> | The drawback is it's a bit "developer-y" - "client vs server" |
| [12:47:22] | <mstenta[m]> | Hi @dornawcox:matrix.org ! |
| [12:47:44] | <mstenta[m]> | "farmOS lite" is kinda nice |
| [12:48:09] | <mstenta[m]> | I'm not a huge fan of "mobile" just because, technically, you can use the normal farmOS in a mobile browser context |
| [12:48:46] | <dornawcox[m]> | farmOS remote? |
| [12:49:01] | <mstenta[m]> | It will be really good to decide on a name though... I'm sick of saying "we're working on a mobile/offline/native/client/blahblahblah version!)" :-) |
| [12:49:02] | <dornawcox[m]> | means far away and control |
| [12:49:03] | <jgaehring[m]> | oh lite is nice |
| [12:49:42] | <jgaehring[m]> | > I'm sick of saying "we're working on a mobile/offline/native/client/blahblahblah version!)" :-) |
| [12:49:43] | <jgaehring[m]> | agreed! |
| [12:49:47] | <mstenta[m]> | "Lite" is also nice because we've talked about sort of differentiating the "advanced farmOS" UI from this "simplified" UI |
| [12:50:10] | <mstenta[m]> | How about we come up with a few choices and make a poll? |
| [12:50:15] | <mstenta[m]> | Then we can get input from lots of people |
| [12:50:34] | <jgaehring[m]> | i like the idea of "remote" too, kinda what I was thinking with the word "field" |
| [12:50:35] | <mstenta[m]> | "Remote" is pretty nice too |
| [12:51:23] | <mstenta[m]> | If we make a poll, I can send out a newsletter to get feedback |
| [12:51:40] | <mstenta[m]> | We're overdue for a newsletter to let everyone know we're working on it :-) |
| [12:51:57] | <mstenta[m]> | And then maybe we can do another one later when the official app store (and officially named) version is launched |
| [12:52:11] | <mstenta[m]> | @dornawcox:matrix.org: you GOTTA see what Jamie and Alex have been working on! |
| [12:52:15] | <mstenta[m]> | It's getting REAL SLICK! |
| [12:52:47] | <dornawcox[m]> | we will also have the more complex versions of farmOS that will hav more aggregation and data exploring features that ill need a name too- FarmOS Research, or MultiFarmOS, or LandscapeFarmOS, FarmOS explorer? |
| [12:53:56] | <mstenta[m]> | Yea... and depending on where those make sense to build, they could either be separate apps (based on the same framework as this client) or as farmOS/Drupal modules |
| [12:54:14] | <dornawcox[m]> | Can't wat to check it out. Really looking forward to FarmOS P2P chat too! |
| [12:54:41] | <mstenta[m]> | Haha yea! |
| [12:54:46] | <mstenta[m]> | donblair: cabal? ;-) |
| [12:55:21] | <mstenta[m]> | I was thinking it might be neat to just embed the Riot chat inside farmOS somehow... so that people who are using it can quickly ask questions |
| [12:56:27] | <mstenta[m]> | Oh jgaehring I'll look into the `/farm.json` endpoint to see what's up on Farmier |
| [12:56:59] | <dornawcox[m]> | I think that would be a great place to start - and move to something like cabal as we figure out the next phase of IOT hosting and deployment in the field. |
| [12:57:43] | <mstenta[m]> | Yea |
| [12:57:46] | <dornawcox[m]> | Riot for internal farm communications would be a great start. |
| [12:58:11] | <mstenta[m]> | Ah yea - internal communications too |
| [12:58:13] | <mstenta[m]> | Vs community/public chat |
| [13:00:18] | <mstenta[m]> | jgaehring: ah i see why `/farm.json` was giving access denied... |
| [13:00:20] | <mstenta[m]> | fixing now... |
| [13:00:40] | <jgaehring[m]> | oh awesome! |
| [13:00:56] | <mstenta[m]> | i just mixed up the permissions names... |
| [13:01:05] | <mstenta[m]> | "access farm api info" vs "access farm info api" |
| [13:01:37] | <jgaehring[m]> | http://www.catb.org/jargon/html/Z/Zawinskis-Law.html |
| [13:02:36] | <mstenta[m]> | haha |
| [13:02:38] | <mstenta[m]> | yup |
| [13:03:13] | <mstenta[m]> | I would probably make any chat module a separate add-on... so it's not actually part of farmOS officially |
| [13:03:43] | <mstenta[m]> | (and someone else can maintain it, perhaps) |
| [13:06:07] | <mstenta[m]> | jgaehring: ok - fix deployed to test.farmos.net |
| [13:06:14] | <jgaehring[m]> | sweet! |
| [13:06:17] | <mstenta[m]> | you can pull in the commit and clear cache on your dev site to test locally |
| [13:09:10] | <jgaehring[m]> | great, although it wasn't an issue locally, for whatever reason |
| [13:09:37] | <mstenta[m]> | oh maybe because you were using admin user |
| [13:09:46] | <mstenta[m]> | (uid 1 has all permissions) |
| [13:11:54] | <jgaehring[m]> | Ahh |
| [13:12:04] | <jgaehring[m]> | It's working! |
| [13:12:10] | <jgaehring[m]> | ACTION uploaded an image: Screenshot_20190205-131131.png (83KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/jNAUgjCiGhWSPdaB... > |
| [13:12:16] | <mstenta[m]> | Woo hoo! |
| [13:13:21] | <mstenta[m]> | How did you trigger it to update the drawer? I'm still seeing "Login for more options" on mine |
| [13:13:38] | <jgaehring[m]> | Login again |
| [13:15:31] | <mstenta[m]> | I did (?) |
| [13:15:41] | <mstenta[m]> | I clicked "Login Screen" and then "Submit Credentials" |
| [13:15:43] | <mstenta[m]> | Should that do it? |
| [13:16:26] | <jgaehring[m]> | Hmm, it should |
| [13:24:45] | <mstenta[m]> | I'll try reinstalling |
| [13:25:37] | <mstenta[m]> | Oh neat I see the GPS permission request now |
| [13:25:57] | <jgaehring[m]> | Oh great! |
| [13:26:33] | <mstenta[m]> | Dang - still didn't work in the drawer |
| [13:56:40] | <dornawcox[m]> | Very cool to see new mobile interface! |
| [14:21:22] | <mstenta[m]> | jgaehring: I'm just getting caught up on some of the discussion with Angela re plantings/inputs/etc... |
| [14:21:46] | <mstenta[m]> | Inputs can be applied to any asset type |
| [14:21:48] | <jgaehring[m]> | oh great |
| [14:21:50] | <mstenta[m]> | And we shouldn't restrict that in the app |
| [14:22:06] | <jgaehring[m]> | and sorry i'm still stumped why the user info isn't showing up |
| [14:22:09] | <mstenta[m]> | Also: the "Equipment used" field will be added to all log types in farmOS |
| [14:22:32] | <mstenta[m]> | So that should also be available on Activities, Observations, and Harvests in the app |
| [14:22:44] | <mstenta[m]> | (As well as the Quantity field) |
| [14:23:18] | <mstenta[m]> | (That shouldn't affect dev time, I wouldn't think - because it means all log types work the same so you don't need to differentiate the fields on them) |
| [14:23:35] | <jgaehring[m]> | sure, that should be easy enough... easier than the alternative in fact |
| [14:23:38] | <jgaehring[m]> | exactly |
| [14:23:38] | <mstenta[m]> | I will follow up in the email thread, but wanted to clarify that with you first |
| [14:24:30] | <jgaehring[m]> | cool |
| [16:25:31] | * ligius has joined #farmos |
| [16:25:37] | * ligius has quit (Client Quit) |
| [16:26:06] | * lablab has joined #farmos |