janok wrote:
Hate to be the bearer of bad news, but this will never work. Aside from the costs of things like installation and support, on your own you might get a system that does what you want, but you will never make a usable by all system with varying options.
Plenty have tried, plenty have failed. They all, in the end, purchase a system from a system supplier whether it be autocab, cordic or mercury.
Stick to what you know.
Are you pointing at my skills as a programmer or are you saying a simple system like the one I made is useless? Can you be constructive when you give your opinion pls? For instance; identify points of failure and offer a possible solution for each. That is better than a general answer.
In retrospect. My small system currently works. I can write a module to auto dispatch. But I don't have that need atm. Most systems are made to solve every possible problem n therefore fail to solve the most basic of the problem. Those systems are made to be sold to operators/managers/accountants etc, but we all know the person who should be focused on is the driver not the office staff. That is just traditional software design.
You don't need 1000nds of configurations bulky never used features. I'm intending for a few useful buttons. 5 maximum: Add( vehicle, driver, licence, booking) and view live, completed and future bookings.
The dispatch is automated, to the longest wait in queu wherever they are, or the closest driver to a fare. Pls add some other scenarios here.
Drivers log themselves in, its up to them. Noo need to chase them around. Jobs are dispatched to logged in drivers only. And they can download and print their own documents in different formats. PDF, CSV etc.
This is what I have just done tonight. Anyone happy to test drive?