Stephen is a Charted IT Professional and the Associate Product Manager for InterBase at Embarcadero. He is also a Product Evangelist for RAD Studio, regularly speaking across EMEA. @DelphiABall
The XML Dom defines which engine in essence is used to work with your XML documents.
Should I read on? Well if your using SOAP or XML in your projects, then this could make a difference to your speed and performance of the applications, and it takes seconds to implement.
One present I’m going to be playing with over Christmas is the Castalia IDE plug in. If you want to know why, check out the 10 minute demo here of some of the cool refactoring and IDE tools that Castalia provides.
http://embt.co/IBXE7FirstLook
I am especially proud today to blog about the launch of InterBase XE7! As the Product Manager for InterBase, I have seen the planning, development and delivery of some amazing new developments over this last year or so, and today you can get your hands on them!
InterBase XE7 – Whats new?
In short, the big headline items include
Change Views
New – 64bit Linux support
New – Ubuntu Linux support
A number of speed improvements (as you would expect)
InterBase XE7 (codenamed DeltaForce during development) introduces “Change Views“, which is a whole new way to track and manage changes (Delta’s). If you have ever wanted an easy way to identify what delta data is needed to keep your local cache up to date Change Views is for you!
Change views identifies data at the field level with exceptionally low footprint on the database, regardless of 1 or 1000’s of subscribers.
Change views introduces a subscription based model that enables you to create a subscription for Inserts, Updates, Deletes to specific tables either completely or partially. A subscription can contain links to one or more tables.
“Tracking and managing data changes to multiple destinations has never been easier; just subscribe and query with SQL!”
InterBase – the 64bit database for Ubuntu!
InterBase is also now available for Linux 64bit for the first time on RHEL 6 and 7, SUSE 11 and also for the first time official Ubuntu 14 support.
Incremental Data Dumps
A data dump is a read only copy of the database. For XE7 they are suggested as the best way to backup the database due to their speed at getting the copy updated to reflect the live version quickly, managed by delta change tracking. This can either be done via the command line using gbak, via IBConsole of via a new services API. If your using Change Views, then you should use Incremental Data Dumps to ensure subscription tracking is maintained.
64bit Transaction ID’s
One great thing about InterBase is that its an embeddable database, i.e. you can install it silently in part of your application. In the past, for exceptionally heavy users with 10’s of 10,000’s of transactions a day you used to be looking to schedule monthly backup and restore’s to ensure you didn’t run out of transaction ID’s at peak time. With XE7, transaction ID’s are now 64bit in size meaning that even if you were using 10,000 transactions a second, you can run for 150+ years (just a tad longer!)
InterBase project DeltaForce, named due to its new patent pending technology for tracking and querying of deltas, is a highly scalable, low footprint answer to a number of distributed data set questions.
I’m really excited about what we have coming up in the InterBase XE7 preview events. I will be hitting the road over the coming weeks in person to present and talk to developers, system architects etc about what InterBase DeltaForce (XE7) can help you achieve and how it can dramatically assist you throughout the product life cycle.
InterBase XE7 First Look – LIVE!
I will be in the following cities over the next few weeks for live preview workshops
The CodeRage 9 videos are now available for reply online via YouTube. To save you searching, the InterBase CodeRage 9 links I did are below; For the full list of videos from CodeRage 9 please visit the Embarcadero Community blog post for CodeRage 9
The C++ programming version demo’ed requires the data module from the Object Pascal code, so once I’ve cleaned that up I’ll post that as well.
The IBLite example code works on Windows, Mac OS X, iOS and Android. The session replays are available online via the CodeRage website. – More on the InterBase sessions in my previous post
CodeRage is a fantastic Object Pascal programming and C++ Programming event – highly recommended for any developer, and best of all – REGISTRATION IS FREE!!
Missed it or got a meeting? – Don’t worry, register and you can still get to see the replays!
My two InterBase CodeRage Sessions!
I will be presenting two InterBase CodeRage sessions on Thursday 30th November 2014
the InterBase Keynote (8am Pacific / 4pm UK / 5pm CET) where we will be revealing some of the exciting new developments we are working on with InterBase with project DeltaForce!
I will also be talking about InterBase’s free edition that can be used on Windows, Mac OS X, Android and iOS – IBLite in the session Embedding local and remote data access into your applications with IBLite (3pm – C++ & 6pm – Object Pascal)
For times and details of all sessions visit the CodeRage website – See you there!!
VCL Styles provide a great way to update the look and feel of your VCL applications. VCL Styles can be easily added into an application before you compile through project options > appearance options.
Adding VCL Styles via Project : Options : Appearance
While you can add VCL Styles into the application binary this way, they will increase the size of the application. If you want to avoid this, (or maybe run a mix of compiled in and dynamically loaded) you can distribute styles along side your application.
By default, VCL Styles are located at the following file path when installing your IDE.
Styles are managed via TStyleManager, a class located in unit VCL.Themes.
TStyleManager is a sealed class with a number of class methods that allow you to interact with the global application settings for the styles.
Some key properties on TStyleManager
TStyleManager.StyleNames – an array of the styles available in the application.
TStyleManager.SetStyle(StyleName : string) – the call to set the application style to a new style
Using these basic methods, its possible to implement code that loops the styles in the application and makes them available to a menu that can then be used at run time to choose which style is selected.
TStyleManager.IsValidStyle(FileName: string) – checks a file is a valid style
TStyleManager.LoadFromFile(FileName : string) – loads a style up from file.
With the additional file based calls its possible to check for style files and load those into your application as well. – So lets do that!
VCL Styles code example
The MastApp demo that is installed by default with RAD Studio has an example of using TStyleManager. You can find the demo at:
This demo uses 2 code parts and 1 design time selection element to provide styles in the demo.
Part 1 – Compiling VCL Styles into your application.
Open the project and then choose Project > Options and go to appearance. As above, select a couple of styles and run the application. You will then see the Styles menu is updated to show these styles.
The initial code to build the menu loops the StyleNames, creates a menu item for each style, adds then links to an OnClick event to change the style.
Part 2 – Building the style list menu
procedure TMainForm.FormCreate(Sender: TObject);
var
Style: String;
Item: TMenuItem;
begin//Add child menu items based on available styles.for Style in TStyleManager.StyleNames dobegin
Item := TMenuItem.Create(StyleMenu);
Item.Caption := Style;
Item.OnClick := StyleClick;
if TStyleManager.ActiveStyle.Name = Style then
Item.Checked := true;
StyleMenu.Add(Item);
end;
end;
Step 3 – OnClick event for the Style selected.
procedure TMainForm.StyleClick(Sender: TObject);
var
StyleName: String;
i: Integer;
begin//get style name
StyleName := StringReplace(TMenuItem(Sender).Caption, '&', '',
[rfReplaceAll, rfIgnoreCase]);
//set active style
TStyleManager.SetStyle(StyleName);
//check the currently selected menu item
(Sender as TMenuItem).Checked := true;
//uncheck all other style menu itemsfor I := 0 to StyleMenu.Count -1 do beginif not StyleMenu.Items[i].Equals(Sender) then
StyleMenu.Items[i].Checked := false;
end;
end;
So: We have styles working, but you can also load them from file with very little change to the application.
Loading Styles from file and displaying them in the list of styles
VCL Styles can be loaded at run time easily using TStyleManager.LoadFromFile
Using the existing demo, its possible to have it check for a styles sub folder and read any file in there to see if its a valid style. To do this, we just need to use FindFirst, iterate the returned files and then if they are valid (something we can use TStyleManager.IsValidStyle to determine) load the files.
So the updated code looks something like this block below where we first build the path to check for VCL Style files; then check the folder exists, and if it does check each file to see if its a valid VCL Style (before loading it). Secondly, using a TStringList the styles loaded are sorted and then the sorted list is used now to build a menu for selecting the styles.
procedure TMainForm.FormCreate(Sender: TObject);
var
Style: String;
Item: TMenuItem;
i: integer;
searchResults : TSearchRec;
SearchDir: string;
SLStyles: TStringList;
begin
SearchDir := ExtractFilePath(ParamStr(0))
+'styles'+ PathDelim;
if DirectoryExists(SearchDir) thenbeginif FindFirst(SearchDir+'*.*',
faAnyFile - faDirectory,
searchResults) = 0 thenrepeattryif TStyleManager.IsValidStyle(
SearchDir+searchResults.Name) then
TStyleManager.LoadFromFile(
SearchDir+searchResults.Name);
except// Who cares.. try the next one.end;
until FindNext(searchResults) <> 0;
end;
// Sort the styles using a StringList
SLStyles := TStringList.Create;
try
SLStyles.Duplicates := TDuplicates.dupIgnore;
for Style in TStyleManager.StyleNames do
SLStyles.Add(Style);
SLStyles.Sort;
PMStyles.Items.Clear;
// build menu from sorted list of stylesfor Style in SLStyles do begin
Item := TMenuItem.Create(StyleMenu);
Item.Caption := Style;
Item.OnClick := StyleClick;
if TStyleManager.ActiveStyle.Name=Style then
Item.Checked := true;
StyleMenu.Add(Item);
end;
finally
SLStyles.Free;
end;
end;
Thats it! You can now create a sub folder for VCL styles that you ship along side your application or deploy at a later point.
For C++ use the same classes and units, just with the C++ Loops and constructs. more on VCL Styles with C++ can be found on docwiki
Programming with Delphi & InterBase
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptRead More
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.