search

radical-cybertools / radical.owms

Tiered Resource OverlaY
Other
0 stars 1 forks source link

plugin naming consistency #39

Closed andre-merzky closed 10 years ago

andre-merzky commented 10 years ago

Troy uses short and long names for plugins, depending on context. As config system will now switch to a hierarchical system, the long names can be phased out.

mturilli commented 10 years ago

Not for the end user config files please.

On Mon, Feb 3, 2014 at 11:48 AM, Andre Merzky notifications@github.comwrote:

Troy uses short and long names for plugins, depending on context. As config system will now switch to a hierarchical system, the long names can be phased out.

Reply to this email directly or view it on GitHubhttps://github.com/saga-project/troy/issues/39 .

Dr Matteo Turilli Department of Electrical and Computer Engineering Rutgers University

andre-merzky commented 10 years ago

Why not? That is more pythonesqe, easier to structure, and the hierarchy reflects better what it is which is configured...

mturilli commented 10 years ago

Following a chat on IRC, happy to go for JSON for all the configuration with our home-made, super-duper parser.

On Mon, Feb 3, 2014 at 12:04 PM, Matteo Turilli matteo.turilli@gmail.comwrote:

Not for the end user config files please.

On Mon, Feb 3, 2014 at 11:48 AM, Andre Merzky notifications@github.comwrote:

Troy uses short and long names for plugins, depending on context. As config system will now switch to a hierarchical system, the long names can be phased out.

Reply to this email directly or view it on GitHubhttps://github.com/saga-project/troy/issues/39 .

Dr Matteo Turilli Department of Electrical and Computer Engineering Rutgers University

Dr Matteo Turilli Department of Electrical and Computer Engineering Rutgers University

andre-merzky commented 10 years ago

This has been addressed.