Re: [PHP] Web application design considerations - a good reference ?

2009-06-03 Thread AngeloZanetti
Tony Marston wrote: If you are building a business application with PHP rather than an ordinary website then I suggest that you use a framework instead of trying to reinvent the wheel (and making a hash of it). The Radicore framework was specifically designed for CRUD applications -

Re: [PHP] Web application design considerations - a good reference ?

2009-06-02 Thread mrfroasty
I am on the same position, half a year ago I tried to wrote the PHP application (sake of learning) using from scratch approaches. Now I want to have a production application, I am bussy to start over and writting/intergrating everthing using a framework. I think for my case is Joomla... So I think

RE: [PHP] Web application design considerations - a good reference ?

2009-06-02 Thread bruce
hi angus... You're probably going to get a lot of different approaches to this one! as a long term/time developer in a past life.. In my humble opinion, a reasonable approach is to start by laying out the key things that the app has to accomplish, and then to break this down into a list/sublist

Re: [PHP] Web application design considerations - a good reference ?

2009-06-02 Thread Paul M Foster
On Tue, Jun 02, 2009 at 02:50:36PM +1000, Angus Mann wrote: Hi all. I'm working on a PHP project for my own personal business use. It will handle billing and invoices as well as payments and time management, bookings, appointments and a few more. I may add things like personal messaging

Re: [PHP] Web application design considerations - a good reference ?

2009-06-02 Thread Lists
Angus Mann wrote: Hi all. I'm working on a PHP project for my own personal business use. It will handle billing and invoices as well as payments and time management, bookings, appointments and a few more. I may add things like personal messaging between the various users and a customer login

Re: [PHP] Web application design considerations - a good reference ?

2009-06-02 Thread Sancar Saran
On Tuesday 02 June 2009 07:50:36 am Angus Mann wrote: Hi all. I'm working on a PHP project for my own personal business use. It will handle billing and invoices as well as payments and time management, bookings, appointments and a few more. I may add things like personal messaging between

Re: [PHP] Web application design considerations - a good reference?

2009-06-02 Thread Tony Marston
Paul M Foster pa...@quillandmouse.com wrote in message news:20090602134327.gk14...@quillandmouse.com... On Tue, Jun 02, 2009 at 02:50:36PM +1000, Angus Mann wrote: Hi all. I'm working on a PHP project for my own personal business use. It will handle billing and invoices as well as payments

Re: [PHP] Web application design considerations - a good reference ?

2009-06-02 Thread Eddie Drapkin
My suggestion to you is probably mosty a rehashing of what a lot of other people have said. I definitely think you should take a good, hard look at some existing solutions (frameworks, cms's, etc.) and decide whether you want to use one or not. In my experience, which is admittedly limited,

Re: [PHP] Web application design considerations - a good reference?

2009-06-02 Thread Paul M Foster
On Tue, Jun 02, 2009 at 03:49:03PM +0100, Tony Marston wrote: Paul M Foster pa...@quillandmouse.com wrote in message news:20090602134327.gk14...@quillandmouse.com... On Tue, Jun 02, 2009 at 02:50:36PM +1000, Angus Mann wrote: snip I would advise against this as hidden fields in forms

Re: [PHP] Web application design considerations - a good reference?

2009-06-02 Thread Michael A. Peters
Tony Marston wrote: Let me expand on that. When you have a form (which is what most of your application will be composed of), it will return all the data you need to process it. You process it, and proceed to a menu or somesuch to tackle the next task. If, for some reason, you need to track

Re: [PHP] Web application design considerations - a good reference ?

2009-06-01 Thread Larry Garfield
Do not under any circumstances try to do this from scratch. :-) Use an existing framework like Zend Framework or CakePHP or a CMS/framework hybrid like Drupal or a dedicated app for billing and processing. It will save you months of work, and countless security holes. Even if you don't use