Php-spry framework-ajax-mysql

[psyche54]

---

Kinsa na nakasulay... we are planning to rebuild our system using the following framework above...

Kinsa naa vast experience using this one as a company tool (Accounting System, HRIS, etc.)

Currently we are on PHP-AJAX-MYSQL, and it seems ok naman with MPDF as our report output..

Your inputs are highly appreciated...

[maddox22]

Spry - pang visual presentation lang and i think wala sila'y ajax back-end support. but compared to other js libraries, mas smooth iya accordion, tabbed panels, and other widgets. so i use Spry for those things.

for ajax implementations i use a combination of Prototype and JQuery. I still use Prototype for basic ajax calls. I use JQuery for the (awesome!!!) plugins.

anyway, if you can use Java instead of PHP then mas maayo for an Accounting System and HRIS. Java for more intricate and accurate (money) calculations for your accounting system. Java for more accurate (employee related) date and time calculations for your HRIS.

Java also has very very good reporting tools: iReport, Jasper, Apache FOP. I've tried MPDF before, and I'm sorry to say but it sucks!!! it is very very limited in functionality and has very very scarce support.

although i'm not saying PHP sucks it's just that it depends more on the type of application you want to build. PHP is excellent for social networking sites like (pero dili sa backend ha) Facebook, Friendster, etc... for business applications like the ones mentioned above, it's much better to use J2EE or .Net

for business applications I would recommend:

database : mysql
persistence layer : hibernate
server-side : java
framework : spring
client-side : adobe flex
or
client-side : jsp, ajax (spry, prototype, jquery, mootools if you can manage prototype compatibility), struts tiles
security : owasp stinger
search engine : solr
reporting : jasper
pdf rendering : apache fop
caching : ehcache or memcached for larger systems
server : tomcat, jboss, or glassfish (depends on the complexity of your application e.g. only use EJB if really needed but if not then don't use it) for most applications that are not too complex, tomcat will do

[psyd_1]

^^ good picks

just to add, jasper can also render PDF's so you may save one from using fop

[psyche54]

Spry - pang visual presentation lang and i think wala sila'y ajax back-end support. but compared to other js libraries, mas smooth iya accordion, tabbed panels, and other widgets. so i use Spry for those things.

for ajax implementations i use a combination of Prototype and JQuery. I still use Prototype for basic ajax calls. I use JQuery for the (awesome!!!) plugins.

anyway, if you can use Java instead of PHP then mas maayo for an Accounting System and HRIS. Java for more intricate and accurate (money) calculations for your accounting system. Java for more accurate (employee related) date and time calculations for your HRIS.

Java also has very very good reporting tools: iReport, Jasper, Apache FOP. I've tried MPDF before, and I'm sorry to say but it sucks!!! it is very very limited in functionality and has very very scarce support.

although i'm not saying PHP sucks it's just that it depends more on the type of application you want to build. PHP is excellent for social networking sites like (pero dili sa backend ha) Facebook, Friendster, etc... for business applications like the ones mentioned above, it's much better to use J2EE or .Net

for business applications I would recommend:

database : mysql
persistence layer : hibernate
server-side : java
framework : spring
client-side : adobe flex
or
client-side : jsp, ajax (spry, prototype, jquery, mootools if you can manage prototype compatibility), struts tiles
security : owasp stinger
search engine : solr
reporting : jasper
pdf rendering : apache fop
caching : ehcache or memcached for larger systems
server : tomcat, jboss, or glassfish (depends on the complexity of your application e.g. only use EJB if really needed but if not then don't use it) for most applications that are not too complex, tomcat will do

very well said sir... thanks... Yeah actually pang visual ra jud namo ang spry and user end filtration sa data...

We haven't tried sa J2EE/Jasper combination pa... We might as well consider doing such approach... Actually ang problema namo with PDF reporting is if ang imong printer, non-postcript printer... Buang jud ang text niya kay I think iprint man sa printer ang PDF as image... Maguba ang text kung dot-matrix ang printer... Ok ra sa LaserJets... So right now, nag himo mi ug library, create and design report in text file, then pipe it to Line Printer Daemon sa linux, or by using "IPP" printing sa PHP para maka select ang user ug printer from the client side...

A brief snapshot sa amo under develop nga system...

[moodsey211]

Database: PostgreSQL - transaction-based database. Much more reliable than MySQL when it comes to concurrent transactions
Server Side: PHP
Framework: CodeIgniter

For reports you could use excel. On our system we use excel to download and display our reports. It's tested against 4000 Employee Self Service concurrent users.

The server side language and framework is depends on what you want to do. But for the database I suggest using PostgreSQL.