14 February 2016
31 December 2015
This is because the article demonstrated how to use the Google Earth API with Delphi. Now that Google has withdrawn the API the article itself has become redundant.
09 December 2015
The bottom line is that I'm persuaded that the site should continue.
So what decided me?
But, there's always a "but"
- Most of the site's content will be frozen. This means:
- No new articles
- No new hints and tips
- The online code snippets database and SWAG database apps may never get out of beta, and may even go away (but I'll ensure that the data remains available).
- The program and code library pages will probably get simplified.
- The content of the documentation "wiki" may get frozen, or even moved elsewhere. I don't like the wiki software much and it's a pain to maintain.
- I'll probably push ahead with giving the site a much needed make-over to make it mobile friendly. It all depends how long it's likely to take.
- I'll be limiting my programming quite severely. That means:
- Many projects will be abandoned, which means no support, no bug fixes, nothing. They'll still be available though.
- Several will become maintenance only - bugs may get fixed but no new features will be added.
- A very few will continue to be developed. These will be the ones that interest me. And I'm not sure which they are yet!
- I'll no longer be testing the code library or code snippets across multiple compilers. Everything will be compiled or tested with either Delphi XE or XE4.
- I can't foresee a time when I'll upgrade beyond Delphi XE4.
30 November 2015
This release adds support for detecting and reporting on the new "November Update" TH2 release of Windows 10.
This has been quite hard to detect because although Microsoft bumped the build number they haven't classed the update as a service pack, so TPJOSInfo reports no service pack as being present. In fact everything looks the same as the original Windows 10 except for the build number.
To allow users to display a bit more information when running on Windows 10 TH2 I've added a new ServicePackEx method to TPJOSInfo. This returns the same result as the existing ServicePack method when run on any OS prior to Windows 10 TH2. However on that OS ServicePack returns an empty string while ServicePackEx returns 'TH2: November Update'. The rationale of providing the new method is that I don't want to subvert ServicePack from its documented remit of reporting genuine service packs and only genuine service packs.
The intention is that ServicePackEx will also detect any future major updates that aren't classed as service packs by MS. Whether this is possible remains to be seen.
The other change in v5.2.0 is that the TPJOSInfo.BuildNumber method now always returns 0 if it can't determine the build number. Prior to this BuildNumber would sometimes try to get a build number from the registry as a last resort. This feature has been removed because it's become apparent that the registry can return the incorrect value for the build number despite the correct number actually being visible when the registry is viewed in regedit. It seems like Windows is spoofing the registry to report an older OS in these circumstances.
Well it all gets more and more complicated with each release of Windows doesn't it!
01 October 2015
What it boils down to is this: the time has come to decide whether to continue with the site or not.
And I need your help to decide.
There are a couple of reasons why I've got to this point. The first is that my interest in music, playing the guitar and recording has resurfaced and it's taking up some of my spare time. The second, and most important, reason is that I'm getting disillusioned with Delphi (the compiler, not the language). I just can't, or won't, keep up with the cost of upgrades.
The problem is that I'm just a hobbyist developer and the cost of staying up to date is getting prohibitive. I feel I'm getting more reward by spending my cash on musical instruments and studio kit than on a constant stream of compiler updates.
I'm not having a pop at Embarcadero here. Amateurs are probably not part of their target group of customers. And if that's true, I can offer no argument as to why we should be! I'm simply commenting that the cost of entry is too rich for me right now.You'd be staggered to learn quite how many decent quality instruments and bits of studio kit I've paid for just by missing out on a couple of Delphi Pro updates and not upgrading to the Android support module!
A consequence of all this is that if I'm cutting back on my Delphi development, I need to look at whether the DelphiDabbler website is worth continuing with. After all it's a lot of effort and costs me money to keep going. Donations have been drying up lately, meaning that more of the financial burden falls on me. (Whether the lack of donations is a sign of the website's diminishing relevance or the fact I've not been updating it much is debatable).
There's still time to decide what to do because the domain has been secured up to August 2017 and the web space is paid up to June 2017, but I think that now is an opportune time to start the debate.
I don't want to just pull the plug and waste all the effort that's gone into the site since it started back in 2002. So at the present time, here's what I think I might do to salvage as much as possible:
- Move all my apps and components etc. wholly onto Github (Git projects) and SourceForge (Subversion projects).
- Convert the articles and tips into PDF format and put them on GoogleDrive or similar.
- Close down the SWAG database web app and simply make the database available as a zip file.
- Close down the Code Snippets Database web app and make the snippets available as a Git project or as Gists on Github.
- Close down the site Contact page to reduce the amount of email I need to deal with.
- Cease development of most of my apps, components etc., leaving some in maintenance mode only, with a just a chosen remaining active. I'm likely to keep only my CodeSnip application (in a modified form) and the System Information Unit and Window State Components under active development.
- When the web space account expires redirect DelphiDabbler.com to some pages on GitHub.
- When the domain comes up for renewal either let it expire or move to a new cheaper .co.uk domain. Alternatively invite others to take it over.
All the above is up for debate and if there's sufficient interest I may keep a more tightly focussed and easier to maintain version of the site up and running.
The only things that are pretty much fixed at the moment are that I won't give up the music and I won't upgrade Delphi beyond XE4.
In the meantime I may explore the Free Pascal and Lazarus options. However once XE4 becomes so outdated as to be useless, that's likely to be where I bail out.
I'm still considering making the site more mobile friendly for what is potentially its last 18 months of existence.
I need your views
So, what do you think? Any observations will be welcome. I've come to a crossroads and I need some guidance about which way to go.
Please comment. Should I let DelphiDabbler.com die? Should I keep some parts? What's the most useful to you, if anything?
I'd also like to hear from anyone who might like to take over the site and/or domain over?
Just encountered a strange bug in one of my programs when running it from the Delphi XE IDE on Windows 10.
Triggering a TBrowseURL action with a valid URL property value causes the program to hang and the default browser (Chrome) is not displayed. The BeforeBrowse event is triggered, but AfterBrowse is not until the program is closed. Sometimes the program hangs and I have to close it with Ctrl+F2.
Running the same code outside the IDE works correctly, but running the program either with or without the debugger in the IDE makes no difference.
I've tracked this down to where TBrowseURL calls ShellExecute from the ShellAPI unit. If I call ShellExecute directly I get the same problem.
I never noticed this problem before when running Windows 7 on my old laptop - it just seems to have started on my new Windows 10 laptop. Still, it's possible the bug was still there on the old machine and I just never noticed it, but I doubt it.
Anyone else had this problem? Any ideas what may be causing it?
04 September 2015
Following the announcement earlier this year that GoogleCode was about to close I moved the Delphidabbler Code Library Subversion source code repository to SourceForge, where the downloads had been hosted for some time.
A little later I started a GitHub project to host the library documentation and copied all the docs formerly hosted in the GoogleCode wiki to there. The documentation is currently split between GitHub and my wiki sub-domain, but ultimately I intend for it all to be on GitHub.
Now that GoogleCode has become read-only I've decided to close that project down, and that's happening as I write this. The old GoogleCode URL will simply redirect to SourceForge.
So, in summary, you'll now find the library in the following places:
22 September 2014
About one month ago I posted an initial design for the new responsive website page header. Here's how the mobile version looked:
At the time I said I would like change this to place the "branding" and the "Menu" button on the same line but I hadn't worked out how to do it. I've pretty much sorted it now, so here's the revised version:
I'm happier with this version since it takes up a lot less vetical space. I'd also decided against using the "hamburger" icon on its own to represent the menu - in the first version I simply used "MENU" instead as being understandable by everyone. In the later version I've appended the hamburger icon to the text.
The appearance of the header on larger tablets and laptops / desktops has been altered very little. There's just a change to the "home" and "search" icons (I'm now using Font Awesome instead of GlyphIcons) and the serif font used for the strapline has changed. Here's the first version:
And here's the revised version (spot the difference!):
As before comments are more than welcome.
21 September 2014
After having mocked up the branding (i.e. page header) for the new website I've now turned my attention to content.
After looking at some designs I like around the web I've come up with the following look and feel for the site's software pages. The mock-up is for one of my applications, but I'm considering using the same style for Delphi library projects.
Here's the 1st draft of the design as it displays on larger tablets and desktops:
And here's how it appears on mobiles or small tablets:
Finally, to anable comparison, here's the current site showing similar content for the same application:
What do you think? Any comments are welcome.
24 August 2014
I think I've got the website header sorted sufficiently well to give it a public airing.
The idea is to keep the original colour sheme and to show the site name in roughly the same style as used on the current site. But now the font's changed and it's rendering text and CSS instead of using an image. It's coded using Bootstrap.
Here's the new header as it will display on larger tablets and desktops:
There's a change in the site navigation: the old site places it down the left hand side of the page while the new site uses a horizontal bar under the branding. I'm using the Bootstrap navbar but I've tried to change the appearance by moving the branding out of the navbar. I've also changed the navbar colour scheme to match the branding. The biggest change is the inclusion of a search box in the navbar.
Here is how the header appears on phones and small tablets:
The navigation moves into the drop down menu on the mobile version and the "strap-line" disappears. I've replaced the Bootstrap "hamburger" menu icon (which I'm not to keen on) with the more obvious "MENU" text. I would prefer to move the menu button up onto the same row as the logo, but haven't worked out how to do that yet!
Just for reference, here's the current website header:
Well, that's the hard part done. All that's left is to design, code and populate the content pages!
Any comments on the new styling will be appreciated.
The current version of DelphiDabbler.com has been around for years. It looked quite modern when it was released, but not now. Far from it.
So, the time I'm been putting off for so long has arrived: a re-design is in the works. Not a simple refresh, but a root and branch re-design and re-build.
I've got four design goals:
- The new site must be responsive - the current one looks aweful on phones and small tablets.
- A want a fresh, clean and uncluttered look and feel - it's currently dated and cluttered.
- The content needs to be leaner - there's just too much stuff on the current site so a lot of it's got to go. Also, this is the only way to make the job manageable.
Big job for one man then. Especially one who has not kept up to date with modern web programming developments.
I've spent a lot of time over the past weeks reading about responsive design and have researched several techniques. I even tried out one UI framework on the new CodeSnip micro-site with no great success - that's getting changed too!
What I've decided so far is that I'm going to use Bootstrap 3 as the front end framework, because I like the mobile-first responsive design it enforces.
I had some reservations about Bootstrap at first because there are many, many Bootstrap based sites that all look pretty similar. So, I've decided to customise it. And I tried writing a CSS file that modified some of Bootstrap's appearance and ended up with a site that looked like all the others. Because re-skinning Bootstrap via plain CSS is hard.
Plan B was called for. I went "shopping" for Bootstrap templates and couldn't find one I liked at the right price, the right price being £0.00!.
So to plan C, which means customising Bootstrap using Less. Problem is, I've never used Less, so have had to go on a detour to grasp the principles. I was considering hacking the Bootstrap Less files directly until I hit a Bootstrap 3 Less Workflow Tutorial. This was the eureka moment. Now I'm incorporating the Bootstrap Less files in my project and customising them via a set of stand-alone Less files. One day in and it seems to be working.
Now I'm having to learn both Bootstrap and Less as I go along!
I'm pretty sure I'm not going down the web application framework route. I struggle to see how frameworks like AngularJS will help me - DelphiDabbler.com isn't really a web app. So, I think I'll stick with PHP and generate pages on the server.
I've always coded straight to PHP, JS and CSS before. This meant I could write directly to the to a version of the site running in a local Apache server and so see the results of changes immediately. No build process at all. Now I'm using Less that old process won't do because there's a compile step needed before I have usable code. I now need a proper build process. So Node and Gulp have just hit the hard drive. Something else to learn - oh joy!.
I going to maintain the source code in a Git repo. Haven't decided yet whether to keep the code private or whether open source it.
So there we have it. Ambitious and challenging for an old Delphi hacker who has pretty much ignored the world of web development for the last 10 years. Not sure if I'll make it.
I'll keep updating this blog with any progress and will aim to publish early versions somewhere deep down in DelphiDabbler.com in due course.
20 July 2014
Pulling together the loose ends to release the BDiff / BPatch Utilities yesterday must have triggered a tidying loose ends gene. Because now I've been motivated to put the finishing touches to some code I wrote a few months ago that significantly extends the capabilities of my CompFileDate File Date Comparison Utility. As a result CompFileDate v2.0.0 was released today.
This Windows command line app now lets you specify what operation is used in the comparison of file dates: ">" (i.e. file 1 is later than file 2), "<" (i.e. file 1 is earlier than file 2), "<=", ">=", "=" or "<>". You can also compare files' last modification dates or creation dates. Finally, when comparing the dates of shortcuts there is the option to compare the dates of the shortcuts or the dates of the shortcuts' target files.
The source is maintained in the delphidabbler/compfiledate Git repo on GitHub. Contributions welcome.