Thursday, August 27, 2015

Two More Days for the RAD Studio 2015 Developers Survery

The yearly RAD Studio developers survey is closing in 2 days. If you can find the time to participate, we'd appreciate. And here are a couple of tidbits from it.

The yearly RAD Studio developers survey is closing in 2 days. If you can find the time to participate, we'd appreciate. And here are a couple of tidbits from it.

But first of all (and before you continue reading) if you haven't already done so, take the survey at www.surveymonkey.com/r/FGCCYNY . We know it is time long and time consuming and really appreciate your input. If you don't have the time, we understand.

Now, if you have taken the survey and had the patience to go to the end, you might have noticed a fun, trivia question asking for your favorite RAD Studio variable or type name. These are the answers so far:

  • Global variable ReportMemoryLeaksOnShutdown is winning with 41% of the votes
  • The exception type EProgrammerNotFound is close second with 37% of the votes

I'm really disappointed that the enumerated values Elf, Dwarf, and Wizard in TDeviceClass got less than 8%. I like those and the way they are documented in the help file.

More seriously, we generally don't share survey data but there are a couple of (temporary) results worth mentioning, considering these are not absolute facts but depend on those who responded, of course, who are mostly "active" customers even if often using versions released years ago)
  • FireDAC is now the most used database access library
  • Microsoft SQL server and Mongo DB are the preferred relational and NoSQL databases
  • Parallel programming library is the favorite RTL extensions done in recent years

Overall, we had a good response rate, but, again, we'd appreciate having even more. And a few extra votes for the elves ;-)

 





Monday, August 24, 2015

Delphi Blogs of the Week/Month #33

Lots of news, despite the summer month, and also a recap of things I already blogged about, in case you were taking some week off. And the first sneak peaks to coming features...

Lots of news, despite the summer month, and also a recap of things I already blogged about, in case you were taking some week off. And the first sneak peaks to coming features...

The Yearly Survey is Open

As I already blogged about, take the yearly survey THIS WEEK ONLYwww.surveymonkey.com/r/FGCCYNY

Coming Soon to RAD Studio...

If you want to know all about the new, coming release sign up to the launch webinar,  forms.embarcadero.com/RADFirstLookWebinar-2015-09-02

Summer Product Announcements

BeaconFence: blog.marcocantu.com/blog/2015-july-beaconfence.html

Konopka Signature VCL Controls: www.embarcadero.com/products/konopka-signature-vcl-controls

CodeSite now from Embarcadero: www.embarcadero.com/products/codesite

My Object Pascal Handbook now in print: blog.marcocantu.com/blog/2015-august-object-pascal-handbook-print.html

Other Recent Blog Posts

Craig Chapman has a long, detailed, and must read article on "Migrating your project from older versions of Delphi. The pitfalls." See chapmanworld.com/migrating-your-project-from-older-versions-of-delphi-the-pitfalls/

Windows 10 Developers White Paper by Embarcadero, introduced in my blog at blog.marcocantu.com/blog/2015-august-windows10-whitepaper.html

If C++ IDE code editor structure windows is blank on Windows 10 machine, here is a workaround by David I: community.embarcadero.com/index.php/blogs/entry/c-ide-code-editor-structure-windows-is-blank-on-windows-10-machine-workaround

 

That's all for now, stay tuned for more RAD Studio coming soon information in the coming days, and don't forget to take the survey and sign up for the webinar.

 

 

Friday, August 21, 2015

Windows 10 Developers White Paper by Embarcadero

Embarcadero has released a white paper titled "Windows 10: The Big New Opportunity for Developers", explaining why Windows 10 matters and why RAD Studio is well positioned to serve the Windows 10 developer community

Embarcadero has released a white paper titled "Windows 10: The Big New Opportunity for Developers", explaining why Windows 10 matters and why RAD Studio is well positioned to serve the Windows 10 developer community.

You can find the white paper (after filling in your contact info) at  forms.embarcadero.com/15Q3DownloadWindows10Whitepaper

The white paper has the following sections:

  • What is Windows 10?
  • What’s new in Windows 10?
  • Windows 10 and RAD Studio
  • Project Centennial: bringing desktop apps to the Windows Store
  • Getting ready for Windows 10

It has been written by an external (and independent) technical expert and includes a lot of background information and technical details. Worth reading for everyone moving or considering to move to Windows 10... which should be all of the Windows developers out there!

PS. Sign up for the webinar "Ride the Windows 10 Release Wave" on September 2nd, http://forms.embarcadero.com/RADFirstLookWebinar-2015-09-02, which will provide a preview of the features in the NEW VERSION OF RAD STUDIO to further enhance Windows 10 support... and not only, given the new release will include many other compelling features.

 

Wednesday, August 19, 2015

RAD Studio 2015 Developer Survey is Live

The 2015 edition of the yearly RAD Studio, Delphi, and C++Builder developers survey is available and will remain open until Aug 28th.

As I already blogged on the Embarcadero community site at community.embarcadero.com/blogs/entry/2015-rad-studio-delphi-and-c-builder-developer-survey, the 2015 edition of the yearly RAD Studio, Delphi, and C++Builder developers survey is available and will remain open 10 days, until August the 28th. The survey has 100 questions divided in 18 pages and we estimate it can take 30 to 45 minutes to take it.

This is the link:

https://www.surveymonkey.com/r/FGCCYNY

In case you don't have time to go over all sections, you can skip a page, as only a limited numbers of questions require an answer to continue. In this case, please complete the pages you are most interested in. Of course, we'll appreciate if you have time to complete all pages.

We know your time is valuable and so we greatly appreciate your participation in this annual survey, which will significantly affect the product development and planning for the next 18 months. There are also new questions this year to help us better understand how you are using the product.





Wednesday, August 12, 2015

The Story of the High Fix Rate of RAD Studio Bugs

Here is an overview of the process the RAD Studio team uses for handling bugs reported by customers and the current status in terms of numbers of bugs fixed. In short, over 70% of the bugs publicly reported in recent years has been addressed.

Here is an overview of the process the RAD Studio team uses for processing bugs reported by customers, and the current status. Over the recent years, the effort in fixing bugs and issues reported by customers has increased significantly. We have numbers from our internal bug tracking system that can shed some light. 

Before we get to those numbers, however, it is important to understand how the RAD Studio team tracks and manages bugs, how they are categorized and processed. I won’t get to the details, but an overview will help explain the rest of the story.

From Quality Central to Quality Portal

For many years, the customer-facing tool for reporting bugs was hosted as Quality Central at http://qc.embarcadero.com. This was an internally developed bug-tracking tool that mapped to the internal bug tracking system, RAID. It is still there, but don't use it any more.

Over the years, RAID was replaced with an instance of Atlassian Jira (https://www.atlassian.com/software/jira), and Quality Central was remapped to it. Since last year, the team introduced the new Quality Portal (http://quality.embarcadero.com), which is also based on Jira but has different configurations and settings. The current flow from Quality Portal to the internal system and back is very smooth and it is significantly improving the communication between the team and customers reporting bugs.

Bugs Flow and Status

The second information worth knowing, before looking to the actual data, is the flow up bugs and their status over time. For this, I’m considering the current system (there were differences in the previous combinations).

When a bug gets reported, it is copied in the internal system and is validated by a QA (Quality Assurance) team member. He might open it and send to the proper developer, close it because it is not considered a bug but the expected behavior, a “test case” error, close because it cannot be reproduced, open it as a feature request for future consideration, ask for more information to the bug reporter, close it as duplicate of an existing issue… and a couple of other scenarios.

At that point, if the bug is open, it is assigned to a developer, who can provide a fix for it, but also suggest a temporary workaround, can decide this is expected, or suggest merging it with future work. An individual developer doesn’t actually do this process alone: There are team meetings, “bug council” meetings, and many steps to access and re-evaluate over time the priority of issues.

There are a couple of further considerations here. The first is that when a bug is closed internally, its status is not immediately reflected in the public system. The reason is simple: Telling a customer the bug is closed but he or she cannot get the fix would be of no value. The bug is marked fixed in the public system when a fix including the bug is released. This is why in the public system there are huge spikes of fixed followed by periods in which it seems nothing is done. The internal system, instead, tells a more complete story.

The second consideration is that a significant number of bug reports that are not considered “errors” in the current implementation, but requests to extend a given capability are kept in the system. While internally tagged as “feature requests” they stay open and look like bugs not being addressed. In theory we could close them indicating the feature works as "currently" designed, and open a separate internal request for enhancements.

The last and final consideration is here we are looking to publicly reported bugs, but you have to consider that the majority of bugs is reported internally by the QA team, other developer, or internal users (incuding myself). Our goal and more consistent effort, of course, is to fix bug before the software is released. So the internal numbers tells a different story, but for this blog post we are focusing only on bugs reported by customers.

Let’s Get to the Data

With this picture in mind, I’ve recently dug some data and some graph that help understanding the current status and the extra effort done recently on RAS Studio quality.

Faster Resolution Time. The first graph shows the yearly average resolution time over the last 4 years. This is how many days it takes on average to resolve an issue. Thinks are improving significantly, I’d say.

70% of Reported Bugs Have Been Solved. If we consider all bugs that have been reported over the same time frame (from 2012) and came from customers, we get a real picture of the effort. If you add closed and resolved issues, it’s a 71% of the total. Many of the re-open issues are also partially closed (they might not be optimal or complete solutions). Also among the open issues there are 279 (at a recent count) marked as feature requests, which brings the real number of open bugs further down.

Conclusion

There is certainly much more information we can dig in our system to show how many publicly reported bugs have been fixed over time in the various product areas. The new public bug tracking system is also making it easier to follow the bugs status and it’s ensuring a better communication between customers, quality assurance team, and development team.

The RAD Studio team is focused on further improving the process and devoting more resources in fixing issues. The trends have been encouraging, but this doesn’t mean we think our effort is good enough and we are going to stop here. On the contrary, we see a positive trend and want to keep focused on that direction, increasing the timeliness of bug fixes, their numbers, and (which is what really matters) the overall product quality.

PS: Clarification on Closed Vs. Fixed Issues

Some of the comments (including a few I didn't approve) hint to the fact that not all "fixed" issues have been specifically addressed by the team, given some might have been duplicate or coud have ended as being considered "test case errors". So I dug some extra information. Out of that bucket of closed bugs, over 3,200 individual and distinct issues have been fixed with actual changes in code. Wiht is roughly half of all of the issues that have been addressed. 

 

Friday, August 7, 2015

Object Pascal Handbook Now in Print

My latest book, Object Pascal handbook, is now available in print on Amazon and other outlets.

My latest book, Object Pascal Handbook, is now available in print on Amazon and other outlets. I finished the book 2 weeks ago, got my proof copy earlier this week, and given it was good, I gave it the green light. The book, in fact, is self-published through CreateSpace, where it is available at  www.createspace.com/5559999  (this is the online store I earn more from, but Amazon is also quite good on margins).

On the Amazon.com site the book is  www.amazon.com/Object-Pascal-Handbook-Marco-Cantu/dp/1514349949  (and already selling, given it is going up in places in the "Langauges and Tools" category under programming). You can buy it also from the UK site (www.amazon.co.uk/Object-Pascal-Handbook-Marco-Cantu/dp/1514349949) and the German one (www.amazon.de/Object-Pascal-Handbook-Marco-Cantu/dp/1514349949) in which case I understand they print the book in Europe and ship locally. Other Amazon stores should have it, and other non-Amazon sites should get it as well in the coming weeks.

Cover price is 46.50 US Dollars, 31.50 UK Pounds, 43.50 in Euro (but Amazon has it a little higher). The final book is well over 500 pages.

More information is at  www.marcocantu.com/objectpascalhandbook/  although I still need to udpate that page with the buy links, the complete TOC and the index, and more information. Should be done in the coming days. Along with sharing more of the source code of the demos.

The ebook remains a free download for XE7 and XE8 registered users, and should be updated with the complete version (3 more chapters from the last draft) shortly. I'm considering making it available as a paid ebook as well, but not immediately.

 

Tuesday, July 28, 2015

New BeaconFence for RAD Studio

Beside announcing the deal with Raize Software, today we are announcing a new internally developed components focused on beacon fencing, that is a new technology for tracking mobile user indoor.

Beside announcing the deal with Raize Software (see my previous blog post), today we are announcing a new internally developed components focused on beacon fencing, that is a new technology for tracking mobile user indoor. You can read all about BeaconFence at:

http://www.embarcadero.com/products/beaconfence

In short, this is a technology based on beacons, that lets developer graphically design areas within an indoor building (a large store, a restaurant, a mall, a sports facility...) and define actions and event that fire when a user enters or exists the given area. The image below of the map editor gives you a feeling of the product, which is a component with some specific and very complex design time editors.

Again, head to the product page for more information and check our the "pay-per-use" pricing. You can sign up the free plan for BeaconFence, get the component, build and deploy a simple scenario. For more complex solutions, there is a deployment fee depending on the size of the building and related factors.

One of the reasons we are particularly proud of this product and this technology is that BeaconFence is the first commercial ready-to-use beacon fencing solution for software developers available today.

Embarcadero Buys Raize Components and CodeSite

Embarcadero Technologies today announced the acquisition from Ray Konopka's Raize Software of Raize Components and CodeSite.

In case you don't know, Ray Konopka has been from the early days of Delphi one of the leading authorities on components development, thanks to his classic components development book, the countless Delphi conferences he has spoken about this subject (along with UI design and other VCL technologies) and the great set of high-quality components he built and sold as Raize Components. Ray has done a lot more with Delphi, in terms of tool, training, consulting and business development, and he is one of the Delphi community gurus.

This is why I'm extremely happy to see this acquisition by Embarcadero Technologies of his flagship components and his CodeSite logging tool (the light version of which already ships with RAD Studio). Embarcadero starts selling these components today. The components have been renamed as "Konopka Signature VCL Controls". The CodeSite Logging System keeps its existing name and is available for RAD Studio but also Visual Studio. Both can be bought today, along with subscription, from Embarcadero web shop and from our partners.

You can read the complete press release at www.embarcadero.com/press-releases/embarcadero-acquires-raize-components-introduces-new-windows-ui-and-logging-products-for-delphi-and-cbuilder-developers.

What should I add? Stay tuned for more add-on components from Embarcadero, to complement RAD Studio but also supporting other development tools.

 





Wednesday, July 22, 2015

Delphi Blogs of the Week/Month #32

Long time without blogging, but I took 2 weeks off and was very busy last week. Here is a short round of interesting tidbits for Delphi developers.

Long time without blogging, but I took 2 weeks off and was very busy last week. Here is a short round of interesting tidbits for Delphi developers.

Company News

Embarcadero opening its focus on more developers, beside those using our IDEs and programming languages. New nice developers landing page at:  www.embarcadero.com/products/application-development . More information will get added to the page over time. Stay tuned.

As an example, AppAnalytics (www.embarcadero.com/products/appanalytics) is going beyond RAD Studio... www.nuget.org/packages/appanalytics.

Unexpected Delphi Blog Posts

The last person I'd have expected to start blogging about Delphi is Chuck Jazdzewski, who was one of the original developers of the VCL library and of Delphi itself (and after moved to Microsoft and Google). He had several posts in his http://removingalldoubt.com/ blog. They really explain some of the core foundations of Delphi, and titles are quite descriptive:

And One More Delphi Blog Post

Minecraft in Delphi? Kind of. Read www.fmxexpress.com/free-minicraft-game-source-code-for-delphi-xe8-firemonkey-on-android-and-ios/ Interesting. I've been watching my son play Minecraft, and set up a server for him. Good stuff.

Again, summer vacation is mostly over for me, now get back to work... and to blogging.

 

 

Saturday, June 27, 2015

Delphi Blogs of the Week/Month #31

A lot time since the last collection of links, but here is it.

A lot time since the last collection of links, but here is it. (And by the way, I'm going on vacation and will leave the blog quiet for a couple of weeks)

Blogs Etc

Third Party