#WIP: resources page
1 messages · Page 1 of 1 (latest)
Here's the current issue:
I've got the counter of the promise that also exceeds 100 ticks so not sure what's going on, path to fxserver and monitor folder are good also
:rocket: Congratulations @rigid dragon, you leveled up to <@&828359841512816671>!
v20.17.0
I am gonna blame the million spaces in the path
How are you running it?
Fairpoint
inside core/ with npm run dev
can you show me what appears when you type that?
Stupid, forgot to mention the readable stream error from the discord js module.
I don't think it's the spaces in the path, but I can give it a shot in a new directory
Did an npm audit fix, could that of been it ? Just saw the uncommited changes to the package files ?
THe main builder was just my line for the path for fxserver
which fxserver build are you based on?
type
git remote get-url origin
i think your branch might be a bit too old
i recommend just cloning the txAdmin repo and reapplying your resources.ejs
That's just returning the url of my fork
Yeah, I'll give it a shot
I'll give it a shot tomorrow, running on fumes at the moment
I was only up to date on the main branch ðŸ«
RIP
Well actually no, 😂
Yeah, not the time to try again
If I remember properly it was the table class coupled with the table-outline that where messing with it.
But you can't just remove table or try to override with style for the border radius. Iirc was a while back
What's wrong tho? When I create a new build it just works out of the box 
A series of fuckups on my end, that's the problem when running on brain fumes🤣

Let's say that One evening I wanted to mess around and try stuff out.
I started using pnpm for some reason, got tired and interrupted the download to shut off the PC saying I'll reinstall tomorrow, next day I use npm.
And I actually was up to date on the develop branch 😂
Now it all works 😂
Sorry about last night 😂
Nice
Now the fun bit, I still can't find an adequate solution to put some border radius on the tabs, because the table class seems to just put it's stiff right over it again, it's there without it being there
maybe just disable the radius
or maybe just do whatever
I am not particularly caring of the maintainability of this particular code
eventually it will be migrated to react
What are you trying to do anyways @rigid dragon ?
make the resources page not suck for anyone with over 50 resources
i have big ideas on how to better do it on react
but not priority 
I want to get resource cpu/memory usage before i remake this page, though
and instead of showing all the resources, on the left it will show just the folder structure with buttons on the right to stop/start the resources in the cartegory
then in the middle of the page it will just show the resources from the folder you have selected
and if you don't select any, it will show "recently added resources"
and for each resource there will be option to auto restart them on changes (for dev purposes), or to see if they are outdated, button to update them, button to configure them, button to add/remove from auto start
...
it will be cool af

Why tho
Will it get merged in the legacy page at all
Like do you want any changes to that
How would you check if they're outdated ? Using the repository key in the manifests ?
Because at one point It started annoying me to go look for specific resources on my dev server, so I changed the UI
The current page is kinda unusable for a lot of servers, and although I personally don't want to put time into improving the current page, if someone feels pressed to do so I can help.
and i've a feeling it will take over 6 months before I even start drawing the new resources page UI

Still unclear for now, maybe git, maybe some api, idk... all i know is that ppl not updating is a pathology of the ecosystem that I will try to cure.
Big hopes
Maybe two methods ?
- if the repository url in the manifest is git use the latest release tag (even if there are some that don't use it)
- if the url is anything else it should simply return the latest version tag ?
@rigid dragon I guess you were not the only one

ffs
idk how to fix this crap
super, it doesn't work on node 16

Ouch, can happen to everyone. Is that from my branch ?
No, just discord.js with its annoying dependency tree
Fun
@rigid dragon Did you manage to fix the table corners?
Still stuck on it, can't seem to force it on top.
Maybe trying to recreate the table styling could solve it but that seems like a lot of hassle.
@rigid dragon Forgot to read discord, I just changed and merged it
nice embed
I rewrote the collapse/show code, made them all start showing (more user friendly)
and changed the layout and button
No probs, looks very good as well, wasn't sure which would be the best between the slider and the button.