Framework or not to Framework?

Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy.
This forum is not for asking programming related questions.

Moderator: General Moderators

Post Reply
encryption
Forum Newbie
Posts: 1
Joined: Mon Nov 28, 2011 4:45 pm

Framework or not to Framework?

Post by encryption »

Hello all,

I have seen the forum board name and think that this community will be great for support and feedback for my uni project.

I have been tasked to solve a problem, I want to sort a paper based system. What I mean is to create a paperless environment. And provide an electronic easy to use system and provide customers with access to logon an view certs and print them if needed, a "Request Formal Copy" button is also an idea.

I am new to PHP but am a quick learner. I have to create a calendar based system with an FTP .pdf GUI interface to download certs and other docs. Users should be able to do the following;

Change House theme / fonts
amend / add / remove - calendar events
FTP GUI download option
Secure HTTPS logon

What framework if any, should I base my project on.

Oh I have no problem ref resource I will use my dedicated server with WHM or rent with Hostgator.com

I hope this post follows forum rules, if it does not I apologize. Any help would be appreciated

Regards,

Neil
User avatar
Christopher
Site Administrator
Posts: 13596
Joined: Wed Aug 25, 2004 7:54 pm
Location: New York, NY, US

Re: Framework or not to Framework?

Post by Christopher »

Most frameworks will work for your project. I would recommend downloading several of them to see if you can get them to work and that they makes sense to you. One or two will probably stand out as a good fit for you.
(#10850)
User avatar
infolock
DevNet Resident
Posts: 1708
Joined: Wed Sep 25, 2002 7:47 pm

Re: Framework or not to Framework?

Post by infolock »

To choose a framework or not is all about personal preference - not so much about making a great product. Frameworks, for many, solve the problem of creating boiler plate code (code that they end up rewriting on every project they are involved with), and as such they want a more uniform way of solving the same problems on each project. Some also believe that by using a Framework, they are following the "standards" for a given language or community.

Whatever the case may be, choosing to use a Framework is kind of an important step. You either need to use that framework exclusively, or not include it at all. The reason behind this point is because of their sheer size - most are huge (such as Zend Framework). Choosing just to include it into your build and never use it is kind of like moving stuff from your Recycle to a sub folder - and just never touching the files in there. You also want to make a decision (to Framework, or not to Framework) because of code clarity. Switching between 2 or more different ways of handling the same solution is not good coding practices and can make your code hard to read and maintain (for yourself and anyone else).

If you choose *not* to use a Framework, then it is typically because you have your own way of doing things, don't really need much (if any) of the bells and whistles a framework provides or many other reasons.

This is all about PHP of course. Just my 2 cents.
Post Reply