Mittwoch, 6. Dezember 2017

Delphi Entwickler (m/w) gesucht!

Programmierer (m/w) für Delphi 2007 und XE 10.x.x!

Für die Weiterentwicklung einer Software für Gerichtsvollzieher in Deutschland suchen wir Programmierer mit hervorragenden Delphi Kenntnissen.

Unser Unternehmen ist der Marktführer im Bereich Gerichtsvollziehersoftware und seit über 30 Jahren auf dem Markt. Mehr als 2.200 Gerichtsvollzieher im Bundesgebiet zählen zu den Kunden. Die Software hat einen enormen Funktionsumfang und der Aufgabenbereich der Gerichtsvollzieher ist ausgesprochen groß.

Ihre Aufgaben:

  • Weiterentwicklung einer umfangreichen Software für Gerichtsvollzieher sowie einiger Nebenprodukte
  • Fehleranalyse und Optimierung
  • Unsere Anforderungen:
  • Hervorragende Kenntnisse in Delphi
  • Fähigkeit, sich in mehrere Millionen Zeilen Sourcecode einzuarbeiten
  • Optional: Erfahrung mit FireMonkey zur Entwicklung von Apple sowie Android Apps
  • Hohe Lernbereitschaft, da Sie viele Arbeitsabläufe eines Gerichtsvollziehers und der Justiz nebst zahlreicher Fachbegriffe erlernen müssen
  • Geduld, Freundlichkeit und eigenständiges Arbeiten
  • Gute Ausdrucksweise, einwandfreies Deutsch in Wort und Schrift

Wir bieten:

  • Sehr sicherer Arbeitsplatz und unbefristete Einstellung beim Marktführer
  • Langfristiges Beschäftigungsverhältnis
  • gute Aufstiegsmöglichkeiten.
  • Nur Festanstellung, kein Heimarbeitsplatz, kein Außendienst, gutes Arbeitsgerät – z.B. nutzen die Programmierer bis zu sechs 40“ UHD Bildschirme gleichzeitig.
  • Stetig neue Herausforderungen und Veränderungen
  • 3 im Thema eingearbeitete Programmierer sowie einige Gerichtsvollzieher zur Unterstützung
  • Ggf. Ausweitung Ihrer Tätigkeit (mehr Verantwortung, eigenständige Entwicklung, Schulungen, Präsentationen)
  • Kleines Unternehmen mit momentan 9 Angestellten
  • Ggf. Unterstützung bei einem notwendigen Umzug
  • Über Ihre aussagekräftigen Bewerbungsunterlagen, mit Beschreibung Ihrer Programmiererfahrung/–kenntnisse, Angabe Ihrer Gehaltsvorstellung und Nennung des frühestmöglichen Arbeitsbeginns freuen wir uns.

Für Rückfragen stehen wir gerne zur Verfügung.

Einen kleinen Einblick über unsere Produkte erhalten Sie auf unserer Webseite

Baqué & Lauter GmbH
Flamersheimer Weg 3
53881 Euskirchen Palmersheim

Montag, 27. November 2017

Back in my office.


After 19 days of workshops with nearly 1600 customer and more than 7000km on the road, I'm back in the office. So I need some time to look through the stacks of Paper on my desk, but after that I will do the FDK update before the end of the year.

Montag, 2. Oktober 2017


Using Facebook or this blog?

OK - Perhaps technical Infos in this blog and Funstuff on Facebook...

I have to look for a cat using my FDK for the best Facebook user experience...


Sonntag, 24. September 2017

Forentage 2017 - Sonderaktion

Hallo Zusammen!

Leider hatte ich die Bestellformulare mit einem Sonderpreis für mein FDK - im Auto - im Kofferraum -  im Saturnparkhaus vergessen.

Natürlich hätte es eine Sonderpreis für Bestellung auf den ForenTagen gegeben!

Also: Befristet bis zum 15.10.2017 gibt es mein FDK für 349,- € (statt 399,- €)

Einfach das Setup downloaden und registrieren!!

Infos unter :

Die nächste Version ist in Vorbereitung.

INFO: Die MVVM-Teile sind zur Zeit noch nicht enthalten!

Dienstag, 5. September 2017

Scanning barcodes the FDK-way

You like to scan barcodes in your app?

Ok, you probably googled this topic! But you will find solutions only for iOS or solutions only for Android. Perhaps a preinstalled thrid-party app must be installed.

Of course there are solutions for both platforms, but for free?

And how long does it take to integrate this in your app?

Perhaps you consider the FDK approach:



  FScanbarcodes : ICanScanBarcodes;

procedure TFormMain.ScanClick(Sender: TObject);
  FScanbarcodes := TAnyFactory.Factory.CreateObj<ICanScanBarcodes>;
  FScanBarcodes.ScanResult(Procedure (AResult : String)
      LBLScanResult.Text := AResult;
      FScanbarcodes := NIL;

Internal I'm using the ZXING Source for Android. For iOS you can choose between the ZBar or the ZXING version. ZBar ist based on the TMSWrapper for ZBar!

The ZXING Version is inspired by MVP Andrea Magni, but without the FrameStand and other overhead.

Threading is done with my TAnyCommandProcessor, that can queue the workflow for the Bitmaps, that are captured with the TCameraComponent!

Dienstag, 15. August 2017


Why I Choose Delphi?

Starting with UCSD-Pascal in school on Apple II. I used my Sharp MZ-800 (Z80 CPU) with CP/M and Turbo Pascal 1.0. I had a special utility to write IBM-Disks on MZ-800. So I was able to transfer my “homework” to the IBM XT, to show my work in school, with Turbo Pascal 1.0, too.

At this point, I got an offer to do program a business application. This application was my first real Pascal application, too.
Before that, all my programs were programmed in Z80 assembler, like my own 1000 byte Disk-Operating-System - FL-DOS from 1986.

To keep necessary procedures together, I collected procedures in “one” Pas File called Runtime.pas.

“Yes”, this unit is still alive today, but called Basis.pas and wBasis.pas for Windows-Stuff. I collected million lines of source-code and unites over the years. Some have changed but many are still in use.

Starting with e.g. C# would take me month or years to reproduce my “runtime” core procedures.

That is the practical side. Beside this, for me, a compiler has to produce an exe…
No P-Code, no script no runtime interpretation. “My” compiler has to produce a standalone application that brings everything with it. No runtime stuff that had to be prior installed.

Ok, .NET was a “not so bad idea”. To have code that could be optimized for the given CPU at first run. Do we have this kind of “run on RISC-CPU” environment?

So let’s compare:

#C could be a choice, because the code is like Pascal or not so far away!
C / C++, source code looks like someone had rolled an Armadillo over the keyboard.

End of List…

Yes, you can do everything in Delphi! However, If you are looking for some special things, you always find source in C* but not in Delphi. For this small parts. Compile with C* link an object or use a DLL, done.

Have I tried to switch to C#? Yes but, I’m so much faster in writing Delphi… It was a waste of time and btw. I hate the MS-IDE. (I still use the original WordStar key mapping from my early days on CP/M).
Remember the famous words: “The clueless people shall spend their time reinventing the wheel, while the elite merely use the WordStar key mappings”.

Let us not talk about Pascal / Delphi as source-code. One of the big thing is productivity. The IDE and the compilation speed. Turn cycles are a major point in development.

Set Breakpoint, F9 to compile and start, debug, STRG-F2 to stop, change something and hit F9 again…. If you like, you can do this thousand times in an hour.

For many years I took the RAD approach – button on the Form -> double-Click -> and go with the code… Why not!
This was the time where nobody talked about design pattern, separation of form and code or other things. Why? No Internet…
Yes, I know the Internet starts at 1989/1991 and my Application was for Win95. However, when did you start your first AOL Internet over Hayes-Modem “You have new Mail” – Client?

We don’t talk about Borland-Pascal for Windows – But I had a small working Demo of my Software, simulating the DOS-Screen in a Windows-Frame… (If you ask me, I’ve never done this).

My Company depends on Delphi and I have no problem with this…

Because Delphi is the best development tool, I’ve ever seen.

Sonntag, 30. Juli 2017

SQL, how do you write your queries?

OK - I know there are many ways to do a simple SQL Query... Like:

Query.SQL.Text := 'SELECT * FROM PersonDB where LastName LIKE "'+ALastName+'%" order by LastName,FirstName ASC LIMIT 50';

of course using Parameter is a better way, like:

Query.SQL.Text := 'SELECT * FROM PersonDB where LastName LIKE :0 order by LastName,FirstName ASC LIMIT 50';
Query.SQL.Params[0].AsString := ALastName+'%';

Perhaps you set you statements in the ObjectInspector or you copy the statement from an other tool.

But what if you are new to SQL?

What kind of errors happens in your SQLQuery?
Misspelled fieldname? Missing brackets, missing space or ",".

The problem is,- normally -  you can only find  this errors by executing the statement...

In my FDK I have all database definition in my sourcecode. All fields can easily checked against this definition.

If I do a search for a Person in my PersonDB, I like to shorten the search result by typing not only the Lastname... I like a search of both Firstname and Lastname.

If I search for my name in this database I can put "Lau,Fr" into the Searchedit and I get the result of all Person starting with the Lastname LIKE "Lau%" and FirstName LIKE "Fr%".

Perhaps you do other combinations.
In this case you always have an If or Case statement to select the right SQL, - or - to Ignore NULL DB Fields.

In my latest development of my ORM/CRUD DB Interface, I tried to include this expectations in my FDK.

For the given search problem I have this solution in every application:
procedure TPersonViewModel.Search(Const ASearchFor : String);
  LastName  : String;
  P         : Integer;
  LastName  :=  ASearchFor.Trim+'%';  
  P := Pos(',',ASearchFor);
  if P > 0
    then begin
FirstName := Copy(LastName,succ(P),
    else FirstName   := '';

  // Normally
  if FirstName.Trim = ''
Query.SQL.Text := 'SELECT ...'// Without FirstName
    else Query.SQL.Text := 'SELECT ...';// With FirstName

But I don't like this untestable SQL in this procedure. So I came up with this:

procedure TPersonViewModel.Search(Const ASearchFor : String);
SearchResult : ICanCRUDSearch; // from my CRUD-Framework
// .. Same as above
  // .. Same as above and then

   {} Where('LASTNAME').LIKE(LastName.Trim).
   {}   begin_Optional(FirstName.Trim <> '').
   {}     _AND.Where('FIRSTNAME').LIKE(FirstName.Trim).
   {}   end_Optional.
   {} OrderBy('LASTNAME').OrderBy('FIRSTNAME ASC').
   {} Limit(100).
   {} Start(SearchResult);

   if SearchResult.SyntaxOnly then
   // Perform UserIO on SearchResult

And for Unit-Testing you can just call this same procedure and "Start" performs a systaxcheck only.

Perhaps you call it "Over Engineering" - I call it helpful. And more:

I love this kind of fluid-source-code. It's so easy to read and understandable.

The {} in front of each line are only to prevent the sourcecode formatter to kill my structure.

The Fluid-Interface helps you to build your statement - of course you should know a little bit of SQL, but...e.g.

After "Where" you can only use a comparer "LIKE, EQUAL, GREATER...". That's why "Where" is defined as

     ICanCRUDWhere = Interface
    Function  Where(Const AName : String) : ICanCRUDCompare;

  ICanCRUDCompare = Interface
    Function  LIKE(Const AValue : String) : ICanCRUDSearch;
    Function  EQUALS(Const AValue : String) : ICanCRUDSearch;
    // more...

The SearchResult stores the Data and you can iterate through it.

My FDK.FMXGridHelper can take this SearchResult and could direct perform the UserIO.

The CleanUp is done by RefCounting automatically.

Stay tuned for the next FDK update... More is coming...