QUESTION: Need an architectural solution:
How to organize UI and business logics(controller in terms of MVC) for this?
Should I use TPageControl for this?
Or may I use TPanel or TFrame preformatted for each case, to manipulate them with property "Visible" (Y/N)?
The DBMS will have D-MVC approach,
Where:
D - data stored in files or got from DB abstraction layer(for SQLite3)
M - internal representation of data regardless of storage
V - GUI for representation
Controller - like a dispatcher which will take data from source and deliver to UI.
There is a form for DMBS UI. there will be several representations (1:1, 1:n, N:M...)
In some cases same data will be shown in different form.
Actually:
GetInput: select specific representation AND check:
if (requested data allows this representation)
then (show specific form) and (parse with specific parser).
Should this be done as several objects with
parent: "DataPresenter"
child: DataPresenter_AsTable, DataPresenter_AsList, DataPresenter_AsText
Then each child object will know it's presentation components, data parcer and data converter to form.
Possibly another architecture:
DataPresenters(form and structure)
DataProviders (with parsers from txt, csv, xml files)