Difference between revisions of "LMD NG 2015 - News"

Latest revision as of 13:51, 18 August 2017

<< Back to Getting started page

[edit]

General

The new Next Generation (NG) Control Suite supplements the LMD line of products for Embarcadero Delphi/C++Builder. While LMD VCL products still (now and in the future) support legacy IDEs (Delphi/C++Builder 6 and higher), NG components make use of new IDE and language features of most recent IDE releases (Delphi/C++Builder 2009 and above). This approach allows us to neglect compatibility issues (e.g. Unicode and Generics support) and to use ideas which are not possible with older IDEs.
Besides that NG Controls are designed to be lightweight and task-focused. They do not represent a complete framework like the LMD VCL platform and can be used at the same time with LMD VCL controls, the VCL (and later FMX) or any other 3rd Party toolbox. [Top]

Support for IDEs and operating systems

• Compatible with Delphi and C++ Builder XE2 - XE7, including 64bit support for XE2 and higher! The next Delphi/C++Builder release will be supported almost immediately after public availability.
• Supported IDEs
  • Delphi 2009, 2010, XE, XE2, XE3, XE4, XE5, XE6, XE7, XE8 (depending on package)
  • C++ Builder 2009, 2010, XE, XE2, XE3, XE4, XE5, XE6, XE7, XE8 (depending on package)
  • All corresponding Studio Products (CRS 2009, RAD Studio 2010, XE, XE2, XE3 etc.)
• Supported operating systems
  • Win 2000 or better (including Windows 7 + 8).

In current releases VCL only is (actively) supported. However for all pacckages support of FMX is in preparation (exceptions are e.g. windows only related features like the native TaskDialog implementation).

64bit support (Delphi XE2 and higher)

All packages are available in 64bit versions.
[Top]

NG ConnectionPack (XE and higher only)

[Top]

NG SerializerPack (XE and higher only)

NG SerializerPack provides the ability to serialize/de-serialize Delphi objects into various storage formats. Any public (not only published!) property can be automatically handled by the engine. This allows to write data applications in a more object oriented and simpler way. NG SerializerPack uses enhanced RTTI features and supports latest features of Delphi/C++Builder runtime (like e.g. Generics).
Common use cases of a serialization engine are:

• Saving/loading application options / configuration data which are represented by typed objects.
• Sending business objects via net between client and server.
• Saving/loading CAD-like application documents, since they are usually represented at runtime in a tree-like object model.
• XML-support for additional 3rd party library (NativeXML) - now 3 different XML providers are supported.
• NEW: JSON support. Either via Delphi built in JSON access (e.g. TJSONValue) or 3rd party (SuperObject).
• NEW: Skipping of unknown members / advanced error handling during de-serialization process is now available.
• TDeserializer.SkipValue and TBinaryData.SkipAll methods has been added to allow users skip values while manual de-serialization. Corresponding protected method has been implemented in all supported formats. Skipping data has been optimized for speed in a binary format.
• OnMemberNotFound event has been added to TDeserializer class, which is executed when RTTI-based de-serialization process is unable to find de-serializing member.
• SkipAllAttribute and SkipMemberAttribute has been introduced. They are designed to be used as type level attributes, and allows to specify, which member names to skip without exception while de-serializing.

See also: NG SerializerPack Guide and NG SerializerPack Reference.

Demos

Demo folder: serialization\delphi
serialization
A very extensive demo project which demonstrates a common use of NG Serialization Pack: Transmitting business objects between client and server applications. An extensive object model is created and usage of many supported attributes and creation of converter classes are demonstrated.
web-service
A web service demo which loads and transfers data from the Jamendo music platform directly via REST into defined TAlbum and TTrack classes.
simple
Simple demo which demonstrates simplicity of (de-)serializing generic TObject and TObjectList descendants from/to XML files (XMLDocument).
json
Simple demo like before using the DBXJSON class (included with Delphi).
super-object
Simple demo like before using SuperObject JSON library (3rd party).
native-xml
Simple demo like before using Native-XML.
omni-xml
Simple demo like before using OmniXML.
[Top]

NG HTMLPack

A set of lightweight controls for HTML display (supporting a subset of HTML tags). Advanced functionality like support of variables, internal controls, DB templates, images etc. is included.
Click on images below for more info.

• 

  What's new

• 

  Format tags

• 

  HTML ListBox

Controls

• Non-DB Controls
  • TNGHTMLLabel
  • TNGHTMLHeaderControl
  • TNGHTMLListBox
  • TNGHTMLPanel
  • TNGHTMLView
  • TNGHTMLStringStorage
• DB Controls
  • TNGHTMLDBLabel
  • TNGHTMLDBView

Demos

Demo folder: html\delphi
features
Demonstrates features of the NG HTML engine.
controls\core
Demonstrates non-DB aware controls of NG HTMLPack.
controls\dbaware
[Top]

NG DialogPack (Delphi 2010 or higher only)

NG-DialogPack is based on the features provided by Microsoft Windows Vista Task Dialog API, which allows to create and show Windows Vista (Windows 7) like dialogs. The package extends platform API with emulation mode, which allows to use NG-DialogPack components in previous OS versions, such as Windows XP. Also, emulation mode provides additional features, such as Input Dialog, which has no analog in platform API.


See also: NG DialogPack documentation
[Top]

Features

NG-DialogPack package contains tree major components:

• TNGTaskDialog component allows to configure and show Windows Vista (Windows 7) like task dialogs. Task dialog can contain:
  • Caption, Title and Content texts.
  • MainIcon, which can be one of the standard icons, like Information, Warning, Error, ect.; or a custom icon.
  • Standard buttons, such as Ok, Cancel, Yes, No, Retry, ect; or a custom buttons, with custom Caption, ModalResult and Enabled state, configurable by the user. There is the ability to show custom buttons as command links, supporting CommandLinkHint feature.
  • Radio buttons with Caption and Enabled state configurable by the user.
  • Progress bar with various configurable properties, such as Min, Max and Position.
  • Expandable additional information text with expand/collapse button.
  • Verification check-box with configurable initial check-box state and check-box caption.
  • Footer area with FooterIcon, analogous to MainIcon, and FooterText.
• TNGInputDialog component allows to configure and show input dialog, which is a dialog that contains some input control, such as edit or memo, and provides a way for the user to input a value. Input dialog can contain:
  • Caption, Title and Content texts, MainIcon, standard and custom buttons, expandable additional information, verification check-box and footer area - all these features are analogous to TNGTaskDialog.
  • Input control, which can be configured by the user by assigning a value to InputType property. Input control can be one of the following: edit, memo, password edit, editable combo-ox, non-editable combo-box, date-time picker or a custom input control (or several controls) configured as a mini-HTML template, using TemplateHtml property.
  • InputValue property can be used to specify initial input value, which is shown when the dialog executed. As well, InputItems property can be used to configure combo-box items.
• TNGMessageDialog component allows to configure and show simple message dialogs with a look, compatible with TNGTaskDialog. The main purpose of the component is to be used internally inside TNGDialogs.Message overloaded methods, so, it, probably, need not be used explicitly. The component provides a set of properties, which are analogous to Delphi standard MessageDlg function parameters.

First two dialog components support advanced set of features, such as callback timer, OnButtonClick event with the ability of dialog content modification from the event handler, and navigation. [Top]

Fluent Interface

We are proud to introduce a simple, very convenient API for executing dialogs. The API is organized as static methods of TNGDialogs structure, most of which are overloaded. In most cases this API allows to show required dialog writing one or just several lines of code without placing dialog components on the form. The API provides replacement for standard Delphi dialog functions, such as ShowMessage, MessageDlg, InputBox and InputQuert to allow to show dialogs, compatible with task dialog look and feel. It also contains some additional simple dialog functions, such as Error, Warning or Information. All these function are overloaded, which allows to specify only required parameters.

Another part of Fluent Interface API is our unique dialog builders, available for task and input dialogs. Following are some usage examples:

The code:

TNGDialogs.Task('My caption', 'My title', 'My description text')
            .Icon(tdiInformation)
            .Buttons([tcbOk, tcbCancel], tcbOk)
            .Execute;

will show the following simple dialog:


More complex example:

  case TNGDialogs.Task('My caption', 'My title', 'My description text')
                 .Icon(Application.Icon)
                 .Button('My button', 100, True)
                 .Buttons([tcbOk, tcbCancel])
                 .ExpandableInfo('My long long expandable information text')
                 .Footer('My footer text', tdiWarning)
                 .Execute of
    100:      ; // My button clicked.
    mrOk:     ;
    mrCancel: ;
  end;

will show the following:

[Top]

Designtime Editor

The package provides design-time editor for TNGTaskDialog and TNGInputDialog components. Double click on the dialog component. placed on a form, to execute design-time editor. The editor provides a simple way to configure dialog, and provides the ability to look at the resulting dialog by clicking "Show Dialog" button:

[Top]

NG ValidatorPack

LMD Validators Pack provides a set of components and classes to implement client-side validation of data input in an elegant and clear way without writing much code (often without any code at all). The two main tasks of client-side validation are:

• to check for validity a value entered by a user into some input control;
• to provide feedback about validation results (e.g. to indicate an error) in some way.

NG ValidatorPack represents the standalone version of LMD Validator Controls without any references to LMD VCL - usable with many available VCL and 4rd Party input controls. For first info check LMD Validator Tutorial (LMD VCL related, but concept is same.
[Top]