Subtle things on naming conventions (:
Posted by jpluimers on 2013/11/26
Sometimes a naming convention has been in place for quite a while, then new functionality breaks it.
One of the naming conventions in the JVCL is that all Delphi design-time packages follow the naming pattern *Design##.bpl
Until a package with run-time design functionality came along named (for Delphi XE3) as JvRuntimeDesign170.bpl. The actual design-time package for that is JvRuntimeDesignDesign170.bpl (:
I guess some of the reporting tools bumped into the same thing when they added run-time design support as well.
–jeroen
The Wiert Corner - irregular stream of stuff 
Kmorwath said
Just because they didn’t adopt Delphi convention of using dcl* for design-time packages. As those who still put the Delphi version in the package name instead of using package options (thereby the .dcp file change its name with every version, making switching apps using run-time packages a tedious process of changing packages names).
Sometimes reinventing the wheel is not smart at all.
jpluimers said
Please enlighten me, as this seems to be a feature I have missed as well.
Hans said
Agreed on both accounts, the dcl prefix is the most commonly used way of letting people know its a design time package. JCL/JVCL is just one of the many thirdparty packages breaking that ;) There isn’t much interesting in in it anywhay (or at least i think its rather uninteresting)
jpluimers said
I think JCL/JVCL is still very relevant, but like most long running open source projects they are in need of fresh developers.