Ticket T1081876
Visible to All Users

Regular updates and new features?

created 3 years ago

I am currently wondering more and more why there is no regular update for DevExpress VCL? In addition, it can be said in comparison to .NET, that the implementation of new features is sluggish to hardly present. Also the FMX version has not been updated for some time. Is there any insider information here as to why VCL is treated so second, third rate or worse?

Maybe there is a good reason for this, since the next update will finally include a lot of new features, and that's why there hasn't been an update for almost two months. If not in the current update, what new "modern features" can we expect in the "near" future?

Show previous comments (1)
Y Y
Yusuf Zorlu | MicrotronX 3 years ago

    +1

    NP NP
    Nicolas Prévot 3 years ago

      +1

      AB AB
      Andreas Bornemann 3 years ago

        main developer in russia ?

        Answers approved by DevExpress Support

        created 3 years ago

        As you probably know, we released our first VCL product in November 1998 (the ExpressGrid v1). By early 2001, we had released 3 major versions of our flagship VCL product. Once Inprise/Borland released Kylix (2001), we rewrote our Grid from the ground up (yes, from ground up). The hope (and hype) was that Linux represented the next frontier. We learned quite quickly that this was not the case. We may have sold a total of 2 licenses for the Kylix (CLX) version of our data grid.

        Allow me to make this point even clearer: The most successful VCL component in the VCL marketplace at the time was the ExpressQuantumGrid v3. In 2001, we ditched significant portions of its codebase and rewrote our Grid for CLX/Kylix/X-platform development. Purchases aside (again, total of 2 CLX licenses sold), our customers were furious - They did not like QuantumGrid 4. The initial release suffered from performance issues (and missing features). No one understood our logic and no one was happy.

        I mention these past events/realities to communicate our position as it relates to FMX. The problem is not necessarily FMX itself or the development complexities associated with cross-platform UI controls. The fact is that we worked on an FMX Grid and made it available to our customers free of charge. We did our best in this regard. In his December 3, 2020 blog post, Julian explained why we chose to abandon FMX development.

        Julian correctly noted that our failure with FMX may have been self-inflicted (the "chicken or egg" debate). Had we created a complete product line - one that mirrored/mimicked its VCL counterpart - the marketplace may have rushed to our door and purchased our FMX libraries. This could have happened, but we will never know. From where I stand, the problem was not the chicken or the egg - the problem was that we were in no position to build a complete FMX product line. Julian's post documents some of the challenges we encountered during our FMX development journey. And as the saying goes…"once-bitten, twice-shy." I lived through Kylix/CLX and I don't want to experience that again.

        Nearly twenty years ago, I got myself in a lot of hot water with Inprise/Borland for arguing that Visual Basic 4 was "better" than Delphi 2/3. I made this statement not because VB 4 was better than Delphi technically. It was not. My point was that VB dominated the marketplace. When we began .NET development in 2000, we did so because of market share/market potential. After 20+ years, nothing has really changed in this respect. Market size drives business investment.

        As far as "modern" features are concerned, I'm happy to discuss this with you - You can always reach out via email (rayn@devexpress.com). Obviously, I cannot do what I opted to do in 2000/2001. Internal debates at the time involved CLX and QuantumGrid v3's code. We ultimately made the decision to address two issues - deliver a cross platform product and eliminate reliance on the TreeList codebase. We did it - and we paid a pretty heavy price.

          Show previous comments (13)
          CM CM
          Charalampos Michael 3 years ago

            if CrossVCL succeeds we don't need fmx! Maybe DevExpress can get or support their engine in the future.
            Or better embarcadero buys CrossVCL … But i prefer WASM controls in the future from DevExpress.

              As far as wasm goes, I don't think it's fair/practical/reasonable to expect a product from DevExpress that has any tie to Delphi/C++Builder/VCL!

              CM CM
              Charalampos Michael 3 years ago

                WASM was on the delphi roadmap under considerations …

                Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

                Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.