CodeSnip Blog

Today I released an  update to CodeSnip  that makes two little changes: The marketing names have been removed from later Delphi versions (e.g. Athens & Rio) to save space in the UI if you have several versions of Delphi registered. So now instead of seeing Delphi 12 Athens you will see Delphi 12.x , for example. The built in REML markup language that can be used to format snippet descriptions and "Extra" text, now supports the ' character entity that gets replaced by a single quote when rendered. For the complete change log see here . Compiler name changes in v4.23.0 New REML character entity in v4.23.0

Yesterday, Delphi 12 was released as part of RAD Studio 12 "Athens" . Today there's an update to CodeSnip  that gives the option of using the new Delphi 12 to test compile your code snippets. It's really simple to configure CodeSnip to use Delphi 12. The first time you start CodeSnip after installing Delphi 12 a dialogue box will pop up and ask if you want to use the compiler alongside any other versions you may have: That will happen only if you haven't turned off the auto-register compiler option. If that's the case you'll need to use the Tools | Configure Compilers menu option to set it up yourself. The Detect Delphi Compilers button in the Configure Compilers dialogue box will do the trick: The only other user-facing change is that the list of compilers in the Configure Compilers and Find Compilers dialogue boxes is now sorted with the newest Delphi versions first instead of them being hidden down the bottom an increasingly long list. There's

CodeSnip v4.21.2 has been released today, 14th July 2023. This is a patch release that fixes a few minor bugs: Fixed some broken and "unsafe" (http) links in the about box. Fixed error in version information. Fixed potential XSS vulnerability in JQuery code used in the program's easter egg . Updated and clarified license & some other docs. Do you need this release? Depends on how much you're bothered about the above errors. Up to you. ⏬ Get the new release from the  v4.21.2 release page  on GitHub.

Back in December 2022 I was quite pleased with myself for releasing the v4.21.0 update to CodeSnip . The main feature that was added in v4.21.0 work fine - automatically detecting un-registered Delphi compilers at start up - worked fine. But, oh dear, the more obscure new feature that lets you use lists in snippet descriptions was a bit of a disaster. The main implementation of lists was a bit flaky, but the main problem is that I forgot to add the implementation of lists in snippets reports and in source code comments in generated units. This pretty much trashed the reports and comments. It's taken a lot of coding to fix these bugs, hence the 4 month delay before this bug fix materialised. But I think I've managed it, although whether the new feature was worth the effort is debatable. ⏬ Get the new release from the v4.21.1 release page on GitHub. Here's what a snippet looks like in the UI when it's description contains an unordered list: Here's how the same snippe

To close off the year, here's a new release of CodeSnip  that adds a couple of new features that have been in the pipeline for quite a while. The first is one I've been working on ever since a user missed out on getting Delphi 11.x Alexandria support when I added it. He expected CodeSnip to just use it when test compiling snippets. It didn't do that. I think his expectation was valid, so I decided to make CodeSnip a bit cleverer! Until now, when support for a new Delphi version was added to CodeSnip you would have to remember to tell it you wanted to use the new compiler, if you had it installed. Now, when CodeSnip starts it checks if there are any versions of Delphi on your system that are not registered with CodeSnip for use when test compiling snippets. If it finds any it offers to register them for you. This feature only works for any version of Delphi that CodeSnip knows about, which for the moment is all of them from Delphi 2 to Delphi 11.x Alexandria. This doesn'

Over 9 years I've had three attempts at creating CodeSnip 5. All have been very ambitious. The latest was CodeSnip Belvedere, rashly announced on new year's day this year. Now I never normally make new year's resolutions, and I should have stuck with that tradition! Of course Belvedere foundered - it was way too ambitious. Again. I was overwhelmed right from the start. Just look at the repo where there have been bugger all commits . So here's a new announcement I can stick by: Belvedere is dead, abandoned, gone. The idea to rebuild CodeSnip from the ground up was an attractive proposition, but it was way too much work. Right from the start I seemed to have an inkling I might have bitten off more than I could chew, because I even queried the wisdom of the new year's resolution in the announcement itself ! And that's what all the failed attempts to create the next release have in common: the plans for the new version were always too ambitious . Maybe I've le