During this webinar we will have several Delphi experts and members of our R&D team showing great technologies using Delphi. I will be there as well showing something that I have been working for a while, the FireMonkey 3D Text Editor, during the webinar I will show you how it was created and share many tips & tricks related with FireMonkey development.

Bellow some screen shots of what I’m planning to show:

3D Text Editor in the IDE

The 3D Text Editor running on Windows, it runs on Mac as well

Image generated by the 3D Text Editor

Related Posts

• Android apps connected to Delphi DataSnap Server
• Using Regular Expression on C++Builder FireMonkey Application
• Using dbExpress Framework on Windows and Mac with C++Builder
• Connecting to PostgreSQL through dbExpress ODBC driver
• Creating XML files with Delphi and FireMonkey on Mac
• Video: Delphi XE2 and FireMonkey app on Windows, Mac and iOS

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

This is a short recap of the video.

In order to have other platforms connecting and interacting with your DataSnap Server you need to enable the REST Interface, and for mobile platforms you can use the DataSnap Connectors that generate proxy classes for Android, BlackBerry, Windows Phone and iOS. In the video I’m showing how to create the Server, let’s take a look at the Server Method implementation.

The first server method called InsertCountry, connect on my InterBase database and add a new record to the Country table, see the implementation below:

function TServerMethods1.InsertCountry(Country, Currency: String;
  out Error: String): Boolean;
var
  Comm: TDBXCommand;
begin

  Result := False;

  DBConn.Open;
  Comm := DBConn.DBXConnection.CreateCommand;
  Comm.CommandType := TDBXCommandTypes.DbxSQL;
  Comm.Text :=
    Format('Insert Into Country (COUNTRY, CURRENCY) Values ( ''%s'', ''%s'')',
    [Country, Currency]);

  if not Comm.IsPrepared then
    Comm.Prepare;

  try
    Comm.ExecuteUpdate;
    Comm.Free;
    Result := True;
  except on E: Exception do
    Error := E.Message;
  end;

end;

The second server method is called GetCountries, and returns all the records I have in the COUNTRY table on my InterBase database. This method returns a DBXReader and DataSnap will convert this automatically to JSON at the moment the Android app calls this method, but since we will use the new DataSnap Connector to generate the proxy class, we won’t need to handle the JSON object and I will explain that after.

The following code represents the GetCountries implementation.

function TServerMethods1.GetCountries: TDBXReader;
var
  Comm: TDBXCommand;
begin

  DBConn.Open;
  Comm := DBConn.DBXConnection.CreateCommand;
  Comm.CommandType := TDBXCommandTypes.DbxSQL;
  Comm.Text := 'Select * from Country';

  if not Comm.IsPrepared then
    Comm.Prepare;

  Result := Comm.ExecuteQuery;

end;

The next step is to create the proxy class for Android using the DataSnap connectors, which is a new feature in Delphi XE2. The generation can be done through command line or via HTTP request on your DataSnap server, and in the video I’m showing how to do that.

The proxy generator generates only the DSProxy.java, all the other files part of the DataSnap Connectors are the representation of DataSnap Framework in Java, for example you won’t need to parse the DBXReader as JSON object in Java, just because we have the DBXReader class in Java and it parses the JSON object for you.

The first step to create a REST connection with your DataSnap Server, which will give me a instance of DSRESTConnection. If your DataSnap Server requires authentication you can use the methods SetUserName and SetPassword to define the credentials.

	private DSRESTConnection getConnection() {
		DSRESTConnection conn = new DSRESTConnection();
		conn.setHost("192.168.254.128");
		conn.setPort(8080);
		return conn;
	}

Now, let’s take a look and see how to execute the server methods, starting with the InsertCountry method as you can see in the following code.

After instantiation of the DSRESTConnection, we pass the REST connection object to the TServerMethods1′s instance, which is the client representation of TServerMethods1 on the server, and from there just call InsertCountry.

Since InsertCountry returns Boolean and also the Error message parameter is passed as reference, InsertCountry methods will return a InsertCountryReturns, which is a static class with two parameters: error that represent the error message and returnValue which represent the value return by InsertCountry.

protected void Insert() {

	DSRESTConnection conn = getConnection();

	TServerMethods1 sm = new TServerMethods1(conn);

	try {
		InsertCountryReturns ret;
		ret = sm.InsertCountry(editCountry.getText().toString(), editCurrency.getText().toString(), "");

		if ( ! ret.returnValue ) {
			System.out.println(ret.error);
		}

	} catch (DBXException e) {
		e.printStackTrace();
	}

	// Hide keyboard
	InputMethodManager imm = (InputMethodManager)getSystemService(Context.INPUT_METHOD_SERVICE);
	imm.hideSoftInputFromWindow(editCountry.getWindowToken(),0);

}

The next method is GetCountries. We start as before by getting the DSRESTConnection instance. The GetCountries method returns a DBXReader and the way we work with the DBXReader class in Java is very similar the way we work in Delphi, use the Next method to interact through the result, and getValue/GetAsXXXXX to get the column value. See the following code:

protected void Refresh() {

	DSRESTConnection conn = getConnection();

	TServerMethods1 sm = new TServerMethods1(conn);

	TDBXReader reader;
	try {
		reader = sm.GetCountries();

		ArrayList COUNTRIES = new ArrayList();

		while (reader.next()) {
			COUNTRIES.add(reader.getValue("COUNTRY").GetAsString());
		}

		// Add the COUNTRIES array in to the list view
		list.setAdapter(new ArrayAdapter(this, android.R.layout.simple_list_item_1, COUNTRIES));

	} catch (DBXException e) {
		e.printStackTrace();
	}

}

This is just a short tutorial explaining how to use DataSnap Connector with Android, take some time and watch the video where I’m going through more details.

The source code is available for download here and download the video from here.

Related Posts

• Video: Connecting Android applications with DataSnap Server – Delphi Conference Brazil 2010
• FireMonkey 3D Text Editor
• Android apps connected to C++Builder DataSnap Server
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”
• Publishing providers when registering DataSnap Server Class in runtime
• Caching data on DataSnap Server

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

Recently I published the White Paper “Reasons to Migrate to Delphi XE2 | What you might have missed since Delphi 7″ and can help you to decide to upgrade to XE2.

Remember, this offer expire on December 30, 2011 and you can have more information here.

It’s time to move on

Related Posts

• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”
• Connecting to PostgreSQL through dbExpress ODBC driver
• Update 2 for Delphi XE2, C++Builder XE2 and RadPHP XE2 available
• Trial, Datasheet, Feature Matrix and FAQ for XE2 release available
• A little bit about FireMonkey and Delphi XE2
• RAD Studio XE2 a new era for Delphi and C++Builder Developers

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

David, Jim and I are here at the Conference talking with customers, community members and our partners.

Related Posts

• FireMonkey 3D Text Editor
• Android apps connected to Delphi DataSnap Server
• It’s time to move on
• White Paper: Reasons to Migrate to Delphi XE2 | What you might have missed since Delphi 7
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”
• Connecting to PostgreSQL through dbExpress ODBC driver

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

If you still using Delphi 7 or past versions, I highly recommend you to reserve sometime to read this article. Delphi has really grown with some truly cool things getting added in the time since the Delphi 7.

This article gives a few good reasons to migrate, along with an overview of all the new features added to Delphi product releases since version 7, where Delphi was an IDE to build Windows 32-bit applications and became an IDE for Windows 64-bit, Mac and iOS development.

If you already read my article “Reasons to migrate from Delphi 7 to Delphi 2009″ or “Reasons to migrate to Delphi XE”, this is the updated version including Delphi 2010, XE and XE2 new features.

I would like to remind you that migrating to Delphi XE2 gives you access to earlier versions at no extra cost. For example buying Delphi XE2 also gets you Delphi 7, Delphi 2007, Delphi 2009, Delphi 2010 and Delphi XE.

I hope this article answer all of your question, any additional question let us know how.

Article download.

Related Posts

• FireMonkey 3D Text Editor
• Android apps connected to Delphi DataSnap Server
• It’s time to move on
• 700 Delphi Developers at Delphi Conference Brazil
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”
• Connecting to PostgreSQL through dbExpress ODBC driver

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

This is no longer a problem, Delphi XE2 Update 2 changed this behavior and now supports Blob fields when using the CopyReaderToClientDataSet method.

To learn how to use the method CopyReaderToClientDataSet read the article “Copying data from ClientDataSet to DBXReader“

Related Posts

• Connecting to PostgreSQL through dbExpress ODBC driver
• Caching data on DataSnap Server
• Copying data from ClientDataSet to DBXReader
• DataSnap videos for 2011 – what would you like to see?
• Registering DataSnap Server Class in runtime with Delphi
• DataSnap XE and Windows Azure – RAD Studio XE Preview #3

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

In order to show how it works, I created a FireMonkey project sample that connect to a PostgreSQL database.

As first step, you must install the PostgreSQL ODBC driver on the machine that will run the application. Second, applications compiled as 32-bit, requires the 32-bit ODBC driver, 64-bit applications will require the 64-bit ODBC driver.

Onde installed the driver, create and configure a User DSN or System DSN on the ODBC Data Source Administrator (odbcad32.exe):

Instructions for windows 64-bit

• For 32-bit applications use c:\Windows\SysWOW64\odbcad32.exe
• For 64-bit applications use o c:\Windows\system32\odbcad32.exe

Instructions for windows 32-bit

• Use  c:\Windows\system32\odbcad32.exe

The next step is to create an dbExpress ODBC alias on Data Explorer, where the Database Name parameter is the name of the Data Source created earlier, in my example the Data Source is called PostgreSQL35W. The database, username and password was already defined in the Data Source, but you can override the username and password parameters through the SQLConnection.

Assuming you already know how to use the SQLConnection, DataSetProvider and ClientDataSet or SimpleDataSet ,and DataSource components, just connect all  the components as you usually do. The SQLConnection will look like this:

  object SQLConnection1: TSQLConnection
    ConnectionName = 'PostgreSQLOdbc'
    DriverName = 'ODBC'
    LoginPrompt = False
    Params.Strings = (
      'drivername=ODBC'
      'Database=PostgreSQL35W')
  end

You can use the dbExpress framework when connected to a database through dbExpress ODBC driver. In XE2 the ODBC driver is compatible with Windows, we are evaluating the possibility to support this driver on Mac.

The figure below shows the FireMonkey application connected to PostgreSQL via dbExpress ODBC driver. Now you can connect to any other other database not supported natively by dbExpress.

Download the source code here.

Related Posts

• Using dbExpress Framework on Windows and Mac with C++Builder
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”
• A little bit about FireMonkey and Delphi XE2
• Video: New dbExpress driver for Firebird in Delphi 2010 and C++Builder 2010
• FireMonkey 3D Text Editor
• Using Regular Expression on C++Builder FireMonkey Application

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

You can download Update 2 for Delphi and C++Builder through the “Check for Updates” option.

RAD Studio XE2 Update 2

• Update 2 for Delphi, C++Builder and RAD Studio XE2 - http://cc.embarcadero.com/item/28597
• Delphi XE2 and C++Builder XE2 ISO (includes Update 2) - http://cc.embarcadero.com/item/28616
• Delphi XE2 and C++Builder XE2 Update 2 Bug Fix List -  http://edn.embarcadero.com/article/41750

RAD Studio XE2 Help Update 1 - http://cc.embarcadero.com/item/28613

RadPHP XE2 Update 2

• Update 2 for RadPHP - http://cc.embarcadero.com/item/28614
• RadPHP XE2 Update 2 Bug Fix List - http://edn.embarcadero.com/article/41756

Related Posts

• Hotfix 2 and Help Update 2 for Delphi XE, C++Builder XE and RAD Studio XE available
• Hotfix 1 for Delphi XE, C++Builder XE and RAD Studio XE available
• Update 1 for Delphi XE and C++Builder XE now available
• RAD Studio 2010 Hotfix 2 available
• It’s time to move on
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

One of the solution for that is to use the Mac API (Cocoa), there are several class and different ways to work with XML on Mac, in this post I’m going to show one way to create an XML file, if you are interested to learn more about the XML class available for Mac, visit the Apple documentation website.

Cocoa provide several classes/interfaces to work with XML, the sample project used on this post use NSXMLDocument, NSXMLElement, NSXMLNode and NSData interfaces and related classes, all of them can be found in the Macapi.Foundation unit.

The NSXMLDocument interface and TNSXMLDocument class are the starting point to create the XML Document, where we define the version and encoding for the XML file.

procedure TFrmXml.CreateXMLButtonClick(Sender: TObject);
var
  XmlDoc: NSXMLDocument;
  Root, Book, Author, Publisher: NSXMLElement;
  Data: NSData;
begin

  // Create Xml Document
  XmlDoc := TNSXMLDocument.Create;
  XmlDoc.setVersion(NSSTR('1.0'));
  XmlDoc.setCharacterEncoding(NSSTR('UTF-8'));

After that we need to define what XML elements (nodes) will be added to the XML, since I’m going to create several elements I created three helper methods (CreateElement and Attribute) to help me with that.

The CreateElement method has two implementations, the first one is very simple, just create a new TNSXMLElement based on the name and value parameters.

function TFrmXml.CreateElement(Name, Value: String): NSXMLElement;
begin
  Result := TNSXMLElement.Create;
  Result.setName(NSSTR(Name));
  Result.setStringValue(NSSTR(Value));
end;

The second CreateElement implementation creates a new element which can contain attributes, in order to pass a NSXMLNode that represent a attribute, we will use the Attribute helper method.

function TFrmXml.CreateElement(Name: String; Attr: NSXMLNode): NSXMLElement;
begin
  Result := TNSXMLElement.Create;
  Result.initWithName(NSSTR(Name));

  if Assigned(Attr) then
    Result.addAttribute(Attr);
end;

Below a short overview about the NSXMLNode class extracted from Apple documentation:

Objects of the NSXMLNode class are nodes in the abstract, logical tree structure that represents an XML document. Node objects can be of different kinds, corresponding to the following markup constructs in an XML document: element, attribute, text, processing instruction, namespace, and comment. In addition, a document-node object (specifically, an instance of NSXMLDocument) represents an XML document in its entirety. NSXMLNode objects can also represent document type declarations as well as declarations in Document Type Definitions (DTDs). Class factory methods of NSXMLNode enable you to create nodes of each kind. Only document, element, and DTD nodes may have child nodes.

Among the NSXML family of classes—that is, the Foundation classes with the prefix “NSXML” (excluding NSXMLParser)—the NSXMLNode class is the base class. Inheriting from it are the classes NSXMLElement, NSXMLDocument, NSXMLDTD, and NSXMLDTDNode. NSXMLNode specifies the interface common to all XML node objects and defines common node behavior and attributes, for example hierarchy level, node name and value, tree traversal, and the ability to emit representative XML markup text.

NSXMLNode could be a comment, text, element and other types in Cocoa, the Attribute helper method ensure we will receive a NSXMLNode of type attribute.

function TFrmXml.Attribute(Name, Value: String): NSXMLNode;
var
  Node: Pointer;
begin
  Node := TNSXMLNode.OCClass.attributeWithName(NSSTR(Name), NSSTR(Value));
  Result := TNSXMLNode.Wrap(Node);
end;

Now is time to use the helper methods to create the XML document and at the end use the NSData object to format and save the XML file. This is what the following code does:

  // Create the root doc element including one attribute
  Root := CreateElement('BookStore', Attribute('url', 'http://www.amazon.com'));
  XmlDoc.initWithRootElement(Root);

  // Create the first Book node
  Book := CreateElement('Book', Attribute('Name', 'Steve Jobs'));

  // Create the Author and Publisher elements
  Author := CreateElement('Author', 'Walter Isaacson');
  Publisher := CreateElement('Publisher', 'Simon Schuster (October 24, 2011)');

  // Add the elements to the XML
  Root.addChild(Book);
  Book.addChild(Author);
  Book.addChild(Publisher);

  // Create the second Book node
  Book := CreateElement('Book', Attribute('Name',
    'Clean Code: A Handbook of Agile Software Craftsmanship'));
  Author := CreateElement('Author', 'Robert C. Martin');
  Publisher := CreateElement('Publisher',
    'Prentice Hall; 1 edition (August 11, 2008)');

  // Add the elements from the second Book node to the XML
  Root.addChild(Book);
  Book.addChild(Author);
  Book.addChild(Publisher);

  // Makes the Xml output more human-readable inserting
  // carriage returns and indenting nested elements
  Data := XmlDoc.XMLDataWithOptions(NSXMLNodePrettyPrint);
  Data.writeToFile(NSSTR(XMLLocation.Text), true);

  XmlContent.Lines.LoadFromFile(XMLLocation.Text);

end;

end.

Here the resulting app on Mac OS X:

You can download the source code directly from the RAD Studio demos repository here.

I originally mention that TXMLDocument was not available for Mac, and this is incorrect, thanks Chris Rolliston for the heads up and to migrate my sample to TXMLDocument.

When you drop a TXMLDocument component on your design the default DOMVendor MSXML, you have to change to ADOM XML v4 to support cross-platform. In case you have the unit Xml.Win.msxmldom added on your form you won’t be able to compile for Mac, after you set the DOMVendor to ADOM XML v4 remove that unit from your code and everything will be fine.

Here the version using TXMLDocument:

unit MainForm;

interface

uses
  System.SysUtils, System.Types, System.UITypes, System.Classes,
  System.Variants, XML.XMLDoc, FMX.Dialogs,
  FMX.Types, FMX.Controls, FMX.Forms, FMX.Layouts,
  FMX.Memo, FMX.Edit, FMX.Effects, FMX.Objects, Xml.xmldom, Xml.XMLIntf;

type
  TFrmXml = class(TForm)
    CreateXMLButton: TButton;
    XmlContent: TMemo;
    XMLLocation: TEdit;
    Label1: TLabel;
    Image1: TImage;
    procedure CreateXMLButtonClick(Sender: TObject);
    procedure FormCreate(Sender: TObject);
  end;

var
  FrmXml: TFrmXml;

implementation

{$R *.fmx}

procedure TFrmXml.CreateXMLButtonClick(Sender: TObject);
var
  XmlDoc: IXMLDocument;
  Root, Book, Author, Publisher: IXMLNode;
begin
  // Create Xml Document
  XmlDoc := TXMLDocument.Create(nil);
  XmlDoc.Active := True;
  XmlDoc.Options := XmlDoc.Options + [doNodeAutoIndent];
  XmlDoc.Version := '1.0';

  // Create the root doc element with one attributes
  Root := XmlDoc.CreateNode('BookStore');
  Root.Attributes['url'] := 'http://www.amazon.com';
  XmlDoc.DocumentElement := Root;

  // Create the first Book node
  Book := XmlDoc.CreateNode('Book');
  Book.Attributes['Name'] := 'Steve Jobs';

  // Create the Author and Publisher elements
  Author := XmlDoc.CreateNode('Author');
  Author.Text := 'Walter Isaacson';
  Publisher := XmlDoc.CreateNode('Publisher');
  Publisher.Text := 'Simon Schuster (October 24, 2011)';

  // Add the elements to the XML
  Root.ChildNodes.Add(Book);
  Book.ChildNodes.Add(Author);
  Book.ChildNodes.Add(Publisher);

  // Create the second Book node
  Book := XmlDoc.CreateNode('Book');
  Book.Attributes['Name'] := 'Clean Code: A Handbook of Agile Software Craftsmanship';
  Author := XmlDoc.CreateNode('Author');
  Author.Text := 'Robert C. Martin';
  Publisher := XmlDoc.CreateNode('Publisher');
  Publisher.Text := 'Prentice Hall; 1 edition (August 11, 2008)';

  // Add the elements from the second Book node to the XML
  Root.ChildNodes.Add(Book);
  Book.ChildNodes.Add(Author);
  Book.ChildNodes.Add(Publisher);

  XmlDoc.SaveToFile(XMLLocation.Text);

  XmlContent.Lines.LoadFromFile(XMLLocation.Text);

end;

procedure TFrmXml.FormCreate(Sender: TObject);
begin
  XMLLocation.Text := IncludeTrailingPathDelimiter(GetHomePath) + 'create.xml';
end;

end.

With this you have everything you need to manipulate XML file on Windows and Mac.

Related Posts

• FireMonkey 3D Text Editor
• Connecting to PostgreSQL through dbExpress ODBC driver
• Video: Delphi XE2 and FireMonkey app on Windows, Mac and iOS
• A little bit about FireMonkey and Delphi XE2
• Android apps connected to Delphi DataSnap Server
• Using Regular Expression on C++Builder FireMonkey Application

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

The solution for this issue is very simple, we just need to register the TDSProviderDataModuleAdapter class, which is used internally to allow a TProviderDataModule to be exposed to DataSnap clients. TDSProviderDataModuleAdapter acts as a proxy between a server-side TProviderDataModule and client-sides TDSProviderConnection.

We could just update the GetDSClass method implementation as below, it works, but it would not be the best implementation, just because the following code will always publish the IAppServer interface methods to the client side, in case your ServerModule doesn’t have any Provider, why you will publish the IAppServer? Doesn’t make sense, right?

Making the publication parameterizable will bring more flexibility and control to the application and the developer, it will be your decision to publish the Providers or not. A new parameter in the TSimpleServerClass constructor is everything we need.

function TSimpleServerClass.GetDSClass: TDSClass;

begin
  Result := TDSClass.Create(FPersistentClass, False);
  Result := TDSClass.Create(TDSProviderDataModuleAdapter, Result)
end;

The following code represents the new implementation for the TSimpleServerClass. The change adds a new parameter (ExposeProvider) to the constructor, which will allow the developer to publish the providers (or not).

type

unit SimpleServerClass;

interface

uses DSServer, Classes, DSCommonServer, DSReflect;

type

  TSimpleServerClass = class(TDSServerClass)
  private
    FPersistentClass: TPersistentClass;
    FExposeProvider : Boolean;
  protected
    function GetDSClass: TDSClass; override;
  public
    constructor Create(AOwner: TComponent; AServer: TDSCustomServer;
      AClass: TPersistentClass; ExposeProvider: Boolean; ALifeCycle: String);
      reintroduce; overload;
  end;

implementation

constructor TSimpleServerClass.Create(AOwner: TComponent;
  AServer: TDSCustomServer; AClass: TPersistentClass; ExposeProvider: Boolean;
  ALifeCycle: String);
begin
  inherited Create(AOwner);
  FPersistentClass := AClass;
  FExposeProvider  := ExposeProvider;
  Self.Server := AServer;
  Self.LifeCycle := ALifeCycle;

end;

function TSimpleServerClass.GetDSClass: TDSClass;
var
  isAdapted : Boolean;
begin
  isAdapted := FPersistentClass.InheritsFrom(TProviderDataModule);
  Result := TDSClass.Create(FPersistentClass, isAdapted);
  if FExposeProvider and isAdapted then
     Result := TDSClass.Create(TDSProviderDataModuleAdapter, Result)
end;

end.

The following code registers 3 classes, where only one exposes the Providers:

procedure RegisterServerClasses(AOwner: TComponent; AServer: TDSServer);
begin
  Assert(AServer.Started = false, 'Can''t add class to non active Server');

  TSimpleServerClass.Create(AOwner, AServer, TGlobal, False, TDSLifeCycle.Server);
  TSimpleServerClass.Create(AOwner, AServer, TCustomer, True, TDSLifeCycle.Session);
  TSimpleServerClass.Create(AOwner, AServer, TObjectPool, False, TDSLifeCycle.Invocation);
end;

Related Posts

• Android apps connected to Delphi DataSnap Server
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”
• Caching data on DataSnap Server
• Copying data from ClientDataSet to DBXReader
• Video: Connecting Android applications with DataSnap Server – Delphi Conference Brazil 2010
• DataSnap videos for 2011 – what would you like to see?

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

The following text is an email from Digital Metaphors, which include all the information about this new release.

Subject: Digital Metaphors Corporation announces the release of ReportBuilder 14.0!

ReportBuilder 14.0 includes VCL support for Delphi XE2, Delphi XE, Delphi 2010, 2009, 2007, 2006, and Delphi 7.

Overview: http://www.digital-metaphors.com/rbwiki/General/What’s_New/RB_14

New Feature List: http://www.digital-metaphors.com/PDF/NewFeatures.pdf

Pricing: http://www.digital-metaphors.com/order

Upgrade here! https://www.digital-metaphors.com/secure

Version 14.0 – 10/21/2011
————————-
- Delphi XE2 support for VCL Win32
- Delphi XE2 support for VCL Win64

Design Layers
————-
- separate layout elements into logical layers
- load/save design layers (example std header/footer or watermark)
- prevent users from adding, selecting, moving, deleting elements
- prevent users from seeing, selecting, deleting layers
- LayerTypes: Band, Page
- Inactive Layers draw alpha blended behind active layer
- ComponentOptions: Add, Delete, Select, Move
- LayerOptions: Select, Rename, Visible, Delete, Load, Save

Preview
——-
- continuous page scrolling
- single and two-up page display
- background thread report generation
- hand scrolling
- PreviewFormSetings.PageDisplay property
- PreviewFormSettings.PageIncrement propery (control page generation)
- PreviewFormsSettings.SinglePageOnly (forces use of old screen device)
- Viewer.DeadSpace property (control amount of space outside of page)

Output Devices
————–
- HTML file device
- PDF/A device (http://en.wikipedia.org/wiki/PDF/A)
- PDFSettings.PDFA boolean property (force PDF to PDF/A standard)
- PDF image compression (automatic jpeg compression)
- PDF image scaling (PDFSettings.ImageCompressionLevel)
- PDF, high quality metafile to bitmap conversion
- DocForm device (exact positioning of lines and text)
- RTFSettings.UseTextBoxes boolean property (exact text positioning)
- RTF/Doc device, support for CodePage and Font.CharSet
- XLS support for AppName, Author, Subject, Title (XLSSEttings)
- Email, Extended Mapi plug-in
- avoid security warnings, Unicode and Html support
- Email, support for HTML messages via Indy 10 Extended Mapi
- Email, EmailSettings.HtmlBody, BodyHtmlAttachments properties
- Email, EmailSettings.StreamAttachments option
- Email, Unicode message body (Unicode VCL w/Indy 10 or Extended Mapi)
- new ScrollableScreenDevice, used by Viewer to implement continuous scrolling
- PrintToFile enhancements
- DefaultFileDeviceType defaults to PDF
- default TextFileName, ArchiveFileName ($MyDocuments)\Report.pdf
- Change default file device, auto-changes default file name
- change output format in print dialog, auto-changes default file name
- support for wildcards in default FileName, ($MyDocuments) is resolved
by print dialog for display to end-user
- change the extension in the print dialog, changes the file

International Language support
——————————
- added 64-bit language modules

TeeChart support
—————-
- enhanced TeeChart Package Builder for 64-bit

RCL
—
- Variable support for Int64 via dtLargeInt data type
- Groups, PreventOrphans
- prevent group header with no detail at bottom of page
- prevent group footer with no detail at top of page
- Columns, ColumnBalancing
- generate vertical columns in min number of rows
- ColumnFooter, AlignToBottom boolean
- enables column footer to generate immediately after detail
- Band.Background property for all bands
- DrawCommand.AsMetaFile feature for simpler RCL add-on support
- SummaryBand enhanced to print on same page as columns

Engine
——
- enhanced group generation – PreventOrphans management
- enhanced horizontal and vertical Column generation

EndUser
——-
- DesignLayers
- LayerOptions: use to lock layers, hide layers
- for example, create a visible/invisible water mark layer
- ComponentOptions: prevent users from moving, deleting etc.
- new OnCustomSaveQueryDoc event
- new ShowHelp method – fires Designer.OnHelp event
- ReportExplorer, invokes Help via new Designer.ShowHelp

RAP
—
- new Int64 data type
- compiler/parser support for // comments
- enhanced object ref scoping: childreport can access parent report objects
- File functions: FileExists, DirectoryExists, ExtractFileName, etc.
- RTTI for PrintDialog
- RTTI for FileDevice
- RTTI for ObjectList
- RTTI enhanced for Picture, Graphic
- enhanced run-time exception message to display subreport name

Server
——
- added 64-bit windows service (ReportBuilder Services)

*features may vary by ReportBuilder Edition and Delphi version
*RB 14 includes support for seven Delphi versions:
D7, D2006. D2007, D2009, D2010, DXE, DXE2.

Related Posts

• FireMonkey 3D Text Editor
• Android apps connected to Delphi DataSnap Server
• It’s time to move on
• 700 Delphi Developers at Delphi Conference Brazil
• White Paper: Reasons to Migrate to Delphi XE2 | What you might have missed since Delphi 7
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

Creating the CloudUpload Shell Extension

In order to start creating a Shell Extension in Delphi, you first need to create an ActiveX Library project and after that create a new Automation Object. In the example I use for this post, the project name is CloudUpload and the Automation Object is called TCloudUploadContext. The TCloudUploadContext class must implement the interfaces IShellExtInit and IContextMenu in order to integrate the Context Menu in Windows Explorer.

    { IShellExtInit Methods }
    { Initialize the context menu if a files was selected}
    function IShellExtInit.Initialize = ShellExtInitialize;
    function ShellExtInitialize(pidlFolder: PItemIDList; lpdobj: IDataObject;
      hKeyProgID: HKEY): HResult; stdcall;

    { IContextMenu Methods }
    { Initializes the context menu and it decides which items appear in it,
      based on the flags you pass }
    function QueryContextMenu(Menu: HMENU; indexMenu, idCmdFirst, idCmdLast,
      uFlags: UINT): HResult; stdcall;

    { Execute the command, which will be the upload to Amazon or Azure}
    function InvokeCommand(var lpici: TCMInvokeCommandInfo): HResult; stdcall;
    { Set help string on the Explorer status bar when the menu item is selected }
    function GetCommandString(idCmd: UINT_PTR; uFlags: UINT; pwReserved: PUINT;
      pszName: LPSTR; cchMax: UINT): HResult; stdcall;

The ShellExtInitialize defines if the Context Menu will appear or not in Windows Explorer. In this sample the context menu only shows up if one file has been selected, otherwise no Context Menu. In case only one file was selected the FFileName variable will receive the name of the file.

function TCloudUploadContextMenu.ShellExtInitialize(pidlFolder: PItemIDList;
  lpdobj: IDataObject; hKeyProgID: HKEY): HResult;
var
  DataFormat: TFormatEtc;
  StrgMedium: TStgMedium;
  Buffer: array [0 .. MAX_PATH] of Char;
begin
  Result := E_FAIL;

  { Check if an object was defined }
  if lpdobj = nil then
    Exit;

  { Prepare to get information about the object }
  DataFormat.cfFormat := CF_HDROP;
  DataFormat.ptd := nil;
  DataFormat.dwAspect := DVASPECT_CONTENT;
  DataFormat.lindex := -1;
  DataFormat.tymed := TYMED_HGLOBAL;

  if lpdobj.GetData(DataFormat, StrgMedium) <> S_OK then
    Exit;

  { The implementation now support only one file }
  if DragQueryFile(StrgMedium.hGlobal, $FFFFFFFF, nil, 0) = 1 then
  begin
    SetLength(FFileName, MAX_PATH);
    DragQueryFile(StrgMedium.hGlobal, 0, @Buffer, SizeOf(Buffer));
    FFileName := Buffer;
    Result := NOERROR;
  end
  else
  begin
    // Don't show the Menu if more then one file was selected
    FFileName := EmptyStr;
    Result := E_FAIL;
  end;

  { http://msdn.microsoft.com/en-us/library/ms693491(v=vs.85).aspx }
  ReleaseStgMedium(StrgMedium);

end;

After the context menu handler is initialized via the IShellExtInit interface, Windows uses the IContextMenu interface to call the other methods of our context menu handler. In this case it will call QueryContextMenu, GetCommandString and InvokeCommand.

The Context Menu options (Amazon S3, Microsoft Azure) will be created through the QueryContextMenu method.

function TCloudUploadContextMenu.QueryContextMenu(Menu: HMENU;
  indexMenu, idCmdFirst, idCmdLast, uFlags: UINT): HResult;
var
  CloudMenuItem: TMenuItemInfo;
  MenuCaption: String;
  SubMenu: HMENU;
  uId: UINT;
begin
  { only adding one menu CloudMenuItem, so generate the result code accordingly }
  Result := MakeResult(SEVERITY_SUCCESS, 0, 3);

  { store the menu CloudMenuItem index }
  FMenuItemIndex := indexMenu;

  { specify what the menu says, depending on where it was spawned }
  if (uFlags = CMF_NORMAL) then // from the desktop
    MenuCaption := 'Send file from Desktop to the Cloud'
  else if (uFlags and CMF_VERBSONLY) = CMF_VERBSONLY then // from a shortcut
    MenuCaption := 'Send file from Shourtcut to the Cloud'
  else if (uFlags and CMF_EXPLORE) = CMF_EXPLORE then // from explorer
    MenuCaption := 'Send file from Explorer to the Cloud'
  else
    { fail for any other value }
    Result := E_FAIL;

  if Result <> E_FAIL then
  begin

    SubMenu := CreatePopupMenu;

    uId := idCmdFirst;
    InsertMenu(SubMenu, AmazonIndex, MF_BYPOSITION, uId, TClouds[AmazonIndex]);

    Inc(uId);
    InsertMenu(SubMenu, AzureIndex, MF_BYPOSITION, uId, TClouds[AzureIndex]);

    FillChar(CloudMenuItem, SizeOf(TMenuItemInfo), #0);
    CloudMenuItem.cbSize := SizeOf(TMenuItemInfo);
    CloudMenuItem.fMask := MIIM_SUBMENU or MIIM_STRING or MIIM_ID;
    CloudMenuItem.fType := MFT_STRING;
    CloudMenuItem.wID := FMenuItemIndex;
    CloudMenuItem.hSubMenu := SubMenu;
    CloudMenuItem.dwTypeData := PWideChar(MenuCaption);
    CloudMenuItem.cch := Length(MenuCaption);

    InsertMenuItem(Menu, indexMenu, True, CloudMenuItem);
  end;
end;

When you are in the Windows Explorer and you pass the mouse over one of the Cloud menu items a short help message is displayed in the Windows Explorer status bar, it is defined on the implementation of the method GetCommandString, which returns a string to the Windows Explorer to display.

function TCloudUploadContextMenu.GetCommandString(idCmd: UINT_PTR; uFlags: UINT;

  pwReserved: PUINT; pszName: LPSTR; cchMax: UINT): HResult;
begin
  Result := E_INVALIDARG;

  { Set help string on the Explorer status bar when the menu item is selected }
  if (idCmd in [AmazonIndex, AzureIndex]) and (uFlags = GCS_HELPTEXT) then
  begin
    StrLCopy(PWideChar(pszName), PWideChar('Copy the selected file to ' +
      TClouds[idCmd]), cchMax);
    Result := NOERROR;
  end;

end;

As the user clicks in one of the Cloud menu items, the method InvokeCommand will be called and start the process to upload the selected file to the Cloud selected. At this point we already have the file name and based on the lpici parameters we can identify what menu item the user clicked.

function TCloudUploadContextMenu.InvokeCommand(var lpici: TCMInvokeCommandInfo): HResult;
var
  Item: Word;
begin
  Result := E_FAIL;

  if HiWord(Integer(lpici.lpVerb)) <> 0 then
    Exit;

  { if the index matches the index for the menu, show the cloud options }
  Item := LoWord(Integer(lpici.lpVerb));

  if Item in [AmazonIndex, AzureIndex] then
  begin
    try
      Upload(lpici.HWND, Item, FFileName);
    except
      on E: Exception do
        MessageBox(lpici.hwnd, PWideChar(E.Message), 'Cloud Upload', MB_ICONERROR);

    end;
    Result := NOERROR;
  end;

end;

In order for the COM object to be created whenever the CloudUpload is loaded, it’s necessary to create an instance of a class factory that specifically creates an instance of the shell extension object, the factory instance will be created on the initialization section, based on the following code, which is a replacement for the default code created by Delphi.

initialization
  TCloudUploadObjectFactory.Create(ComServer, TCloudUploadContextMenu, CLASS_CloudUploadContextMenu, ciMultiInstance, tmApartment);
end.

Since the class factory will be responsible to register/unregister the DLL, the methods ApproveShellExtension and UpdateRegistry will be invoked, it will happen when you use the regsvr32.exe.

  { the new class factory }
  TCloudUploadObjectFactory = class(TAutoObjectFactory)
  protected
    procedure ApproveShellExtension(&Register: Boolean; const ClsID: string);
    function GetProgID: string; override;
  public
    procedure UpdateRegistry(Register: Boolean); override;
  end;

{ TCloudUploadObjectFactory }

{ Required to registration for Windows NT/2000 }
procedure TCloudUploadObjectFactory.ApproveShellExtension(&Register: Boolean;
  const ClsID: string);
Const
  WinNTRegKey =
    'SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved';
var
  Reg: TRegistry;
begin
  Reg := TRegistry.Create;

  try
    Reg.RootKey := HKEY_LOCAL_MACHINE;

    if not Reg.OpenKey(WinNTRegKey, True) then
      Exit;

    { register the extension appropriately }
    if &Register then
      Reg.WriteString(ClsID, Description)
    else
      Reg.DeleteValue(ClsID);
  finally
    Reg.Free;
  end;

end;

function TCloudUploadObjectFactory.GetProgID: string;
begin
  { ProgID not required for shell extensions }
  Result := '';
end;

procedure TCloudUploadObjectFactory.UpdateRegistry(Register: Boolean);
Const
  ContextKey = '*\shellex\ContextMenuHandlers\%s';
begin
  { perform normal registration }
  inherited UpdateRegistry(Register);

  { Registration required for Windows NT/2000 }
  ApproveShellExtension(Register, GUIDToString(ClassID));

  { if this server is being registered, register the required key/values
    to expose it to Explorer }
  if Register then
    CreateRegKey(Format(ContextKey, [ClassName]), '', GUIDToString(ClassID),
      HKEY_CLASSES_ROOT)
  else
    DeleteRegKey(Format(ContextKey, [ClassName]));

end;

Compile for 32-bit or 64-bit platform

At this point we just need to compile the extension, for this sample the Win APIs and RTL methods are the same for both platforms, we don’t need any specific code. You can define the target platform through the Project Manager, by default your project target 32-bit Windows, right click on Target Platforms to add 64-bit Windows.

You can’t register 32-bit dll in 64-bit operation system, and you can not register 64-bit dll in 32-bit operation system. If you are using your develop machine to test, compile for the platform compatible with your OS.

Registering the CloudUpload Shell Extension

First, you must Run as Administrator the application you are going to use to register the shell extensions even if you are the Administrator user.

32-bit shell extensions can be registered through the IDE, and command line (cmd) can be used to register 32-bit and 64-bit.

Here the cmd line to register and unregister:

- Run as Administrator the cmd;

- Register the extension using the following command line: regsvr32 <PATH WHERE IS LOCATED THE DLL>CloudUpload.dll

- To unregister the extension using the following command line: regsvr32 <PATH WHERE IS LOCATED THE DLL>CloudUpload.dll /u

After register the DLL you can open the Windows Explorer, select one file and right click, you will see the new menu “Send file from Explorer to the Cloud”. The following screenshot show the shell extension on my Windows 7 64-bit.

You can download he source code in 2 different ways:

• Use the RAD Studio XE2 IDE menu File option “Open from Version Control” and set the URL to https://radstudiodemos.svn.sourceforge.net/svnroot/radstudiodemos/branches/RadStudio_XE2/Delphi/CloudAPI/CloudUpload
• Update your RAD Studio XE2 local demo repository, in case you use TortoiseSVN just right click on the C:\Users\Public\Documents\RAD Studio\9.0\Samples\Delphi folder and select update;

Related Posts

• Microsoft Windows Azure during 30 days FREE
• Test our DataSnap XE Live Server on Amazon Cloud
• DataSnap XE and Windows Azure – RAD Studio XE Preview #3
• FireMonkey 3D Text Editor
• Amazon Web Services (AWS) is the first choice for PHP Developers
• Android apps connected to Delphi DataSnap Server

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

The certification program tests your knowledge in Delphi, we recommend you to use Delphi XE or XE2 release in order to be prepared to answers questions related with the IDE, generics, anonymous methods, DataSnap, unicode, and other areas, which was implemented/improved after 2009 releases.

The Delphi Certification program allows you to distinguish yourself from all the other professionals in this increasingly competitive marketplace.

Related Posts

• Delphi Developer Certification Tips #3
• Video: Delphi Certification Webinar Replay
• FREE Delphi Certification for Delphi XE and RAD Studio XE registered users
• Delphi Developer Certification Tips #2
• Delphi Developer Certification Tips #1
• Delphi Certification Program – Official Announcement

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

We plan to have the web site live with all the new product information soon. The official announcement press releases for the tools and FireMonkey will go out then. We thought would be great to let you know that you can get the software a little early. Enjoy!

Related Posts

• RAD Studio XE2 a new era for Delphi and C++Builder Developers
• Available now the new Delphi XE, C++Builder XE, Delphi Prism XE and RadPHP XE
• DataSnap XE and Windows Azure – RAD Studio XE Preview #3
• RAD Studio XE = Delphi XE, C++Builder XE, Delphi Prism XE and RadPHP XE
• Agile Development = Delphi XE + C++Builder XE + Delphi Prism XE + RadPHP XE
• It’s time to move on

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

I know you are curious to see all of the great stuffs coming on RAD Studio XE2 and to give you an idea; I prepared a 5 minutes preview video. It shows a Delphi XE2 HD FireMonkey application running on Windows (64-bit), Mac and iOS, the use of 3D components and animations.

There are lot of possibilities with FireMonkey and all of the other new features in Rad Studio XE2, we are presenting all of them during the World Tour, reserve some time and register for the World Tour near you.

Register today for the RAD Studio XE2 World Tour

Related Posts

• FireMonkey 3D Text Editor
• Connecting to PostgreSQL through dbExpress ODBC driver
• Creating XML files with Delphi and FireMonkey on Mac
• A little bit about FireMonkey and Delphi XE2
• Video: Delphi Certification Webinar Replay
• Video: Delphi Conference 2010 Brazil Opening Keynote with David I

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

Components in FireMonkey are containers; it means you can embed any component inside any other component. Just to give you an idea, the Button component is composed of 9 components. When together, they look and behave like a Button, let’s see how it works.

Starts with a TLayout component, which helps to organize all of the controls
Three TRectangle are responsible for the button look and feel, like: border, background and foreground color
A Label represents the Button text
And ends with four components, two for animation and other two for effects. Why effects and animations? Animations will happen when you move the mouse over/out the button, effects will happen when button is pressed or has a focus, the glow effect is responsible for that.

As you can see, a number of different features has been used to create a button, this is what happen with all of FireMonkey components.

And one more think, components’ look and feel can be changed and reused using Styles. Imagine a web page that use CSS, you change the web page look and feel just updating the CSS, right? In FireMonkey is the same, instead CSS you will use Styles to change the application look and feel.

Apps and components look and work properly on the respective native platform, but you can also style them to look or behave differently. below an example.

More to come, stay tuned to this blog, other Embarcadero blogs and Embarcadero web site.

Register today for the RAD Studio XE2 World Tour

Related Posts

• Connecting to PostgreSQL through dbExpress ODBC driver
• FireMonkey 3D Text Editor
• Using Regular Expression on C++Builder FireMonkey Application
• Using dbExpress Framework on Windows and Mac with C++Builder
• It’s time to move on
• CopyReaderToClientDataSet, Blob and the message “Feature not implemented”

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

This release represents a new era for Delphi and C++Builder developers, there are lot of new stuffs on this release and we will show all of them during the RAD Studio XE Tour, in the mean time I would like to highlight some of them:

New Delphi for 64-bit Windows and full VCL/RTL support
Full monitoring and controlling of DataSnap connections
LiveBinding, the new mechanism for binding any type of data
dbExpress ODBC driver
Cloud API support for Amazon S3
VCL Styles to modernize the look and feel of VCL applications
FireMonkey the new platform for NATIVE software development

FireMonkey is a big step forward, it opens a whole new market for Delphi and C++Builder developers, allowing to offer their current applications on Mac, develop new products and at the end deploy their applications through App Store reaching millions of end users. The power of FireMonkey will distinguish your applications from any other.

Much more to come, stay tuned to this blog, other Embarcadero blogs and our Embarcadero website throughout this month for more information.

Register today for the RAD Studio XE2 World Tour

Related Posts

• Trial, Datasheet, Feature Matrix and FAQ for XE2 release available
• Available now the new Delphi XE, C++Builder XE, Delphi Prism XE and RadPHP XE
• DataSnap XE and Windows Azure – RAD Studio XE Preview #3
• RAD Studio XE = Delphi XE, C++Builder XE, Delphi Prism XE and RadPHP XE
• Agile Development = Delphi XE + C++Builder XE + Delphi Prism XE + RadPHP XE
• It’s time to move on

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

Exceptions are exceptional conditions that require special handling; the exception handling provides a standard way of dealing with errors. Using exception handling you will be able to manage errors when it happen and decide what to do.

The RAD Studio documentation has a specific topic about Exception Handling, take sometime and read this topic, it will help you to answer the exam questions related with exceptions.

You may think because you use try..except..end, you know enough to answer the exam questions, I would say NO. Since we have a large pool of questions, the exam will ask you about different aspects of exception handling, like: Re-raising Exceptions, Silent Exceptions and more.

Silent Exceptions is a way to raise a exception without showing the error message, while the regular exception show the error message, but is not only this.

• Silent exceptions all descend from the standard exception type EAbort.
• Delphi has a procedure called Abort, which automatically call raise a EAbort exception

function GetFileList(const Path: string): TStringList;
var
  I: Integer;
  SearchRec: TSearchRec;
begin
  Result := TStringList.Create;
  try
    I := FindFirst(Path, 0, SearchRec);
    while I = 0 do
    begin
      Result.Add(SearchRec.Name);
      I := FindNext(SearchRec);
    end;
  except
    FindClose(SearchRec);
    Result.Free;
    raise;
  end;
end;

GetFileList creates a TStringList object, and then uses the FindFirst and FindNext functions to initialize it. If the initialization fails – for example because the search path is invalid, or because there is not enough memory to fill in the string list – GetFileList needs to dispose of the new string list, since the caller does not yet know of its existence. For this reason, initialization of the string list is performed in a try…except..statement. If an exception occurs, the statement’s exception block disposes of the string list, then re-raises the exception.

The exam goes beyond of the two aspects mentioned here. The following three links will help you to learn more about exception handling:

• RAD Studio documentation – Exception Handling
• Delphi Basic – Exception handling in your code
• Delphi Basic – Raise

Related Posts

• Delphi Certification Program and Delphi XE2 release
• Video: Delphi Certification Webinar Replay
• FREE Delphi Certification for Delphi XE and RAD Studio XE registered users
• Delphi Developer Certification Tips #2
• Delphi Developer Certification Tips #1
• Delphi Certification Program – Official Announcement

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

Presentation Slides

Webinar Replay

All the Certification Program information is available at the Certification Center, as well as the study guides and FAQ.

• Delphi Developer
• Delphi Master Developer
• Certification FAQs
• Free Exam Offer for Delphi XE and RAD Studio XE Users
• Purchase an Exam Code – here
• Contact a Delphi Certification Center to take the Delphi Master Developer Certification exam, find one here

Related Posts

• Delphi Certification Program and Delphi XE2 release
• Video: Delphi XE2 and FireMonkey app on Windows, Mac and iOS
• Delphi Developer Certification Tips #3
• FREE Delphi Certification for Delphi XE and RAD Studio XE registered users
• Delphi Developer Certification Tips #2
• Delphi Developer Certification Tips #1

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse

Congratulations for the Delphi-Treff team.

Related Posts

• Free eBook Delphi XE Starter Essentials by Bob Swart
• Delphi 2009 Handbook translation for Portuguese “Recursos Avançados do Delphi”
• FireMonkey 3D Text Editor
• Android apps connected to Delphi DataSnap Server
• It’s time to move on
• 700 Delphi Developers at Delphi Conference Brazil

Andreano Lanusse | Technology and Software Development
Follow me on Twitter: @andreanolanusse