|
|
|
 |
Why apps developed with MSFT tools have a poor UI I am part of a group that develops biz apps using Delphi. We have all the visual components that are de facto standard in Delphi community (Express Gris, Virtual TreeView, etc) and with them we wipe up apps that users just love.
Seemore
I think because creating components in Delphi is soooo much easier and better than in VB or VC++ there are many very advanced UI third party controls available. Also because developing these fancy third party grids/edits etc can be done many times faster in Delphi than ActiveX controls can be developed using VC++ (or VB if you want a crap result) they have more features and are more polished. These third party controls integrate much tighter with the delphi environment than alternative ActiveX style controls do in VB or VC++ the end result is a much nicer total package. Also adding third party controls to a project in Delphi does not have to be as painful as VB because there are no additional ActiveX controls or files that need to be distributed.
Craig
Outlook has one neat feature that no one ever seems to use. Open up a new appointment and in the date field type something like 'next monday' or 'next month'. It will figure out the actual date and enter it for you.
Interaction Architect
I find out look complex, confusing, and lacking many
son of parnas
Sorry, I have to disagree with you Seemore.
Wayne
One word: subclassing. In order to access most of the funcionality achieved by applications such as Outlook, using Microsoft tools you have to subclass some base class and add properties and methods for your own use. Delphi, on the other hand, have an event driven model that's much easier to extend, and is much more encapsulated (ie, you don't have to deal with queues, messages or other blunt objects.)
Leonardo Herrera
|
