On 2 May 2017 at 18:15, Ulises <[email protected]> wrote: > Perhaps YAML isn't the format? I know next to no Lua and I'd personally > welcome being able to configure PM using a 3rd party format.
Have a look at the current format: https://github.com/apache/incubator-ponymail/blob/master/tools/setup.py#L496 The above config.lua generation code ends at line 525 currently. This could be enhanced with some more docs, but I think it's readily understandable without needing to know Lua. > Having said this I also acknowledge that having config as code is good in > that you get compilation/interpreter errors if you made a mistake which is > very nice. Indeed. > On Tue, May 2, 2017, 09:59 sebb <[email protected]> wrote: > >> On 2 May 2017 at 13:10, Shane Curcuru <[email protected]> wrote: >> > Daniel Gruno wrote on 5/1/17 1:35 PM: >> >> While having a cup of coffee on the balcony, I got to thinking - would >> >> it make sense for us to convert the PM UI configuration to yaml instead >> >> of a .lua file? It should make it less arcane to edit for non-techies. >> > >> > +1. The older I get, the more and more I appreciate systems that store >> > config data in very clear and easy to process formats. Being able to >> > change behaviors - or use automated deployment tools - without having to >> > look into code files is definitely helpful. >> >> I contend that the existing format is already pretty simple and easy >> to understand. >> >> It's not much different from a properties file. >> >> Whilst YAML has the concept of a hierarchical structure, it's pretty >> easy to get the layout wrong, but still end up with valid YAML. >> Unless the code that processes the file does some careful checking, it >> may result in unexpected settings. >> >> > Separately, is there any timeline for UI/theme work in the future? >> > >> > >> > -- >> > >> > - Shane >> > https://www.apache.org/foundation/marks/resources >>
