id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5407	Make the input of array parameters a humane experience	Francesco Casella	Adeel Asghar	"Currently, the input of array parameters in OMEdit is a rather inhumane experience, particularly for beginners:
- it is not at all clear if the parameter is a scalar, an array, or an  N-dimensional array, one has to guess or to look at the source code or at the documentation to find that out
- there is no (obvious) way to use {{{each}}}
- if a literal value is to be input, one has to get the syntax right
- even for advanced users, you may spend 10 solid minutes typing in
  an elaborate literal array expression, hit return, and discover you
  just lost ''all'' your work because of a stupid syntax error, e.g.
  {{{
[3] 19:35:48 Scripting Error
Unable to set the component modifier value using command
setComponentModifierValue(
 BasicAeroEngines.Tests.TestTurboJet, fuelFlow.table, $Code(=[0, 0.4;]))
}}}

I would strongly suggest that we improve the end user experience on this front, at least in these directions:
- include some hint in the parameter window so as to the dimension 
  of array parameters
- allow to use {{{each}}} from the GUI (mandatory with the NF)
- add a GUI for one- and two-dimensional array input
- check for the syntax validity before closing the input window,
  and in case of error give some error message but do not discard the
  wrong input, rather keep it available for correction"	defect	new	blocker	2.0.0	OMEdit