Modules are folders with functionality like Oracle fmb-s. This page is Mnu module home
Find Out More
See and explore what other people write. Hard work on learning is worth nothing if not explained & shared.
 |
 |
 |
 |
 |
01_DDL_mysql_blog.sql 01_DDL_oracle_blog.sql 01_DDL_moj_adrs_MINI3_mysql.sql |
|
Step
1.
Request
is
URL
adress
entered
by
user. Response is HTML from Home view. |
Step
2.
Config_allsites
(utl,
utilities)
is
reusable
(includ-able). Home_ctr class extends utl is "ctrl+c,v reusable" Home is view class, is "ctrl+c,v reusable". |
Step
3.1
Tbl_crud
is
module
DB
adapter class,
"ctrl+c,v
reusable
DAO". This code layer is Middle tier - business logic & objects. |
Step
3.2
Db_allsites
DB
adapter class
is
shared,
global
on
site
level,
common,
reusable
(includ-able)
Data
Acess
Object.
Implements
Db_allsites_Intf reusable (includ-able) DAO. |
How
works
R(ead)
of
cRud
: Router in Config_allsites called from Home_ctr returns user's commands (interactivity) decoded from URL request to Home_ctr which dispatches request (URL parameters) to own methods. Home_ctr's method call Home's method which reads table rows using DAO's (three classes in Step 3.) and display them - response is HTML from Home view. |
|
Data flow determines the structure (skeleton) of the program code.
 |
Image 2. Circular display of important functionalities, data and control flow and B12phpfw classesTbl_crud and Db_allsites classes have same named CRUD methods cc, rr, uu, dd. Tbl_crud contains also business methods (largest and most complicated code) which call CRUD methods. Tbl_crud and Db_allsites classes are independent thanks to Db_allsites_Intf list of atributes and methods. Persistant storage object variable is parameter (dependency injected property palete object $pp1) of Db_allsites CRUD methods. This means that cc, rr, uu, dd CRUD calls in Tbl_crud may access any persistant storage - MySQL, Oracle, OS texts... See https://github.com/nazonohito51/clean-architecture-sample - good picture, but for me to complicated code. |
1. SEES in picture means : C assigns variables from user request in URL
(from URL query) telling V what user wants and calls V method or includes V (not showed in picture).
2. UPDATES in picture means : V pulls data from M according C variables assigned in 1.
3. MANIPULATES means :
V (user request) may call C method for some state
changes ordered in URL by user (USES in picture).
Eg : table row update "Approve
user comment" in msg module. User`s events are so handled in Controller class.
View gets (singleton) or instantiates model object and pulls data from M. If we have user`s interactions (events) eg filter displayed rows (pagination is sort of filtering), than M-V data flow is only possible solution.
Controller instantiates M and pushes M data to V. I do not see advantages compared to M-V data flow. Disadvantage are : for pagination M-V data flow is only possible solution, C is fat in large modules (lot of code). C in my msg (blog) module has lot of code, but code is very simple.
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Voluptatibus provident...
ccccccc cccccccc
Todo / Done
ddddd ddddddd
ggggggg gggggggg
aa111 Lorem ipsum dolor sit amet, consectetur adipisicing elit. Voluptatibus provident sed mollitia, ...
ddd dddddddddd
hhhhhh hhhhhhh
Ready to start your next project with us? Send us a messages and we will get back to you as soon as possible!
L
Singleton
ALL HELP SW
aaaaaaaa aaaaaaa
/vendor/b12phpfw/img/
/vendor/b12phpfw/img/
![[project image]](/vendor/b12phpfw/img/mvc_M_C_V_data_flow_Laravel.jpg)
/vendor/b12phpfw/img/
![[project image]](/vendor/b12phpfw/img/mvc_M_V_data_flow_MVC_3tier_DAO_abstract_interface.jpg)
mvc_M_V_data_flow
![[project image]](assets/img/portfolio/fullsize/5.jpg)
Project Name
![[project image]](assets/img/portfolio/fullsize/6.jpg)
Project Name