-
Notifications
You must be signed in to change notification settings - Fork 1
A0.02 Non navigation aware components (Xamarin)
chempkovsky edited this page Jul 21, 2021
·
1 revision
In articles 07 through 99, we described how to create the basic components for our database and have a fully functional application. Let's compare the folder structures for Book and Edition entities.
The folder structures are identical. This is because we created the same component sets for both entities.
-
eform is a component for Add, Update and Delete operation (it has three functional modes).
- eform knows how to send and receive data to and from the backend node.
- but eform has no UI to activate "save"-operation
-
edlg is a wrapper for the eform-component
- edlg is a dialog
- edlg has "Ok"/"Cancel"-buttons
- when OK is clicked, edlg sends a notification to eform to make validation and submit data to the backend.
-
sform is a tabular form
- sform knows how to send and receive data to and from the backend node for filtering and sorting
- sform has select one item functionality
-
sdlg is a wrapper for the sform-component
- sdlg is a dialog
- edlg has "Ok"/"Cancel"-buttons
- edlg is used by "SearchDialog" controls of eform component (last two slides of 66 article)
-
lform is a component that wraps eform and edlg
- lform is a tabular form with CRUD capability
-
ldlg is a wrapper for the lform-component
- ldlg is a dialog
- ldlg has "Ok"/"Cancel"-buttons as select one item implementation
-
Additional component.
- O2m component
- O2m is one-to-many tabular form
- O2m has no dialog wrapper
- CRUD capability can be turned on/off for master and detail table
- O2m component
All components mentioned above are non navigation aware. They know nothing about URL and routing.