joshtronic/pickles
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'master' of github.com:joshtronic/pickles

Browse source
This commit is contained in:
Josh Sherman 2010-05-11 00:53:52 -04:00
commit 489edfd61d
1 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README
View file

@ -15,24 +15,24 @@ The whole point behind PHP with PICKLES was for me (Josh Sherman) to take
a decade of PHP experience and a dozen or so of my own websites (all
running on different but similar custom systems of my own design) and build
a new framework / rapid development system that would be flexible enough to
run all of my sites off of a single shared codebase. PICKLES runs in such a
run all of my sites off of a single shared code base. PICKLES runs in such a
way that the core files are completely separate from the site code it's
serving. So much so, that the core files should never really need to be
accessed after installation (unless you want to void your warranty and/or
make a global change to all of your sites), and each site you have running
will be nicely packaged in a directory all it's own. This keeps your sites
simple and tidy with no duplicated code for each site! In a site's
directory, models and modules (page logic) and templates are kept seperate
from eachother and everything is ran through a single entry point
directory, models and modules (page logic) and templates are kept separate
from each other and everything is ran through a single entry point
controller.
Okay, but why?
--------------
Now I know you're wondering, "why didn't you just use one of the
pre-existing and already established PHP frameworks that are out there?" I
preexisting and already established PHP frameworks that are out there?" I
do have a handful of reasons for that, but those are personal gripes based
on a limited number of experiences and I won't being going into detail
on a limited number of experiences and I won't be going into detail
about them. The main reason for developing my own framework is that I am,
and also have been, a very do it yourself type when it comes to coding, and
typically very proud of my coding accomplishments. Also, because all of the
@ -55,7 +55,7 @@ Get the facts!
so there's no point in forcing PICKLES into the MVC box for the sake of
it. PICKLES strives to provide a modular system for developing websites
while keeping the display elements separated from any database calls and
other logic. That isn't necessarily a bad thing, it just meants that
other logic. That isn't necessarily a bad thing, it just means that
PICKLES isn't all that trendy because it lacks a silly buzzword that's a
bit overused at this point.
@ -68,7 +68,7 @@ Get the facts!
* Included with PICKLES are shared CSS files (foundation classes and one to
do a full CSS reset) and shared JavaScript files with includes jQuery
(and some plugins / add-ons) and a core JavaScript file which includes
(and some plug-ins / add-ons) and a core JavaScript file which includes
automatic AJAXing of forms and some other niceties.
* Writing error free code is very important to me, so any PHP development I