| [22:25:17] | * JustTB has joined #farmos |
| [22:36:27] | * JustTB has quit (Quit: Leaving.) |
| [22:48:29] | * JustTB has joined #farmos |
| [23:13:23] | * JustTB has quit (Ping timeout: 245 seconds) |
| [23:29:12] | * JustTB has joined #farmos |
| [06:57:50] | * JustTB has quit (Quit: Leaving.) |
| [10:58:49] | * JustTB has joined #farmos |
| [14:00:02] | <mstenta[m]> | jgaehring: Just a thought regarding the idea of moving "quick forms" into the client... we do still get some nice bonuses using Drupal forms, like language translations, accessibility, non-JS browser support, etc. |
| [14:00:12] | <mstenta[m]> | They don't work offline. |
| [14:00:40] | <mstenta[m]> | But maybe we can think of some creating solutions... |
| [15:15:02] | * JustTB has quit (Ping timeout: 250 seconds) |
| [15:17:31] | <jgaehring[m]> | well, perhaps field modules will be their own thing... like quick forms, but not replacing them |
| [15:18:07] | <mstenta[m]> | yea true - it will probably become more clear as use-cases arise |
| [15:18:34] | <mstenta[m]> | i wonder if we could do something where we define a form with JSON, and then have some code in JS and PHP to translate it into an actual form in either context |
| [15:19:09] | <jgaehring[m]> | oh interesting |
| [15:19:33] | <mstenta[m]> | that could get really complicated really quick tho... |
| [15:19:40] | <mstenta[m]> | so maybe not worth it |
| [15:20:21] | <jgaehring[m]> | hm, maybe |
| [15:30:07] | * JustTB has joined #farmos |