Solver and plot configuration data structure design discussion

[j8xixo12]

Thanks @yungyuc to point out in #391 (comment) that the way to access data of SolverConfig and PlotConfig is too wordy.

For exmaple:

modmesh/modmesh/app/euler1d.py

Line 507 in 6e634cd

ncoord=self.solver_config.get_var("ncoord", "value"),

modmesh/modmesh/app/euler1d.py

Line 511 in 6e634cd

self.interval = self.solver_config.get_var("timer_interval", "value")

I would like to share my thought of this.
There are some items about this data structure of configuration data:

1. Because of our solver and plot configuration is using QtTableView and it's data model is QtAbstractTableModel. the QtTableView use index-base way to access it's data, for example: foo[0][1]
2. For user's perspective, the configuration table has row and column name, using string way to access data is more intuitive, for example : foo['var1']['value']

Based on these requirements I think the configuration class should has the following api :

• _ _ getitem _ _ and _ _ setitem _ _ : should support access data by index and string

[yungyuc]

Thanks, @j8xixo12 . If it is doable to enhance to use __getitem__ and __setitem__ for index and string data access, how much effort it will take?

[j8xixo12]

I think it would take me about 2 hours to implement and test it.
I plan to file a PR in this week.

[yungyuc]

If it's just a couple of hours, please go ahead. It will be efficient to directly discuss in the PR.