Ecere SDK

This is an interesting cross-platform sdk (http://www.ecere.com). It is c with object, like c++. But seems easier to learn and code than c++. It should build fine on Linux, on Windows with MinGW or MinGW-w64 or TDM-GCC, on Mac OS X with Xcode command line tools installed or on FreeBSD (with gmake). Executables can also be deployed to the Android platform using the Android NDK.

The SDK includes complete development environment for coding and GUI designer, supports including c and c++ code as part of the project and got cross-platform GUI toolkit with 2D and 3D graphic engines, though the GUI components are somewhat primitive.

The runtime component covers file access, multithreading, time and networking (with SSL Sockets support through OpenSSL). With the EDA (Ecere Data Access) components, you will be able to access Ecere RDBMS, SQLite (as well as an encrypted version using SQLiteCipher), and Oracle databases. It also has a simple report engine with preview support. The runtime libraries size is below 10MB.

The most impressive thing is, the Ecere SDK is Free Open Source Software licensed under a revised BSD license which allows applications built with it can be distributed both commercially and non
commercially, along with the supporting Ecere runtime library(ies).

 

Just successfully compile #QtRpt & #QtRptDesigner with #Qt5.1.1

#QtRpt is a #reportengine for #Qt application. I like its interface as it looks similar to #FastReport. However, it seems to be a startup project which lack of many features that I used with #FastReport, like nested data band, #master-child report, #barcode printing, #export to #Excel, #pdf, #crosstab report, ti name a few.

Though #QtRpt missing many features that I need, it is a good starting point for me to study.

As recently, I'm trying #Qt5.1.1 , I take it as my testing project. The report engine is written using #Qt4 initially(?), and the latest version of #QtRpt is able to be compiled with #Qt5 , it is not the case for its #QtRptDesigner.

Porting of #QtRptDesigner to #Qt5 is much easier than I think. It's just a few replacement/addition of #include clause and add the #Qt version checking in the #project file to add #Qt5 module will be done.

And now, I have a working suite of #QtRpt for testing. :)