PHP Intranet Reporting
Latest Source is Here
What is this thing anyway?
PHP Intranet Reporting is a means of keeping a journal based
on dates and times (calendar based)
Generally intended for status and reporting type events. The front end is
HTML
generated by PHP
, the backend is an Apache Web Server
running the PHP Module with PDFLib
and MySQL
support
compiled in running on Linux test box is
Red Hat 7.1*note most of the software components are compatible with other
Operating systems, there's no reason to believe that this wouldn't work on
other systems, but probably runs best on Linux :
Reports can be generated Dynamically in PDF format using PDFLib. *Please
read the PDFlib license before using PDFlib.
Future versions will most likely include alternatives document formats.
What do I do with it?
Whatever you want! Currently it's little more than an online notebook. Long before
I thought of adding the reporting piece that's what I used it for and it did quite
well in that role. Adding some reporting functionality means I don't have to type
a status report out every week while rifling through sticky notes and scattered bits of
paper. I'm appealing to all the slobs out there! Of which I'm an upstanding member
In a nutshell try it out. At the very least you'll have a nice place to keep your notes
I've had mixed reviews from my work. All seem to agree there's value here but like anything
there are the purists (it's not correct html or dhtml or css or whatever), and there are the
bells and whistles crowd (why can't it do my dishes). Somewhere in-between I'm working on
functionality first, layout and finally bells and whistles.
What do I need to run this?
- An apache Web Server with DSO turned on
- PHP 4.x compiled w/support for MySQL and PDFLib
- MySQL ver 3 and up.
- PDFLib (not sure what the latest is)
As for hardware: Well . . . I run just fine on a Pentium 3 400mhz at work
and a pentium 166mhz for development at home.
It's a web server with some pretty light duties for queries and calcs so
horsepower should not be an issue unless you've got a high ratio of clients
accessing the box.
What next?
First things first, while the software is very usable for me, there's much
to be done to make it something even close to a reasonable
release for the general public, hence the site you're reading now. I'm hoping
a few people will take an interest in helping me develop
this.
You can get the sourcecode Here
And for the visually dependant below are some screenshots.
|