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 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