Yesterday I heard something intriguing, a colleague who works for a large company in Brazil, is removing the DevExpress components from the systems, because it do not support VCL themes.
Not sure about the latest version, but this has been true at least 2 years ago and they had no plans for supporting VCL Styles in the near future. BTW, the same is true for most TMS components.
My impression has been that DevExpress is in VCL mostly as a matter of inertia, and that they are not committed to much in the way of new development.
Before anyone decides to scream, not that I did say it has been my impression. I have no more objective data for that than for new license sales on Delphi.
DevExpress implemented their own Skin/LookAndFeel support long ago and use it throughout all the suite, why would they be interested in adding support for a parallel implementation?
Alexander Elagin Because the DevExpress Skin doesn't support other 3rd party components. Even if a component library implements its own system, it should at least provide a kludge to connect the VCL themes. Otherwise you might have to deal with several different systems. The VCL Styles consist of bitmaps and colors. Even if they don't support the bitmaps they could at least take the colors.
Uwe Raabe In Xe2 time there was a post from DevExpress about the VCL-Skins. They don't want to support it because of the quality. It can be the quality have changed, but I think it was the right decision then. If I see how long it goes for nearly every new part from Embarcadero until it is usable I can understand. And to Bill Meyer there are a lot of really good new components from DevExpress for VCL, to name some: Richtext with *.docx, *.doc, Exell Grid *.xlsx, *.xls and the last new the PDF Viewer. For me it is always the better joice to use the DevExpress Components. The Quality is very good, and that is something I can not say about the Embarcadero Components
Friedrich Westermann There is also this ticket: devexpress.com - Q359279 - VCL Styles with DevExpress Components | DevExpress Support Center . Uwe Raabe I must admit I never needed any other 3rd party visual component in addition to DevExpress suite (save TeeChart Pro for charting and FastReport Pro for reporting) because their set of controls covers virtually everything imaginable, and most of my work is with Delphi XE which does not have VCL styles while DX have skins ready at hand. YMMV.
Friedrich Westermann Happily there are more alternatives to the Embarcadero components than just DevExpress. I don't see perfect solutions from anyone, but my comment was based on my own perception that DevExpress appears more focused on the .NET side than on VCL. And I am not suggesting that is wrong for them -- it is a business decision, after all.
DevExpress is very expensive. They will not support FMX. So VCL is there for now but they have the entire company gearing towards .NET which most likely makes alot of money for them.
You really cannot blame them for their business plan but as a buyer i would not purchase their components for the fear of them dropping support in the near future.
Friedrich Westermann Not to forget DevExpress' very good support and great collection of Q&A and knowledge base. I was very disappointed when changing job to see not using the DevExpress components in the new company. I miss them a lot.
StyleControls VCL (www.almdev.com) includes special unit to use VCL Styles for DevExpress controls. But only for control, which has LookAndFeel property. Just add scDevExStyleAdapter unit to the StyleControls package, recompile it and set LookAndFeel.Skin property to "VCL Style" in DexEx controls. At this moment 16.X version is supported. 17.X coming soon, we hope. Main problem is that DevExpress not likes contacts with other vendors.
While it is true that DevExpress VCL may appear stagnated to the casual viewer, the truth is that they have added lots of very exciting components to their suite.
Their spreadsheet alone is worth the subscription price!
Not sure about the latest version, but this has been true at least 2 years ago and they had no plans for supporting VCL Styles in the near future.
ReplyDeleteBTW, the same is true for most TMS components.
My impression has been that DevExpress is in VCL mostly as a matter of inertia, and that they are not committed to much in the way of new development.
ReplyDeleteBefore anyone decides to scream, not that I did say it has been my impression. I have no more objective data for that than for new license sales on Delphi.
DevExpress implemented their own Skin/LookAndFeel support long ago and use it throughout all the suite, why would they be interested in adding support for a parallel implementation?
ReplyDeleteAlexander Elagin Because the DevExpress Skin doesn't support other 3rd party components.
ReplyDeleteEven if a component library implements its own system, it should at least provide a kludge to connect the VCL themes. Otherwise you might have to deal with several different systems.
The VCL Styles consist of bitmaps and colors. Even if they don't support the bitmaps they could at least take the colors.
Uwe Raabe In Xe2 time there was a post from DevExpress about the VCL-Skins. They don't want to support it because of the quality. It can be the quality have changed, but I think it was the right decision then. If I see how long it goes for nearly every new part from Embarcadero until it is usable I can understand. And to Bill Meyer there are a lot of really good new components from DevExpress for VCL, to name some: Richtext with *.docx, *.doc, Exell Grid *.xlsx, *.xls and the last new the PDF Viewer. For me it is always the better joice to use the DevExpress Components. The Quality is very good, and that is something I can not say about the Embarcadero Components
ReplyDeleteFriedrich Westermann There is also this ticket: devexpress.com - Q359279 - VCL Styles with DevExpress Components | DevExpress Support Center .
ReplyDeleteUwe Raabe I must admit I never needed any other 3rd party visual component in addition to DevExpress suite (save TeeChart Pro for charting and FastReport Pro for reporting) because their set of controls covers virtually everything imaginable, and most of my work is with Delphi XE which does not have VCL styles while DX have skins ready at hand. YMMV.
Friedrich Westermann Happily there are more alternatives to the Embarcadero components than just DevExpress. I don't see perfect solutions from anyone, but my comment was based on my own perception that DevExpress appears more focused on the .NET side than on VCL. And I am not suggesting that is wrong for them -- it is a business decision, after all.
ReplyDeleteDevExpress is very expensive. They will not support FMX. So VCL is there for now but they have the entire company gearing towards .NET which most likely makes alot of money for them.
ReplyDeleteYou really cannot blame them for their business plan but as a buyer i would not purchase their components for the fear of them dropping support in the near future.
Friedrich Westermann Not to forget DevExpress' very good support and great collection of Q&A and knowledge base.
ReplyDeleteI was very disappointed when changing job to see not using the DevExpress components in the new company. I miss them a lot.
StyleControls VCL (www.almdev.com) includes special unit to use VCL Styles for DevExpress controls. But only for control, which has LookAndFeel property. Just add scDevExStyleAdapter unit to the StyleControls package, recompile it and set LookAndFeel.Skin property to "VCL Style" in DexEx controls. At this moment 16.X version is supported. 17.X coming soon, we hope. Main problem is that DevExpress not likes contacts with other vendors.
ReplyDeleteDemo:
http://www.almdev.com/prods/stylecontrols/files/devexvclstyle.zip
https://plus.google.com/photos/...
While it is true that DevExpress VCL may appear stagnated to the casual viewer, the truth is that they have added lots of very exciting components to their suite.
ReplyDeleteTheir spreadsheet alone is worth the subscription price!