Reminder to self: check if David Nottage published source code the Firebase application analytics

I need to check the outcome of this comment at [WayBack] Google analytics is no more avaliable for analytic Apps and send to firebase when you want to track a new App. How to do with firebase analytics? there … – Xavi P. – Google+: I’m working on an implementation. It’ll be an extension of what I did with Firebase Cloud Messaging: [WayBack] Adding Firebase Cloud Messaging to your mobile apps – part 1 – Delphi Worlds However, my implementation may or may not become a part of a commercial solution that includes other Firebase services, including Firebase Database, using the Android and iOS SDKs –jeroen
Read More

What’s New and Updated in GetIt for November 2018

The GetIt Package Manager is your source for RAD Studio, Delphi, and C++Builder add-ins and packages built right into your favorite IDE. Here’s a look at what was new and updated during the month of October 2018 along with the most popular downloads. Find a new favorite for November today!

Want your Package, Library, Trial, or Open Source Project in GetIt? Just fill out this form.

New and Updated

The following components are new to GetIt this month, or were recently updated to a newer version.


Delphi Console – Delphi Console is a Delphi implementation of the well-known C# class: System.Console. With this in hand you can easily use all the functions of the console window. For example: Console.WriteLine.



Eigen – C++ template library for linear algebra: matrices, vectors, numerical solvers, and related algorithms.

[More info]


Trial – FMX Skeez – An animated list view component for Delphi FireMonkey. The package includes derived components: filesystem browser, picture list viewer and audio file list viewer.

[More info]


Trial – ImageEn – A native image library for Delphi and C++ Builder. It includes a complete suite of components to handle all aspects of image and editing, analysis and display. 

[More info]


Trial – nrComm Lib – Helps with wide range of device communication tasks and industrial issues. It contains ready solutions for RS232, modbus, GSM, HID and etc.

[More info]


Trial – Clever Internet Suite – A Delphi and C++Builder library for Internet communication protocols. It provides support for HTTP, FTP, SMTP, POP, IMAP, SFTP (SSH), DKIM, OAUTH, SOAP, WebDAV, complete client and server solutions for supported protocols, digital signatures and encryption.

[More info]

GetIt Top and Trending

Here are the top 10 most popular downloads from October, and any from the top 30 that are increasing in popularity.


    JEDI Code Library: The JEDI Code Library (JCL) consists of a set of thoroughly tested and fully documented utility functions and non-visual classes which can be instantly reused in your Delphi and C++ Builder projects.


    JEDI Visual Component Library: JVCL is a library of over 600 Delphi visual and non-visual Delphi/C++Builder components.


    Icons8: Single icon pack with 64,800 free icons. Each icon is in 5 flat styles.


    CnWizards: CnPack IDE Wizards (CnWizards) is an extremely popular, well established and comprehensive free open source plug-in toolset for Delphi/C++ Builder/RAD Studio to help improve development efficiency by proving a large number of useful add-ons and wizards to enhance the Delphi/C++ Builder/RAD Studio IDE.


    Aqua Light Slate 2 VCL Style: Free to use VCL Style


    CodeSite Express: Live Local and Remote Application Logging


    Abbrevia: Abbrevia is a compression toolkit for Delphi and C++Builder.
Supported on platforms: Windows, Android, macOS, and iOS.


    AsyncPro for VCL: Async Professional is a comprehensive communications toolkit for Embarcadero Delphi and C++Builder. Supported on platforms: Win32, Win64


    FortesReport Community Edition: The FortesReport is a powerful report generator available as a package of components for Delphi. In FortesReport, the reports are composed of bands that have specific functions in the print stream. You define groupings, sub-levels and totals simply by hierarchical relationship between bands. Moreover, the FortesReport has a rich palette of components for text, charts, formulas, bar codes, filters and layout.


    Glossy 2 VCL Style: Free to use VCL Style


    EhLib: EhLib is a Delphi and C++Builder library of visual and non-visual components. Most advanced component is DBGridEh, component to operate tabular data in DataSet. Library includes more than 30 components in total.


    SysTools for VCL: Utility routines and classes for Delphi and C++Builder. It includes bar codes, sorting, money routines, logging, high precision math…Supported on platforms: Windows


    Clever Internet Suite: Clever Internet Suite is a Delphi and C++Builder library for Internet communication protocols. It provides support for HTTP, FTP, SMTP, POP, IMAP, SFTP (SSH), DKIM, OAUTH, SOAP, WebDAV, complete client and server solutions for supported protocols, digital signatures and encryption.


    TFrameStand: TFrameStand is a component to ease use of FMX frames in your application. Take advantage of TFrameStand functionalities to build stunning visual transitions and improve the visual continuity of your UI. Supported on platforms: Win32, Win64, Android, OS X. Open source by Andrea Magni.

Read More

Read More

The Web vNext

I have been reading a lot about Web development lately, and pondering the future of web development.  For the longest time I shied away from Web development, largely because it was so laborious and frustrating. I dabbled a bit back when people were using COM objects with VBScript on the server and Javascript on the client in classic ASP pages. Even back then, companies were making software look like Windows applications within the browser (IE).  By today’s standards, those applications look dated, but today’s web SPAs function in a similar manner, although great progress has been made in standardizing browsers, abstracting out their idiosyncrasies using frameworks, and handling variable display sizes.  My current experience is that it’s still harder and more time consuming to develop a good web application, and they are still not as rich as a Windows app IMHO. That begs the question as to why people are writing applications for the web anyway.  For eCommerce sites, I get it, but for other line of business applications why not throw off the shackles of HTML/CSS and embrace a new UI framework altogether?  Now I know what you’re thinking…..this guy has lost it and wants to re-invent the web which a lot of smart people have worked on for years to make Web 2.0 a reality.  Before you call the white coats, read on… When a user goes to a web site for any commercial activity they should be ensuring the website has a valid SSL certificate from a trusted authority.  The Internet is a dangerous place these days where web sites may be trying to attack your computer.  We download content from such sites into our sand boxed browser. This is not that much different than downloading a signed application.  We use signed applications all the time now, when using applications on our phones, tablets and desktops from the “app stores”.  The only difference is whether the store owner i.e.: Apple, has reviewed the application testing for malware.  Open source software such as Tortoise Git is often signed as well to ensure users trust that the application they are getting is from the advertised source and is safe to use.  I think it’s safe to say that most people would trust a signed application. With that premise in hand, why aren’t we all writing signed Desktop apps using REST back ends?  Or if we really want to leverage single source cross platform applications, why not use WASM with a UI framework that allows an application to be written in languages that are typically used for native desktop, and mobile devices such as C#, Delphi, or C++? The performance of even Javascript is pretty decent.  Many games have been ported to the browser using Javascript transpilers or EmScripten.  WASM allows developers to take this one step closer to the metal (CPU) and skip the run-time parsing and execution of Javascript.  Blazor is a project that does just that, within the confines of HTML/CSS, but also shows the possibility of using WASM with a different presentation framework such as Uno, or Ooui.  Obviously I’m not the only one thinking that a different presentation layer might be overdue in the web space. One of the advantages of Blazor is to eliminate some of the third party dependencies, making the development stack more reliable, and to use the same technology and tools throughout.  Of course you can learn and use Javascript throughout the entire stack now, or a Javascript transpiler, but without WASM using your development language of choice is not possible. I would like to see Object Pascal support the entire development stack.  Preferably the same language dialect and core libraries.  Perhaps something similar to Blazor, or maybe FMX targeting the web with WebGL.  All we need is to be able to capture the compiler IR and feed it into the WASM LLVM back end (okay there might be a little more to it than that).  The web is a huge horizontal market that is ripe for disruption and with the right moves, Delphi could grab a chunk of that segment, making the product relevant again. What do you think is the future of Javascript on the web?  Will it be dethroned at some point by WASM? Is the future of the Web HTML/CSS, a different UI layer, or perhaps a mix depending on the type of web app?  Should I dust off the Delphi .NET compiler to generate MSIL to feed the Mono WASM run-time, or do we need a way to get the current compilers to output LLVM IR? Maybe it’s just time to call the white coats as pondering all the options can drive you crazy…
Read More

TMS WEB Core: a bridge to the future!


While working in the TMS Labs this week, we had a fruitful discussion on how we could interact with a desktop or mobile environment, where the browser that hosts a TMS WEB Core application, runs on. We already had some experience creating a JavaScript bridge between a TWebBrowser and Google Maps ( and figured out this could be useful for TMS WEB Core as well. We wanted to give the user the capability of hosting its TMS WEB Core application in a native desktop or mobile application that offers access to all of the operating system functionality and make it accessible via the browser.

Finding an entry point

We created a TTMSFNCWebCoreClientBrowser class that acts as the communication and viewing component for a TMS WEB Core application. To setup the communication, we needed an entry point. In JavaScript, a global variable can be defined and that was just the entry point we were looking for. In TMS WEB Core, during the creation of TApplication, we also injected a global variable “TMSWEBCoreClientBrowser”, that is initialized with a string “unknown”. This variable is filled in, when the TTMSFNCWebCoreClientBrowser establishes a conection to the TMS WEB Core application.

  if ExecuteJavascript('document.readyState', true) = 'complete' then
    if ExecuteJavascript('window.TMSWEBCoreClientIdentifier', true) = 'unknown' then
      FInitialized := True;


After the initialization is complete, the TTMSFNCWebCoreClientBrowser instance performs a handshake. This is being done by executing JavaScript. The HandshakeScript is dynamically being added during the initialization of the TMS WEB Core Application and initializes the TMSWEBCoreClientIdentifier global variable.

  HandShakeScript := TJSHTMLScriptElement(document.createElement('script')); := 'HandShakeScript';
  HandShakeScript.type_ := 'text/javascript';
  HandShakeScript.innerHTML :=
  'var TMSWEBCoreClientIdentifier = "unknown";'+#13#10+
  'function HandShake(cid){'+#13#10+
  '  TMSWEBCoreClientIdentifier = cid;'+#13#10+

  Application := TApplication.Create(nil);

The handshake script is being called from the TTMSFNCWebCoreClientBrowser instance after the initialization is complete.

procedure TTMSFNCCustomWebCoreClientBrowser.PerformHandshake;
  c: string;
  c := 'windows';
  c := 'ios';
  c := 'macos';
  c := 'android';

Sending and receiving messages

When the handshake is complete, the client can send and receive messages. The communication format is a JSON string that is automatically URL encoded and parsed to a JSON object. A sample sending from the client to the TMS WEB Core application:

procedure TForm1.ClientSendButtonClick(Sender: TObject);
  c: TJSONObject;
  c := TJSONObject.Create;
  c.AddPair('Message From Client', 'Hello World !');

And of course, sending back from a TMS WEB Core Application to the client:

procedure TForm1.WebButton1Click(Sender: TObject);
  o: TJSONObject;
  js: TJSON;
  s: string;
  js := TJSON.Create;
  s := '{"Message From TMS WEB Core Application":"'Hello World !"}';
  o := js.parse(s);

The future

This technology opens up a lot of possibilities for the future. You can send and receive messages with plain text, as well as small binary data encoded inside a JSON string between the client and the TMS WEB Core Application. The client application can then interact with the operating system, such as opening files, and other operating system specific functionality. The code runs on FMX (Windows, macOS, iOS, Android) and VCL (Windows) and is coming to TMS WEB Core in the near future!

Read More

Read More

Better Performance with REST Compression

Many Delphi applications, esp. mobile iOS or Android apps, are using REST, to retrieve data from a backend. Often TRESTClient and TRESTRequest are used to get access to an external REST api. There several Blogs and CodeRage videos (including from me), that demonstrate how to do this. Even the Delphi… Read More Der Beitrag Better Performance with REST Compression erschien zuerst auf Developer Experts.
Read More

Visiting the TMS lab day 7: TMS WEB Core testing and exploring

With the ever growing number of TMS WEB Core UI controls we have and the ever growing complexity, testing web UI controls becomes a non-trivial task. Our team clearly has a need to allow an efficient way testing not only by the developer of the UI controls but also by other users. One of the chores for testing a UI control with numerous settings that affect the appearance and the behavior, is that typically an application needs to be developed that will surface all the combinations of settings. And then we are not yet talking about interactions between multiple UI controls. So, we found ourselves both writing a lot of test application code and also going a lot through the cycle of configuring a UI control, compile, run, test and repeat with other configurations.

Out of this laborious experience, the idea for creating a test environment was born. We wanted to have a runtime test environment for the TMS WEB Core components. Wanting the ability to test with every possible property setting of the control and realizing we had in our TMS FNC UI Pack component library an object inspector control, developing this test environment turned out to be faster than we imagined.

After using our test environment for a while now, we realized that this would probably also be interesting for users new to the TMS WEB Core framework. It allows to play with the TMS WEB Core UI Controls directly from the web without the need to install anything. It allows to learn all features and capabilities and discover the rich set of controls meanwhile available that can help you build your web applications. So, we thought of a name for this environment and came up with “Component Explorer”.

During these 2 weeks of visits to the TMS lab, we wanted to show you the experimental version of our Component Explorer. You can use it to explore our TMS WEB Core UI controls, play with it without installing it, experiment and test. And oh, of course we would appreciate if you’d let us know if you find an issue so our team can look into it.

Head to now and discover.

Some notes for your information:

  1. A nice technical detail about the Component Explorer is that it is not a monolithic single-page web application. This means that the Component Explorer consisting of the Object Inspector, designer and component palette dynamically loads the UI control libraries. So, when we develop new UI controls or update the UI controls, this can be done by deploying compiled UI control library JavaScript files to a “component” folder.
  2. Another nice tidbit, is that the Component Explorer is mainly made up of FNC UI controls. The Object Inspector, the design surface, the tool palette, … were all developed with TMS FNC UI Controls. Given that FNC controls can be used for VCL, FMX, LCL and WEB, this means that theoretically, we could also create a desktop Component Explorer versions. In that case it would be limited to exploring FNC controls of course as the native TMS WEB Core UI controls of course cannot be used from VCL, FMX or LCL applications
  3. There is an edit mode and runtime mode. Normally on the design surface, the mouse interacts with the UI controls to move & resize the controls. When unchecking the “Edit Mode” checkbox, we can interact with the UI controls directly with the mouse.
  4. There are still several shortcomings in the Component Explorer. One of these shortcomings is that it is not yet possible to insert controls as child of other controls. All inserted controls are child of the form. So far, for our testing purposes, we could live with this limitation but as our testing becomes more complex (for example testing a ribbon control), this is something high on the priority list.
  5. Although there is already a TStringList property editor, TCollection property editor, there is no mechanism yet for custom property editors. Class properties can be edited by expanding the class and that is in most of our testing scenarios more than sufficient.
  6. In working on integrating testability of our TMS XData backend framework, we discovered a nice side effect that we could create on-the-fly not only a component exploring environment but also a data exploring environment. An example for exploring this, is by dropping a TXDataWebDataSet, TXDataWebConnection, TWebDataSource and TWebDBGrid on the form. Hook the grid to the datasource, the datasource to the dataset and the dataset to the connection. You can use your own XData endpoint or you can use our test endpoint Then set the TXDataWebConnection.Active to true and set TXDataWebDataSet.DesignLoad to true. You can see now the XData data in the TWebDBGrid.

  7. We did use Bootstrap in the Component Explorer, so you can also play with Bootstrap styles. Use the TMS WEB Core UI controls ElementClassName property to assign a fitting Bootstrap class and it should update live. For example, drop a TWebButton on the form and set WebButton.ElementClassName = ‘btn btn-primary’ and you should get a nice looking blue Bootstrap button.

Lab visit feedback & win!

Our team loves to hear what you think about what is brewing in the lab, how you plan to use the upcoming features, what priority our team should give to it and if you have possibly interesting and/or creative ideas to make this even more powerful for Delphi developers. To reward your interaction & feedback, we’ll pick 3 blog comments on October 15 that we liked the most and first prize is a free TMS WEB Core license, the 2nd and 3rd prize is a 50% discount coupon on TMS WEB Core. Let yourself hear to increase your chances!

Get started

Meanwhile, you can go ahead and explore the new & exciting territories of web client development that become available for Delphi developers with TMS WEB Core! You can download the trial version that is generally available, go ahead with the standalone version you purchased or with TMS WEB Core and additional tools that are all included in TMS ALL-ACCESS. Or you can come to see TMS WEB Core and discover and discuss it face to face with Bruno Fierens of showing it in London on October 23, 2018. Note also that in October, you can still take advantage of purchasing TMS WEB Core at launch price from 295EUR for a single developer license. From Nov 1, regular pricing will be active on TMS WEB Core (395EUR for a single developer license).

Read More

Read More