Change Of Heart

-

A couple of days ago, over on DelpDabbler's Blog, I announced that DelphiDabbler.com is no longer to close down.

The site is more than likely to be moving to a new host. Even if that falls through the site will relocate to GitHub.

So what does this mean for CodeSnip?

Well, alongside my decision to keep DelphiDabbler.com running I've also decided to update CodeSnip at long last - work is well underway on the new release - expected to be v4.16.0.

I'm still planning to make some of the changes I announced in January, but other things have changed. Here's what's happening now:

Firstly, here's the deal with all the current versions of CodeSnip (i.e. up to v4.15.1):

  • Support has ceased. Please don't report any bugs. The old bug reporter on SourceForge has been taken down.
  • The web services that CodeSnip uses are still going to close on 15th June.
  • CodeSnip will no longer be able to download the online database, access the SWAG database or submit code after 15th June.
  • The news feed and program & database update checkers will cease to work on 15th June.

As for the new version:

  • It will not use any of the old web services. (I've done this because I can't guarantee they'll be supported on the new host).
  • A new version of the online database will be released on GitHub. CodeSnip will be able to load a load that database or continue to display any existing copy. However the user will have to manually download it from GitHub. There's a new wizard to help with this.
  • Likewise there's a revised version of SWAG due to be released that can be downloaded from GitHub. The import wizard is being modified to help load the new format.
  • Submissions to the online database will no longer be possible, although the export of code for sharing with others will continue to be supported.
  • The news feed and update checkers will be removed. News about updates will be posted on this blog. The blog is linked to from CodeSnip's Help menu.
  • The program will be supported: bugs will be able to be reported on GitHub (account required).

The upshot is that users need to update as soon as the new version of CodeSnip is released, and certainly before 15th June.

Watch this blog for more info.

Comments

Post a Comment

Popular posts from this blog

Released CodeSnip v4.21.2 (minor bug fixes)

-
Image
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.
Read more

Released CodeSnip v4.21.1 (bug fix)

-
Image
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
Read more

Released CodeSnip v4.21.0

-
Image
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'
Read more