Dimensional Data

Account Ability is a network ready software application developed in Delphi that fulfills the needs of small to midsize businesses with a simple, yet powerful, solution to the complicated job of annual 1095, 1098, 1099, 3921, 3922, 5498, W2G, W2 and W2c compliance. Payee/Payer copies can be printed on ordinary copy paper, preprinted forms, or written to PDF. Includes electronic filing with IRS and SSA. According to the developer, “The entire database, which can reside on your Local Area Network (LAN), Wide Area Network (WAN), Cloud Server or Desktop Computer, can be shared among select groups or users at your discretion. Account Ability’s Integrated Browser eliminates the need to remember your TCC, EIN, User ID, Password and PIN required by IRS FIRE and SSA Business Services Online (SSA BSO).” The amount of supported forms and features in this tax software for dealing with the United States tax code is staggering.

The BlobStreams sample shows you how to use the BLOB streaming techniques of FireDAC. To this end, this sample implements both the external streaming and the internal streaming. Location You can find the BlobStreams sample project at: Start | Programs | Embarcadero RAD Studio Sydney | Samples and then navigate to: Object PascalDatabaseFireDACSamplesComp LayerTFDQueryBlobStreams Subversion Repository: You can find Delphi code samples in GitHub Repositories. Search by name into the samples repositories according to your RAD Studio version. How to Use the Sample Navigate to the location given above and open BlobStreams.dproj. Press F9 or choose Run > Run. Files File in Delphi Contains BlobStreams.dprojBlobStreams.dpr The project itself. fBlobStr.pasfBlobStr.fmx The main form. Implementation Before running the sample, the main components are configured at design time using the Object Inspector as follows: Two TFDQuery objects named qSelect and qInsert. These components are used to implement the datasets capable of executing SQL queries. The following setup is needed: Configure the Connection property of both objects to specify the FireDAC connection object that is used to connect to a DBMS. In both cases it is set to FDConnection1. Set the SQL property for both objects. It specifies the SQL statement to execute for the query. The SQL property of qSelect is set to select * from {id FDQA_Blob}. The SQL property of qSelect is set to insert into {id FDQA_Blob} (blobdata) values (:blobdata). Configure the qInsert.Param[0]: The Name property is se to BLOBDATA The DataType property is set to one of the BLOB data types. In this sample ftBlob. The ParamType property is set to ptInput. It means that the stream will be read and written to a database BLOB value. The StreamMode property is set to smOpenRead. This is the default value. It means that the stream is used to read the database BLOB value. A TDataSource object named DataSource1. This component provides an interface between a dataset component and data-aware controls on a form. In this sample, it is used to provide communication between the dataset and a TDBMemo object named DBMemo1. DBMemo1 is used to display the blobdata field of the dataset. To this end, the following setup is needed: The DataSet property of DataSource is set to qSelect. The DataSource property of DBMemo1 to DataSource1. The DataField property of DBMemo1 to blobdata. Once the main components are configured at design time you can run the application and interact with the sample in run time. To this end, the sample offers three buttons: Prepare data. This button creates an OnClick event that uses the TFileStream.Create method to instantiate the file stream in order to write a string into the file. Insert (external stream). This button creates an OnClick event that implements an external streaming. An external stream is provided by the application to FireDAC (external to FireDAC). Then, FireDAC reads this stream. See the code below: Insert (internal stream). This button creates an OnClick event that implements an internal streaming. An internal stream is provided by FireDAC to the application (internal to FireDAC). Then, the application reads this stream. To this end, the sample does the following: Use the StarTransaction method to start a mandatory transaction. Set the parameter DataType to ftStream. Set the parameter StreamMode to smOpenWrite in order to write the database BLOB value. Use the ExecSQL method to execute the SQL command. This will return the internal stream reference. Write the internal stream reference. Call the CloseStreams method to flush database API buffers and close internal streams. Use the Commint method to finish the transaction. For more information about this sample, please refer to the link below:http://docwiki.embarcadero.com/CodeExamples/Sydney/en/FireDAC.TFDQuery.BlobStreams_Sample Check out the full source code for the BLOB streams sample app in Windows for Delphi on GitHub.

Introduction Delphi Builder components for preparing and burning images to CD, DVD, and Blu-ray optical storage media. Uses standard Windows Image Mastering API 2. 2. Components in the Demo and what they do The Demo contains some labels with text, as well as TEdits for the directory paths and file names. The ‘Create Image’ button calls the button onClick event, which executes the Write process. In the next code you can see the execution in details. procedure TFormMain.ButtonCreateImageClick(Sender: TObject); begin Cancel := False; ProgressBar.Value := 0; UpdateControls(True); try FDiscImage.VolumeName := EditVolumeName.Text; FDiscImage.SourceTree := EditSourceTree.Text; FDiscImage.Write(EditImageName.Text); finally LabelStatus.Text := ”; UpdateControls(False); end; end; procedure TFormMain.ButtonCreateImageClick(Sender: TObject); begin   Cancel := False;   ProgressBar.Value := 0;   UpdateControls(True);   try     FDiscImage.VolumeName := EditVolumeName.Text;     FDiscImage.SourceTree := EditSourceTree.Text;     FDiscImage.Write(EditImageName.Text);   finally     LabelStatus.Text := ”;     UpdateControls(False);   end; end; The Main component that does the Image Writing is the TFDiscImage component by Winsoft. Depending on the TRadioGroup choice, the user chooses between two file systems – ISO 9660 and UDF. When one of the files systems is marked, an onChange event is fired with code: procedure TFormMain.RadioButtonChange(Sender: TObject); begin if RadioButtonIso9660.IsChecked then FDiscImage.FileSystems := [fsISO9660] else FDiscImage.FileSystems := [fsUDF]; end; procedure TFormMain.RadioButtonChange(Sender: TObject); begin   if RadioButtonIso9660.IsChecked then     FDiscImage.FileSystems := [fsISO9660]   else     FDiscImage.FileSystems := [fsUDF]; end; To get better vision on what these components do, check the video below: If you want to download this Component suite, click on the next link: https://winsoft.sk/fburncs.htm

procedure TFirebaseDatabase.SetBaseURI(const ABaseURI: string); begin   FBaseURI := ABaseURI; end; procedure TFirebaseDatabase.SetToken(const AToken: string); begin   FToken := AToken; end;   function TFirebaseDatabase.Get(const AParams: array of string;   AQueryParams: TDictionary<string, string> = nil): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcGet, nil,     AQueryParams); end;   function TFirebaseDatabase.Post(const AParams: array of string;   AData: TJSONValue = nil; AQueryParams: TDictionary<string, string> = nil;   ADataOwner: boolean = true): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcPost, AData,     AQueryParams, ADataOwner); end; function TFirebaseDatabase.Put(const AParams: array of string;   AData: TJSONValue = nil; AQueryParams: TDictionary<string, string> = nil;   ADataOwner: boolean = true): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcPut, AData,     AQueryParams, ADataOwner); end; function TFirebaseDatabase.Patch(const AParams: array of string;   AData: TJSONValue = nil; AQueryParams: TDictionary<string, string> = nil;   ADataOwner: boolean = true): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcPatch, AData,     AQueryParams, ADataOwner); end; function TFirebaseDatabase.Delete(const AParams: array of string;   AQueryParams: TDictionary<string, string> = nil): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcRemove, nil,     AQueryParams); end;

This industry-ready Order Entry Application template for busy small business owners. This project is to build a general template for the regular structure of the order entry application.       Specifics • Specifically we are working on something similar to general existing order entry applications. • The goal is to have a reusable template that a user can download and add their content to and create a professional-looking application. • The template will be delivered in a sample application that shows the power and flexibility of the template. And that is documented enough so that a user will understand how to customize it for their use. On the following slides, you will find screenshots and annotations Order Entry – tabs, rooms, and menu management Time Clock – employee clock in/out Manager – main manager settings Exit – exit from the application In a room view, it is possible to assign a table to a user and to start a new tab It is possible to move tables on the screen according to their real location It is possible to see the number of seats for each table On this screen, the user can pay for the order in different ways and leave tips You can download the Order Entry App from GetIt Package Manager Also, be sure to check out other amazing sample application here!

The sample demonstrates how to use the TFDQuery component in order to set up master-detail relationships between datasets. It uses the master-detail relationship to automatically filter a detail dataset based on a current master dataset record. In this sample, the master dataset has “Order” records, and the detail dataset shows only lines for the current order. Moreover, you can modify in run time the Cache property of TFDFetchOptions to control the data allocation in cache memory. Location You can find the MasterDetail sample project at: Start | Programs | Embarcadero RAD Studio Sydney | Samples and then navigate to: Object PascalDatabaseFireDACSamplesComp LayerTFDQueryMasterDetail Subversion Repository: You can find Delphi code samples in GitHub Repositories. Search by name into the samples repositories according to your RAD Studio version. How to Use the Sample Navigate to the location given above and open Qry_MasterDetail.dproj. Press F9 or choose Run > Run. Files File in Delphi Contains Qry_MasterDetail.dprojQry_MasterDetail.dpr The project itself. fQueryMasterDetail.pasfQueryMasterDetail.fmx The main form. Implementation To set up a master-detail relationship, this sample uses the Object Inspector to configure the following components at design time as follows: Two TFDQuery objects named qryOrders and qryOrderDetails. These components are used to implement a dataset capable of executing SQL queries. The following setup is needed: Configure the Connection property of both components to specify the FireDAC connection object that is used to connect to a DBMS. In order to set up a master-detail relationship, the SQL properties of both components have to be set up using the Object Inspector at design time as follows: The SQL property of qryOrders is set to select * from {id Orders} in order to select “Order” records. The SQL property of qryOrderDetails is set to select * from {id Order Details} where OrderID = :OrderID in order to select “Order Details” records. Finally, both objects are linked in a master-detail relationship, where qryOrders is the master dataset and qryOrderDetails is the detail dataset. To this end, you have to set up the following properties of qryOrderDetails: MasterFields is set to ORDERID. IndexFieldNames is set to ORDERID. MasterSource is set to dsOrders. Two TDataSource objects named dsOrders and dsOrdDetails. These components provide an interface between a dataset component and data-aware controls on a form. In this sample, it is used to provide communication between the datasets and the grids where the datasets are displayed. To this end, the following properties are set up at design time using the Object Inspector: The DataSet property of dsOrders is set to qryOrders and the DataSource property of DBGrid2 is set to dsOrder. The DataSet property of dsOrderDetails is set to qryOrderDetails and the DataSource property of DBGrid1 is set to dsOrderDetails. The Cache details check box includes fiDetails into the FetchOptions.Cache property of qryOrderDetails if the check box is checked. It means that if it is checked, the associated detail record will not be discarded from the memory after changing a master dataset record. The Refresh master button uses the Refresh method to re-fetch the master data from the database. The Refresh details button uses the Refresh method to re-fetch the detail data from the database. Please refer to the link below for more information about the sample: http://docwiki.embarcadero.com/CodeExamples/Sydney/en/FireDAC.TFDQuery.MasterDetail_Sample Head over and check out the full source code for the master detail Windows sample app on GitHub.

Rapid PHP is a lightweight native code editor and IDE for PHP on Windows and it is built in Delphi. According to their site, “Rapid PHP editor is a faster and more powerful PHP code editor for Windows combining features of a fully-packed PHP IDE with the speed of the Notepad. Rapid PHP is the most complete all-in-one software for coding PHP, HTML, CSS, JavaScript and other web development languages with tools for debugging, validating, reusing, navigating and formatting your code.” It offers 6 different localization languages for the interface and a truly massive amount of features. In addition to PHP it has extensive Javascript and CSS capabilities to create a rounded development platform for building web apps in PHP. Notable productivity features include things like “Edit/save directly on FTP/SFTP/FTPS server or quickly publish all changed files”, “SVN and Git integration”, and “PHP debugger (xDebug)”. Website https://www.rapidphpeditor.com/ Screenshot Gallery Reduce development time and get to market faster with RAD Studio, Delphi, or C++Builder. Design. Code. Compile. Deploy.Start Free Trial   Upgrade Today    Free Delphi Community Edition   Free C++Builder Community Edition Webinar: Massively Boost C++Builder Compile Speed Up To 50x with TwineCompile

Since Chet uses an actual compiler, you will need to have a (minimal) C develop environment installed, as well as LLVM with Clang. Clang needs to be able to find the system headers for the development environment. These will usually be available if you have some version of Visual Studio with Visual C++ installed. The free (community) edition of Visual Studio suffices. As said in the readme on Github, unlike some other header translators, Chet uses the Clang compiler to parse header files, resulting in more accurate translations that require fewer manual adjustments. Please check out the awesome features Chet lists: Translates C data types such as structs, union, enums, typedefs, procedural types and opaque types. Translates C functions to Delphi procedures or functions. Tries to translate #define declarations to constants where possible. Generates a single .pas file for an entire directory of .h files. This reduces issues due to dependencies between header files. Generates output for multiple platforms (Windows, macOS, Linux, iOS and Android) if desired. You can customize the Clang parsing process by supplying command line arguments to the compiler. You can customize the output of some conversion operations. Retains any Doxygen style documentation comments if desired, or converts them to XmlDoc comments or PasDoc comments. Provides a GUI for configuring the conversion process, and allows you to save the conversion settings to a .chet project file for reuse. Although Chet has amazing features, there are some limitations that the user has to pay attention on: Chet only works with C header files, not with C++ header files. All non-inlined functions in the header files are translated and assumed to be available in the static or dynamic library for the project. This does not have to be the case. (Inlined functions are never translated since they are never available in the library.) Since Clang is used to parse the header files, this means that Clangs preprocessor is run as well to perform conditional parsing (guided by #ifdef directives). This is both good and bad. It is good because it improves conversion accuracy. But it can be bad because it uses the system that Chet runs on to determine some conditional paths. For example, because Chet runs on Windows, it will parse code in #ifdef _WIN32 sections but skip any code in sections for other platforms. You can run Chet first to check for any errors related to missing dependencies. If you get any dependency errors when running the translator, then you can download the dependencies here: LLVM with Clang (Clang for Windows (64-bit) is recommended); Visual Studio IDE (the free Community edition suffices; be sure to install C++ support). You can use the pre-compiled 64-bit Windows Chet application in the Bin directory. If you want to compile Chet yourself, then you also need libclang for Delphi and make sure the Delphi IDE can find it (the Chet project will find it automatically if the Neslib.Clang directory is at the same level as the Chet directory). Chet is licensed under the Simplified BSD License. From the Github article we understand that Chet is pretty straightforward. In many cases, you only need to provide a directory with header files, the name of the output .pas file and select “Run Header Translator (F9)”. For more control over the conversion process, you can specify various options, described below. The screenshot from GitHub for the project is below: This […]

procedure TForm1.CreatePythonComponents; begin   if cbPyVersions.ItemIndex

LockBox3 is a Delphi library for cryptography. It provides support for AES, DES, 3DES, Blowfish, Twofish, SHA, MD5, a variety of chaining modes, RSA digital signature and verification. This is a source-only release of TurboPack LockBox3. It includes designtime and runtime packages for Delphi and C++Builder and supports VCL, FMX, Win32, Win64, macOS, iOS, and Android. Reading the information from http://lockbox.seanbdurkin.id.au/HomePage, “the user interface shall be clean and simple. For Ciphers and Hashes, two styles shall be provided: A component and an interface pointer. IV, salting of ciphers and signaling of IV’s shall be managed and hidden from the developer-client. The main encryption functions shall be implemented in 100% native Delphi code. (TOpenSSL_Signatory component is the exception to the rule).“ That is to say it shall not rely on links to third party libraries (at least as far as the core functionality is concerned). LockBox 3 is has easy traceability to standards. Developers should be able to open cipher standards and open the respective implementing source code; put them side-by-side, and very quickly observer that one implements the other. implementing source should borrow the style and symbols and the specifiying cipher standard.It shall be as easy as it can be to extend the library with new hashes and block ciphers. The selection, implementation and usage of ciphers shall be divorced from the chaining mode. LockBox3CR.bpl (C++Builder Runtime) and LockBox3CD.bpl (C++Builder Designtime). TurboPack LockBox3 is available via the GetIt Package Manager where you can quickly and easily install and uninstall it. To manually install TurboPack LockBox3 into your IDE, take the following steps: Unzip the release files into a directory (e.g., d:lockBox3); Start RAD Studio; Add the source directory (e.g. d:lockBox3run and all the subdirectories) to the IDE’s library path. For C++Builder, add the hpp subdirectory (e.g., d:lockBox3sourcehppWin32Release) to the IDE’s system include path; Open & install the designtime package specific to the IDE being used. The IDE should notify you the components have been installed; I can tell for sure that this is the best choice for cryptography library ! If you want to download this package via GitHub, please refer to the link below: https://github.com/TurboPack/LockBox3 Or find out more about TurboPack LockBox3 and download it via Embarcadero GetIt.