We have a development in progress that was shared by @pacman, which we put on hold to prioritize the general foundation, organization, and development of our data.
That spreadsheet could be linked to our data in Budibase or a similar tool (preferably self-hosted) to mix the info directly with the community profiles.
What are we looking for?
The spreadsheet should update automatically in Budibase or a similar application, which would also allow us to work with our own DBs (Postgres).
La base de Criptonautas intenta estar cerca de lo más moderno, privado y desarrollado a nivel “comunidad”. Y ahà veo que los frameworks sobre Javascript tienen un chingo más de support.
Desde ya que la base suma muchĂsimo! Pero toca continuar, para que tenga cercanĂa con nuestra realidad actual.
Javascript y CCS estarĂa bien, porque no tenemos nada en Boostrap (y casi todo migrĂł para Tailwind pero tienen muchas clases que no se usan y sobre-carga todo de gusto).
Thanks! In principle, I was thinking of building it from scratch, maybe I’ll reuse the existing pure JavaScript code. Since I’m not using Bootstrap and instead using CSS for responsiveness (I’ll also add the CSS you sent me), I need to take a good look at it and implement a save option right from the start, because the last time I made it with multiple options, it got complicated. I’ll just use what you sent me and that’s it. I’m figuring out how to approach it—whether to keep everything on one page or separate each screen into different HTML files. I looked into making it a PWA so it can be installed, and for anyone interested, this link explains that methodology/pattern: https://web.dev/learn/pwa/
I’ve started working on it. Basically, I’m going to use Bootstrap without JS, and once I have that set, I’ll rename the CSS classes by adding -custom so it’s easier to adapt later; otherwise, I’ll spend more time on CSS and HTML than on adding the pure JavaScript.
As for the data, I’ll see about saving it in the browser’s localStorage instead of IndexedDB.
The idea is to add a dark mode, but for now, I am sticking with light.
I still need to add the Admin section, which will mainly be used to, for example, modify the mode, upload or download data, and a few other things.
As seen in the image, the form to load a trade is only shown if you click on + trade or if you are editing one; otherwise, it only shows the table with the information.
In the upper part of the table, I still need to add the totalizers that were there, as well as a way to filter the data.
…
Once the above is done, I will upload it to the repo, although we would have to delete what exists first.
I’ll be uploading progress updates bit by bit. I’ve added the bar I mentioned to filter trades or perform searches, along with the totalizers for AVG Return, AVG Hits, MAT, FK, and messages. We’ll need to double-check the calculations for those later on.
Data filtering applied, admin section added with data import and export, and I added the ability to replicate trades.
I am working on data filtering via search, making sure it adapts well to mobile. I’ll leave the dark theme for later, and I think after that I’ll upload it so you can test it to see if the calculations are correct. Some are, but I’m in doubt about others, for example, the MAT and F.Kelly (FK), as well as the ones for each trade.
No problem at all! Regarding the previously associated repo, it can be deleted and a new one created with the same name; however, it’s not letting me do that at the moment.
Ah, okay! Yes, in the original, I can edit/delete/create another, etc.
As for whether to use one or the other, honestly, Tailwind is more customizable, and Bootstrap is more like having things already made. You can customize Bootstrap too, of course, but that’s more for an expert frontend developer or someone who specializes in it. In my case, I used Bootstrap because it’s the one I know best, and using native CSS or Tailwind takes time to learn (I’ll take a look at Tailwind later to see how it is). But for the meantime, what we have works well enough to get the functionality going, and the CSS can always be changed later.
I compared the CSS for both (I only use Bootstrap’s CSS, it’s just one file); the Tailwind CSS file is 355kb and Bootstrap is 228kb. Although, in Tailwind’s favor, it finished in 3.25ms compared to Bootstrap’s 3.51ms (in both cases locally).
