{"id":21,"date":"2007-05-22T23:35:25","date_gmt":"2007-05-22T18:05:25","guid":{"rendered":"http:\/\/www.bin-co.com\/blog\/2007\/05\/iframe-features\/"},"modified":"2007-05-22T23:35:25","modified_gmt":"2007-05-22T18:05:25","slug":"iframe-features","status":"publish","type":"post","link":"https:\/\/www.bin-co.com\/blog\/2007\/05\/iframe-features\/","title":{"rendered":"iFrame Features"},"content":{"rendered":"

iFrame Logo<\/a><\/p>\n

In the previous post I introduced my new PHP framework – iFrame<\/a>. It had the reasons why you should not use the framework. In these post, I will talk of the advantages you get if you use my framework. But remember – do not use my framework.<\/p>\n

No routing – Fully file based<\/h2>\n

There are no complicated routing rules – the URL should specify which file should be used. For example…<\/p>\n

http:\/\/www.example.com\/user\/create.php<\/code><\/p>\n

Here, ‘user’ is the controller and ‘create’ is the action. <\/p>\n

Folder Structure<\/h2>\n

Like many other frameworks, iFrame has a rigid folder structure.<\/p>\n

\/\n+-common.php\n+-configuration.php\n+-\/includes\/  #System files\n+-index.php\n+-\/user\/\n\t+-index.php\n\t+-create.php<\/span>\n+-\/templates\/\n\t+-index.php\n\t+-\/user\/\n\t\t+-index.php\n\t\t+--create.php<\/span>\n+-\/js\/\n\t+-\/user\/\n\t\t+--create.js<\/span>\n+-\/css\/\n\t+-\/user\/\n\t\t+--create.css<\/span>\n<\/pre>\n
Auto inclusion of CSS\/JS files<\/h2>\n
The system will auto include the CSS\/JS files with the same file name as the current file – the files highlighted in the above ‘Folder Structure’ will be included automatically when ever the create.php file is called.<\/p>\n
Library for Paging\/Tagging<\/h2>\n
These two classes are great time savers. Unfortunatly they have no documentation – yet.<\/p>\n
Small\/Manageable Files<\/h2>\n
The framework forces the code to be broken down into smaller parts. In this framework, one action is one file – instead of one controller per file as in other frameworks. I find this easier to manage than the other approch.<\/p>\n
Uses OOPs only when it is required<\/h2>\n
I only use Object Oriented Programming only if there is a clear need to use it. This step made the system much simpler.<\/p>\n
Three Layers<\/h2>\n
This framework tries to follow both MVC(server side 3 layer) and Content\/Behavior\/Presentation(client side 3 layer) approaches.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the previous post I introduced my new PHP framework – iFrame. It had the reasons why you should not use the framework. In these […]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21,25,30],"tags":[111,119,143,144,210,245],"class_list":["post-21","post","type-post","status-publish","format-standard","hentry","category-php","category-scripts","category-web-development","tag-features","tag-framework","tag-iframe","tag-iis","tag-php","tag-script"],"_links":{"self":[{"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/posts\/21","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/comments?post=21"}],"version-history":[{"count":0,"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/posts\/21\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/media?parent=21"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/categories?post=21"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bin-co.com\/blog\/wp-json\/wp\/v2\/tags?post=21"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}