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?
Related
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
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 7 years ago.
Improve this question
I want to build a web-application using the php, I have started with CodeIgniter and Smarty. The issue is I came to know opinion about this combination like "framework in 2015?, like a joke", there are so many framework and all the updated and and many more thing like socket and node.js and all which make me so confusing.
I know many thing have there own need and work all the way, but I want to develop a site which will expecting 1-5 million hit monthly and I want it fast and efficient, using core php need to do more work which a good framework can do for you but still not sure what's the best approach to go from here.
Any top PHP framework like Laravel or Symfony can handle websites with so much traffic. If you want to create an API based on PHP and leave front-end to another app like Angular, you may also take a look a Lumen or Slim Framework.
I know it's a broad question but answer is simple, these frameworks give you the tools, as long as you follow modern principles and use caching they will be able to serve that many requests.
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
So I am new to unit testing. I'm through a book and couple of tutorials but I still have some doubts about the exact proper implementation.
I am searching for a well written unit test, because the sample examples that are based on the relationship of 2 or 3 classes cannot answer my remaining questions. I'd like to see some real world scenarios of proper coding that ensure long-term maintainability. The bigger the project the better. Does somebody have a well written test, or does somebody know a well written test that's available somewhere on the web? Thanks for help!
You may use Github to browse sources of various popular open source projects like Joomla.
Here is the link to Joomla CMS https://github.com/joomla/joomla-cms and here is the link to Joomla Framework https://github.com/joomla/joomla-framework.
Mentioned Joomla because it is my favorite; especially Joomla Framework. You may also try others like CakePHP, Code Igniter etc.
Just browse through most of well known open source projects on Github.
Doctrine
Zend
PHPExcel
To name but a few.
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.