Make it generic enough and you can re-purpose it into a component suitable for reuse in your other applications or even better release it to the general public so they make use of it in their applications.Ĭhoose a framework which lets you extend the framework easily and with minimal fuss. While a framework covers all of the important bases of an application, chances are, you'll still have to write a bunch of code. People like these loosely coupled frameworks just as much as the frameworks which are tightly couple with respect to its core components. It lets you switch out almost all of its parts starting from the ORM right down to its templating language. An excellent example of this would be Pylons. In other words, it lets you swap out parts of the library with another part of your choice. In these cases, you'll need to make sure the framework in question has only the features you need.Ī current trend among frameworks is that they are created as a library of libraries. A lot of people prefer frameworks to handle the bare minimum whilst letting the developer handle the rest. Of course, not every one needs a framework brimming with features. Most frameworks offer libraries which cover almost all of the following list: The library must be in such as that it frees you from writing repetitive code but still provides a way for you to tinker with it if you need more control or features. Let's face it it is for the core library that most people adopt a framework.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |