Tobias

I think it's looking better, I have organized better my css files with some new button animations

Added FaQ and fixed some button issues and styles

I have changed minor css details for a better look

The web site is almost done, I forgot to publish my devlogs before. I need to prepare some things for deploying it

Readme updated

I've completed the documentation for using Esolang with pre-selected playground examples to illustrate its use.
I've used AI tools to help me translate and format the project's Markdown file.

Fixed some bugs and update readme file

I made some changes in my docker config in order to use .env vars for my MONGODB_URL and redeployed it to DockerHub

I designed my playground with two main sections: code and output. The code is written in a text area that logs changes and is passed to the compiler when the run button is pressed to display the output with logs and errors in different colors, if any.

Now I have a way to communicate errors and continue with execution program (orange color), if it's not catched, the user get error text (red color)

Now the language allows calls to subprocesses that are declared with tags similar to xml and return a value that can be assigned to a specific variable.

Rn I can assign vars values, make operations (+, -, *, /) and log values

After struggling a bit with registering variables and their values, I decided to save them in JavaScript objects. The compiler checks the syntax of the Main function, evaluates its lines of code, and proceeds to perform operations and assignments of type: (a = 2), or operations like (a = 3 + 5).

I was going to try using regular expressions, but in the end I considered implementing the parser functions myself using array and string methods to do syntax validations.

I've defined the basic structure of my Esolang and what a program in this language should look like.
The scope of functions and the main process will be separated into tags like those in HTML, and the attributes will define inputs, outputs, and auxiliary variables used in the process.

I have completed the configuration of the functionality to generate PDF from an image.
It was a little more difficult than I thought, as I was not able to get the image dimensions before adding them to a PDF page.
In the end I was able to figure out how to get it all to work and did the deployment at https://enjoypdf.netlify.app/.

I have completed the development of the functionality to extract images from PDF. You are prompted to upload a file and then you can download the images individually or all together as a .zip file. It's a job where I had to do a lot of research to choose and implement the right libraries without asking an AI to generate the code for me.

PDF merge design and functionality. The field to load multiple PDF files was added, type validations are made, the merge is performed with the “pdf-merger-js” library and then displayed as an iframe on the page.

I have completed the design and structure of the home page with cards that allow navigation between the sub-pages of my application tools.

I've created the basic layout for my app, including route navigation.
I decided to use Ant as my CSS library because of its customization and large number of components, and because I wanted to use something different than Material UI this time.

I have completed the Electron setup for my app. It was a bit difficult at first because I had to install other packages on my Linux operating system, but after some reading and browsing through several tutorials, I was able to run my app in web and desktop mode and perform the builds.

I just create my react app using Vite and setup react router

I've finally deployed the project in render mode. You can visit it at: https://fireresty.onrender.com.

Sometimes it may take a while for the app to load while it's in downtime, so please be patient.
I'll be working on version 2 soon, so feel free to suggest changes and new features that might be helpful in improving the app.

Endpoint features added with CURL commands to interact with Firebase using fireRESTy

I have completed base features on backend
- Schema generator from firebase data
- Save schema snapshots
- Access to collections data via http from frontend
- Docker containers from frontend and backend
- I'm using mongodb as my db

Endpoints and schemas views with mock data
TODO: backend connection

I'm working in firebase web client frontend
Features at the moment:
- Upload JSON with credentials
- Encrypt JSON data and save in local storage
- React context to manage global state
-Table data view completed with mock data

Next:
- Http client with auth headers to request Firebase data
- Save Firebase collections schema versions

I have developed the encryption and accessing to Firebase project data process

I have configured base components for data management: form, table and json schema preview

I completed the frontend Layout using Material UI and React router for routing

TODO list: created
Ok, I know what I have TODO
I only have to code the features :(

I just created my react and node js app as the starting point
Let me cook