Some Impacts Of Forthcoming Site Closure

Update: The site is no longer closing!

Some of the changes below may still happen, but the site itself is staying up. See this post for details. Keep an eye on this blog for updates.

Now that the 15 June date for closure of DelphiDabbler.com is less than 6 months away I thought it was time to set out some of the implications.

Here are the main issues:

  • The wiki at wiki.delphidabbler.com will go away. This means that some documentation, FAQs and various useful notes will be lost. In particular the online help for some of my Delphi Code Library will disappear. Some of the docs have been moved to GitHub, but many haven't. I doubt there will be time to move any more. There may be time to save some FAQs and to GitHub but it can't be guaranteed.
  • The CodeSnip program will loose access to some of the webservices it uses. There's a separate blog post about this.
  • The online version of the Code Snippets Database will be lost. But all the code should still be available to users of the CodeSnip program (all being well).
  • All the site news feeds will stop working.
  • My Delphi articles will be lost. But I'm hoping to save at least PDF versions on GitHub, time permitting.
  • The software on the site will not be adversely affected - everything exists either on GitHub or on SourceForge.
  • The online SWAG database will be lost. I'm hoping to move the actual database to GitHub, again timw permitting.
  • The Delphi Tips database front end will be lost. It was announced a while ago that it was deprecated. Every tips has been rendered as a PDF and those, along with the raw HTML has been placed on GitHub.

I'm considering retaining the delphidabbler.com domain and pointing it at GitHub, but haven't finally decided.

Finally, thanks for supporting the site over the years. And thanks for the donations that helped offset some of the costs.

Comments

  1. Far8:37 am

    What a pity. Can I buy your site?

    ReplyDelete
  2. Delphidabbler10:06 am

    Hi Far.

    Thx for the offer, but I don't want to sell it. Currently discussing whether we can keep it going with someone.

    Cheers

    ReplyDelete

Post a Comment

Comments are very welcome, but please don't comment here if:

1) You have a query about, or a bug report for, one of my programs or libraries. Most of my posts contain a link to the relevant repository where there will be an issue tracker you can use.

2) You have a query about any 3rd party programs I feature, please address them to the developer(s) - there will be a link in the post.

3) You're one of the tiny, tiny minority who are aggressive or abusive - in the bin you go and reported you will be!

Thanks

Popular posts from this blog

Deleting elements from a dynamic array

In my blog " Initialising Dynamic Arrays " I mentioned I have been writing some unit tests that needed numerous repetative array initialisation operations. Well, one of the other common operations I found myself writing was the deletion of items from dynamic arrays. So I decided to find a generic way of doing this. Assuming we know the index of the item to be deleted we need the equivalent of Delphi's built-in Delete procedure for strings. If you read the previous post you won't be surprised to learn that I decided to further extend the Generics.Collections.TArray class by adding to the TArrayEx class I introduced there. My first attempt emulates Delphi's Delete procedure by deleting the array element in-place: i.e. it updates the array passed as a parameter. Unsurprisingly the method is called DeleteInPlace . Here's how it goes: type TArrayEx = class ( TArray ) public .. . class procedure DeleteInPlace < T > ( var A :
Read more

Initialising dynamic arrays

When writing some unit tests a while ago I found myself needing to initialise some dynamic arrays with test data. It would be nice if we could do something like this: var A : array of Integer ; begin A := ( 1 , 2 , 3 , 4 ) ; // !! WRONG end ; but we can't. So I decided to write some functions to initialise dynamic arrays to the contents of another array, be it a constant, a literal or another dynamic array. The result was a set of overloaded routines, one for each data type I needed to handle, for example for Integer and string arrays I had: function CloneArray ( const A : array of Integer ) : TIntegerDynArray ; overload ; var Idx : Integer ; begin SetLength ( Result , Length ( A ) ) ; for Idx := Low ( A ) to High ( A ) do Result [ Idx - Low ( A ) ] := A [ Idx ] ; end ; function CloneArray ( const A : array of string ) : TStringDynArray ; overload ; var Idx : Integer ; begin SetLength ( Result , Len
Read more

New String Property Editor Planned For RAD Studio 12 Yukon 🤞

Image
This blog post is based on a pre-release version of the RAD Studio software and it has been written with specific permission by Embarcadero. No feature is committed until the product GA release. It seems I'm getting very excited about multi-line strings of late. My previous post was about multi-line string literals for Delphi  and this time I'm talking about the new multi-line string property editor being slated for the RAD Studio 12 IDE. For more years than I care to remember, I've been frustrated by the inability to enter multi-line strings in the Delphi IDE object inspector. That meant having to resort to code to initialise some multi-line labels. So frustrated was I that I wrote a little property editor of my own ( stringpe ), way back in 2004. It's still around and on GitHub. Here's what it (sometimes) looks like: Yeah, I know this is Vista - I used an old screenshot Sometimes? Well it looked like that until it got installed on DPI aware Delphis, and then it sh
Read more