{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 孤傲高冷的网名 的问题《Question about MVC folder structure》','https://www.manongdao.com/q-992633.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
To use the MVC pattern/layout structure, does it basicly require everything to be loaded through 1 file, like your index file?
相关问题
- Views base64 encoded blob in HTML with PHP
- Laravel Option Select - Default Issue
- PHP Recursively File Folder Scan Sorted by Modific
- Can php detect if javascript is on or not?
- Using similar_text and strpos together
No. The MVC pattern only dictates a separation of concerns regarding event/request handling, data modelling and user interface. The way this is implemented is not specified.
Many (all?) of the current PHP frameworks I am aware of do use a single entry point (index.php) and route from there. This often makes use of the "Front Controller" pattern.
The other method (using a separate PHP file per page) is known as the Page Controller pattern. It has the advantage of being much simpler, but loses the application wide control afforded by the front controller and may be prone to code duplication.
No. Nothing about the MVC pattern in and of itself says anything about how your files or folders should be arranged. A given framework that you use might mandate a particular arrangement, however.