Issue #18 has been updated by Raphaël Ouazana.
Hi, After manipulating some big configuration files, here are some thoughts about the new format: * the taskName should be highlighted in the configuration and/or the configuration file should be splittable * javascript should not really be an issue if: # it becomes possible to define functions (#182) # some helpers are added (ex. #226) # support for external javascript files is added (#182 too?) * the format should not be more verbose than the actual one Regards, Raphaël Ouazana. ---------------------------------------- Feature #18: Change the configuration format to something more adaptable http://tools.lsc-project.org/issues/18 Author: Jonathan Clarke Status: Feedback Priority: Normal Assigned to: Category: Core Target version: Sometime in the future XML? YAML? Think about it being parsed/written by a web interface. WIP : h2. XML : + Very easy to read/write for a computer + With CDATA we can write multiple lines JS - Very hard to read/write for a human h2. YAML : + Easy to read/write for a human/computer + Can write multiple lines JS h2. Properties : + Easy to read/write for a human/computer + Can reference other properties - Can not write multiple lines JS h2. NeXt/ Open Step configuration files See : http://commons.apache.org/configuration/apidocs/org/apache/commons/configuration/plist/PropertyListConfiguration.html + Easy to read/write for a human/computer - Can not write multiple lines JS -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
