1. We have 4 full-time Delphi VCL staff at fabsoftware (www.fabsoftware.com). I am an owner/director/employee.
2. We develop our own non-visual and visual components to talk to our own web-server backend built on PHP, as well as a lot of drop and integrate. We use interfaces extensively similar to the IDE.
3.Since version 1
4. <ADV> (please forgive me or skip) Very recently, when I realised we had developed a system that could be of use to other Delphi dev companies. If you have legacy Delphi code, would like to make it web enabled / db independent / 2-way synchronisable using BPL's and an open API, without throwing it away and going to J2EE or .Net, we have a solution and a fully integrated CRM to boot. (see www.fortecrm.com)</ADV>
5. It depends. If Borland keep up with the delphi compiler and offer 64 bit and there is a component market, we will take the least change approach. We only use Delphi for the application Client, but there is a lot of great functionality there. We are taking a wait and see approach, as our app has a lot of life in it yet, win32 should run for ages, we would like to get the ideal of cross platform at the client without users sacrificing look and feel, and there is still a way to go with Java client, Kylix (to say the least), Lazarus, Mono, and .Net. MS are pulling back somewhat on .Net everywhere (at least in Longhorn) so I think that boat can be caught at our leisure, depending upon the component writers.
Cheers,
Jonathan Hull
FAB Software Ltd
_______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
