DelphiDabbler.com Closure And Impact On CodeSnip

-

This post has been superseded - please see the Change Of Heart post for details.

On 15 June 2020 DelphiDabbler.com will be closing down.

This will have the following impact on users of CodeSnip:

  • Users will loose access to the online Code Snippets database. If the database has already been downloaded by then you will retain access to it.
  • Access to the online SWAG database will also cease. Any snippets from that database that have been downloaded before 15 June will remain available because they're stored locally.
  • CodeSnip will no longer be able to check for programs and online database updates. In the latter case that won't be a problem because there will not be any more updates, but you won't get notified of any new program updates that may follow 15 June.
  • The CodeSnip news feature will stop working - not that there's been any news for a long time!

In addition I'm not taking any more feature requests or bug reports for CodeSnip versisons up to 4.15.1] and, although the online bug reporter may work until 15 June, the bug report page it points to already gives a 404 error.

So, will there be any more programs updates?

I'm planning one final one that removes all the options that require DelphiDabbler.com to be alive. I'm also hoping to merge the online database with the user databasethat enables the online one to be downloaded from GitHub and to make it editable.I'm changing the online database to be downloadable from GitHub.

Whether I'll manage it before 15 June is debatable. If you want to follow progress please look at CodeSnip's GitHub page from time to time.

And finally, thanks for using CodeSnip this past 15 years!

Comments

Post a Comment

Popular posts from this blog

Released v2.2.0 of the Code Snippets Collection

-
Image
Finally, months after I meant to, I've released v2.2.0 of the DelphiDabbler Code Snippets Collection. This is a collection of snippets that can be loaded into CodeSnip program. To do so, download csdb-v2.2.0-data.zip from the GitHub release page . Unzip it somewhere on your system then run CodeSnip. Select the Install or Update DelphiDabbler Snippets Database  menu option and follow the wizard. If you would like to run tests on some of the snippets then download  csdb-v2.2.0-tests.zip  from the same place. Read the included read-me file for info about how to run the tests. Finally there's comprehensive documentation in  csdb-v2.2.0-docs.zip . In this release the main feature is the addition of a few routines to the Mathematics category. Specifically there are three IEEE conformant Pown routines and a couple of heavily overloaded summing functions. For details of these and other changes see the change log .
Read more

CodeSnip v4.23.0 Released

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

Never make new year's resolutions - dumping CodeSnip Belvedere

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