Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am a PHP developer and I want to increase my knowledge. So I am trying to understand some online scripts. I see some folders named ( Zend, Symfony.. etc ) and I read about code igniter.
However, I still didn't understand anything of what I want to know.
What is and when to use each of them?
What are the features they provide?
With which should I start with?
Codeigniter, CakePHP, Laravel, Zend and Symfony frameworks
I know this may be a duplicate question but I really need a complete answer that I really did not find.
Thanks :)
I think that you should start from learning MVC pattern that is used in all of mentioned frameworks, if you're not already know what it is.
The next thing are requirements - what you need or what you expect from framework? There are some things that frameworks cannot do. You can check and compare what each framework can or cannot do for you. Note every part that you discovered.
Some frameworks are easy to start, others need advanced knowledge. Check the examples in docs.
Next step could be your own testing to code something.
This is really too general question, that was asked and answered many times not only here (at stackoverflow), but at many other websites too. Just add some important keywords and search. All in your hands.
They are php frameworks
https://laravel.com/docs/5.5
https://www.codeigniter.com/
Just google tutorials for (one of the frameworks) and work your way through them. There are plenty of resources out there.
I would start with codeigniter first since the learning curve is less steep
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I want to learn to create and modify php applications. I learned most of the common syntax by now and understand basic concepts like connecting to mysql and post and get http methods, but still not sure how to go about creating something complex like a full application with libraries and how it all connects together. I tried analyzing already existing apps and get really confused just by looking at codes that call on other files with many custom functions which are unreadable to my eyes. I hear about frameworks and about libraries, but I am pretty confused in this step of the way. What would be the concept I am missing to learn to make the leap towards creating complex applications. Any help will be appreciated.
There is always a lot to learn with php. It's a constant learning curve.
Some of the things that I can let you know.
Firstly make sure you follow best practices. There is always the temptation to cut corners, because php allows it.
Here is a guide to coding with php the right way which I found useful
http://www.phptherightway.com/
There are many php frameworks out there these days and choosing the right one that fits your needs is important. Some are more powerful or flexible than other, but some also have a steeper learning curve than others.
http://www.hongkiat.com/blog/best-php-frameworks/
Article that may help. Most of the frameworks will have a "how to" which will guide you through the process.
I personally use ZF2, but Laravel has gained a lot of popularity these days.
Also make sure you take a look at some of the places like tutsplus, project treehouse and other great learning resources.
Good luck, and I hope you make some amazing applications.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I'm new to PHP and am trying to more of an overview before I jump into the code sometime tomorrow.
What advantage does using a framework like CodeIgniter or CakePHP or Zend provide over using 'plain vanilla' PHP?
The framework takes care of the stuff that everyone's done a hundred times - authenticating users, talking to databases, handling file uploads, validating forms.
It saves you time, because you don't have to write it again.
It saves you headaches, because it's probably designed better than you would off the cuff and because it's already been thoroughly debugged.
It makes it easier to collaborate, because anyone who knows the framework has a step up on understanding your program.
It makes programming more fun, because you can focus on writing the interesting bits, not the slugwork.
Any framework has the advantage of solving problems that just about any programmer would encounter without using a framework.
There are many common problems that you and I would face regardless of whether or not we're building software for banking, media, news, etc, and instead of reinventing the wheel, you can springboard off of the hundreds and thousands of hours of developer experience by using code that has been tried and tested in a multitude of different production environments.
The motto is this: Don't reinvent the wheel. Your job is to meet a business goal, not solve problems that other people have already solved for you.
One advantage is: Design decisions are made for you.
One disadvantage is: Design decisions are made for you.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I'm planning on building a private API for a CodeIgniter web application I have. I've found a tutorial for that which shows me how to do it using pre-built libraries.
I'm very new to this so my questions is: shall I use and rely on these libraries? or shall I learn how to build it from scratch in order to have complete control over it? also, do you have any tips of someone like me who's just getting started with APIs?
Of course it's up to you but I would really suggest using my libraries. The code has already been tried and tested by several large public web-apps and I recently added in key management, logging and request throttling.
Months of coding has gone into those libraries and they have been used to death, so it will be way easier that writing your own.
Just have a look through the code as you go so you understand how everything works. It's pretty flexible and getting more flexible as it goes.
When I decided that I was going to write an API, I was still in the early stages of learning CodeIgnitor so I didn't use it for developing the API. I think even now, I would probably still go the route of writing it all myself and not use a framework. This is mainly because I like to keep things as slim as possible and I feel that is more likely to happen without using a framework.
To get me started, I found this tutorial to be really helpful.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I am not trying to create yet another web framework.
For one of the applications I am working on, I want to create a custom framework. I don't want to use any already available framework.
What are the common things to consider?
What should be the architecture?
Thanks :)
If the point of a framework is to make tedious things easy, a good start would be to consider what is tedious.
What are the common things to consider?
Purpose. Usually, when you start building a piece of software, you have a purpose in mind. What will it do that other programs can't?
If you can't answer that question, then take any existing open source framework, change its name and your job is done. Now you have your own framework.
Well if you are going to write a custom framework then I assume the framework needs to be tailored to your needs, otherwise you would use one that is already available. So figure out what your needs are and go from there ;)
What are the most often repeated operations in your application? Is there a division of labor that a framework could make more apparent?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Hi sorry if this is a naive question, but what did people do before mvc frameworks became so popular? All you hear of nowadays, and im talking php here, are mvc, Zend etc but what did developers do beforehand?
Are there some developers who use the mvc pattern but without a framework - if so how do they do this and is it really complicated to set up?
MVC is a design pattern. You can easily roll your own MVC "framework" (technically even without using object-oriented programming). The main goal is simply to have a separation between data storage, business logic, and presentation.
When I was first learning about MVC, I decided that trying to sift through the mountains of code of CakePHP or other frameworks was simply too complicated. I started writing my own "framework" using this tutorial (http://fuelyourcoding.com/php-frameworks-just-roll-your-own-part-1/). It's really not as much work as you think (you can go through that tutorial in a day and have a very nice mini-MVC), and you can expand it later into a full-fledged framework later on if you have the time and dedication.
As to the question of what developers did before frameworks, well, they just wrote everything themselves. Unfortunately this led to a lot of spaghetti code with HTML mixed with PHP blocks and SQL statements, but that's not really a fault with not having a framework, rather with not trying to implement any sort of separation of concerns.
Edit: Part 2 is probably the most important part because it shows you how to make a template. This isn't actually the exact tutorial, the one I used seems to have disappeared.