Another milestone was reached. The new application can load and parse historical data.

As expected, the data sources are the same as in EA Studio. However, some changes are made:
Premium Data is shown as DukasCopy.
MetaTrader Demo is shown as MetaQuotes.

I finished a lot of work on the other project, so I am continuing to work on this new application.

I already have an idea of the general design of the user interface and have prototyped the main panels and navigation bars.

Now, I'm starting the work on the functionality.

I'll post regular updates on the progress.

Trade Safe!

I refactored and improved the server code a lot. Now, I consider it ready.

I also cleaned up the client-side code for account management:
- Signup
- Log-in
- Password reset
- Password change

My next task is to start building the main layout of the application - navigation bars and content panels.

This is a helper library which sends email through Postmark
I'm using this third-party service to send emails from applications when a user registers or changes a password.

Link: https://github.com/PopovMP/postmark-email

I also worked on the server code today, fixing bugs and improving code quality.

I started working on the new application's user interface and ported some of my previous code.
The new server is online in its domain name. We can sign up, log in, change, or reset passwords.
It is an empty frame so far, but I'm satisfied with the progress.
I need several days more to clean up the backend and the client-side framework and improve some messages.

I wish you a prosperous new year full of excitement!

Many Thanks to all of you!

I wish you a pleasant New Year's celebration filled with health, happiness, and love for you and your families!
May the new year bring you lots of joy and success!

I usually write a program once. Then, I rewrite it again for optimization, validation, or code cleanup purposes ten times.
This is not how professional software companies work. However, I consider myself an Independent developer and see programming more as an art than a job.

As for now, FSB Pro, EA Studio, and Express Generator are mature products.
Top 10 Robots App and Prop Firms Robot App are also more or less ready (though there are some issues, and I'm still working on improving the validation workflow).

I started working on a new product, which I'll introduce later.

I'm currently working on the server part of the new application. I'm trying to build a frame around which I'll later add the program's actual functionality.

Programming languages, software tools, technology and knowledge change with time. Therefore, I'm rewriting the components I used in the previous products.

(More particularly, I'm converting the code from CommonJS to ES Modules and applying the strictest possible validation with TypeScript, ESLint, and Unit Testing.)

> Is the specific purpose safety or performance?

I achieve better safety and performance, but this is a side effect of my work.
It happens because my programs use only the necessary code for the purpose.

> Or literally new software for another exporter
When the backend is ready, I'll start the work on the actual exporter

I think I get it, are you writing all the software from scratch? Is the specific purpose safety or performance? Or literally new software for another exporter

I can now control the databases with remote requests.

Today, I've been doing a lot of code cleaning and refactoring. I have a good feeling that I'll have the user management working until the evening.

It needs at least these essential components:
- configuration—it contains and provides the application's generic settings. It also reads private local settings.
- server - this is the main part of the backend. It will construct the request and the response objects
- server-request - it will parse the incoming request and will hold the properties in a handy way.
- server-response - it will compose and send the request's response.
- router - it will map the incoming requests by URL and will redirect them to the corresponding controller actions.
- public-server - it will deal with all public resources like: javascript files, images, styles, fonts, data files...

I have these components working in my previous apps, but I'll "modernize" them and make them suitable for future products without third-party dependencies.

My next steps are:

1) Make a stand-alone backend app using the previously listed components. It must be able to show a static webpage with the corresponding pages, scripts and stiles.

2) Add DataBase and API. Introduce a "User" model. Implement CRUD: Create, Read, Update, and Remove users remotely.

3) Make the basic frame of the application's client-side user interface. Make a Light and Dark theme

4) Make user forms for sign-up, login, change password, and reset password.

I hope all of these will be read to some extent next week. Then, I'll have the foundation of the new application and can start the work on the main functionality.

Happy Holidays!

It sends GET, POST, or PUT requests and parses the response body depending on the Content-Type response header.

Link: https://github.com/PopovMP/client-request

It helps to parse the token information from an Authorization header.

This module comprises several helper functions for parsing incoming requests:

- Parse URL path parameters
- Parse request body
- Parse Form Data
- Parse Query String
- Parse JSON values
- Split Authorization Header

Link: https://github.com/PopovMP/request-parser

I just uploaded the next component, Json-DB. This is a "modernized" version of the DataBase engine I developed for EA Studio.

This database is straightforward for me because I understand it completely. This is not the case when I'm using third-party software components. No matter how thoroughly you study something you did not create, there are always questions about how exactly it works or the reasoning behind some solutions.

Link: https://github.com/PopovMP/json-db

I need to update and prepare several more components before assembling the backend server. I'm using parts of my previous projects to assemble the necessary libraries.

Extracting the code into separate modules makes it easy to optimize it or to find problems.

Another essential concept is Unit Testing. A unit test is a small program that tests the main program.

The JSON-DB has 87 unit tests.
Each test has a short description and checks whether a function gets the expected result when given particular parameters. All tests must pass before publishing software.

Example:

✔ dbProjection gets complete doc given {} (0.7249ms)
✔ dbProjection gets complete doc (0.1449ms)
✔ dbProjection gets partial doc (0.1486ms)
✔ dbProjection does not get _id by default (0.0871ms)
✔ dbProjection accepts excluding values (0.1057ms)
✔ dbProjection does not accept mixed values (0.9165ms)
✔ dbQuery gets all _id if the query is empty (1.1526ms)

Have a great holiday season!