使用Delphi数据感知组件-优点和缺点 [英] Using Delphi data-aware components - pros and cons

问题描述

我想知道您对在项目中使用数据感知组件的看法.通过使用Delphi和数据感知组件(来自Delphi的标准套件或第三方)来开发应用程序(Win32和Web)的优势"和弱点"是什么?

I want to know your opinion about using data-aware components in projects. Which are the 'strength' and 'weak' points of developing applications(win32 and web), by using Delphi and data-aware components(from Delphi's standard suite or third-party)?

使用FireBird，我在IBObjects上做了很多工作，IBObjects是一套成熟的组件，并且工作得很好.

Using FireBird I've worked a lot with IBObjects, which are a mature suite of components and worked very well.

但是还有很多其他RDBMS(MySQL，MSSQL，DB2，Oracle，SQLite，Nexus，Paradox，Interbase，FireBird等).如果您开发了大型项目，并且在这些项目上使用了很多数据感知组件，请回答数据库类型和数据感知组件套件名称.

But there are also a lot of other RDBMS (MySQL, MSSQL, DB2, Oracle, SQLite, Nexus, Paradox, Interbase, FireBird etc). If you have developed big projects, on which you've used a lot data-aware components please answer with the database type and data-aware components suite name.

我也对DB2(AS400)感兴趣.您成功使用了哪些组件，或者使用哪些组件确实很痛苦?

I'm also interested on DB2 (AS400). What components have you used with success, or which components are really a pain to work with?

推荐答案

我发现使用数据感知组件可以使应用程序在业务逻辑和UI逻辑之间没有明显的区别.

I've found that using the data-aware components results in an application with no clear distinction between business and UI logic.

这对于小型项目很好，但是随着它们的增大，代码变得越来越难以维护.

This is fine for small projects but as they grow larger the code becomes less and less maintainable.

事件代码的所有各个方面(及其交互)都可能成为理解的噩梦！

All the various bits of event code (and their interactions) can become a real nightmare to understand!

在这种情况下，我总是放弃了数据感知组件，并改用了(手动编码)MVC设计.

Invariably in such cases I've ditched data-aware components and have switched to a (hand-coded) MVC design.

这确实需要大量的前期编码工作，但是在可维护，可扩展和可调试的项目中会产生(IMHO).

This does require a lot of up-front coding effort but results (IMHO) in a project that is maintainable, extensible and debuggable.

这篇关于使用Delphi数据感知组件-优点和缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！