hope the debugger can be stronger! and if can open the library source, it's much better. I know most of the bug comes from application instead of the library,but if we can see the source(just like mfc in vc++),we can back-trace and figure out where the problem is in our code. Instead, in delphi/bcb, when some problem happen in the lib, what u can see is just some asm code and some label,this help u nothing. u need to guess what parameter or call order you passed to vcl is wrong.
我最需要的是VCL组件的版——本——向——下——兼——容——性——!!!
to 楼上: 是呀是呀是呀是呀是呀是呀是呀是呀是呀是呀是呀是呀(只见oldsword一个劲的点头,终于将脖子扭伤,不得不抬进医院急救,5555555555555)
2、FOR LIUNX;
3、改HELP;
4、使控件安装更简单;
5、加强DEMO
另外如果能把文档做得跟MICROSOFT一样,俺就开心多一点点了
还有调试器用起来像VC那么舒服
比如:
1.Delph生成的总是Unit1,Unit2,form1,form2.让人分不清谁是谁.而VC中的文件名是根据工程名字来定的.
2.Delphi新建一个工程时缺省总是在同一个目录下面.有时候一不小心或是顺手一敲回车,久而久之,Projects目录下面就有N个项目.而且说不定这个Project's Unit1就覆盖了那个Project's Unit1.反观VC没见一个工程,她会新建一个以工程名命名的目录.既不会于其他项目混淆,有一目了然.
3.Delphi的程序中调试信息去不干净,无论怎么设置Project Option.有一些调试工具调试Delphi的程序,就会发现一些调试信息.而这一点VC要表现的好得多.
2。好好加强帮助,中文化,组织好,免得用起来一头雾水。
还有,还有,要有一个与C++的类型对照列表
这样做api就方便多了(我最希望的)
delphi带的flatnet吧,哪个网络构件
非常不好用,老是停止响应最后希望delphi能做的更好
and if can open the library source, it's much better.
I know most of the bug comes from application instead of the library,but if we can see the source(just like mfc in vc++),we can back-trace and figure out where the problem is in our code. Instead, in delphi/bcb, when some problem happen in the lib, what u can see is just some asm code and some label,this help u nothing. u need to guess what parameter or call order you passed to vcl is wrong.
是呀是呀是呀是呀是呀是呀是呀是呀是呀是呀是呀是呀(只见oldsword一个劲的点头,终于将脖子扭伤,不得不抬进医院急救,5555555555555)
我最需要的是VCL组件的版——本——向——下——兼——容——性——!!!
你说的太对了。