[Please read OP] Aviate: create dynamic, component driven statuses on the fly (aviate.scratchers.tech)

NFlex23

Please read this post: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/post/7878515/

Last edited by NFlex23 (March 23, 2024 12:54:53)

ToastersUnited

Amazing!

NFlex23

ToastersUnited wrote:
(#2)
Amazing!

Thank you, it means a lot to me!

ToastersUnited

NFlex23 wrote:
ToastersUnited wrote:
(#2)
Amazing!
Thank you, it means a lot to me!

https://aviateapp.eu.org/api/ToastersUnited
Might use this in my projects!

NFlex23

ToastersUnited wrote:
(#4)
NFlex23 wrote:
ToastersUnited wrote:
(#2)
Amazing!
Thank you, it means a lot to me!
https://aviateapp.eu.org/api/ToastersUnited
Might use this in my projects!

Of course, use it as much as you like!

Chiroyce

I'm beyond impressed with the looks of the site..

god286

Nevermind, but, I would keep a lookout on your env variables, make sure no mention is in the frontend JS

Last edited by god286 (April 7, 2022 04:31:28)

Jeffalo

this is pretty cool! the website looks really neat, and the status components could be very useful.

i'm just a bit concerned that now we have two competing standards for statuses. perhaps we can come to some sort of middle ground on this?

-gge

ocular 2

Sid72020123

This website is Cool! I like the design.

mbrick2

"[error] Unexpected token < in JSON at position 0"

-EmeraldThunder-

This site looks amazing, the status feature is really useful and the UI is very modern.

Pufferfish_Test

Nice clean look, my only complaint is the cursive font - please consider changing that

Chiroyce

Pufferfish_Test wrote:
my only complaint is the cursive font - please consider changing that

agreed - it looks a bit awkward around the normal font

NFlex23

Chiroyce wrote:
(#6)
I'm beyond impressed with the looks of the site..

Thanks, I took me a while to perfect it, but I'm pretty happy with it now.

god286 wrote:
(#7)
Nevermind, but, I would keep a lookout on your env variables, make sure no mention is in the frontend JS

Don't worry, the env is only in the backend; I made sure of it.

Jeffalo wrote:
(#8)
this is pretty cool! the website looks really neat, and the status components could be very useful.

i'm just a bit concerned that now we have two competing standards for statuses. perhaps we can come to some sort of middle ground on this?

Thank you! I'm not sure how we could do that, do you have any ideas?

-EmeraldThunder- wrote:
(#12)
This site looks amazing, the status feature is really useful and the UI is very modern.

Thank you.

Pufferfish_Test wrote:
(#13)
Nice clean look, my only complaint is the cursive font - please consider changing that

Maybe I'll add preferences in the future, also a dark mode would be cool.

NFlex23

Chiroyce wrote:
(#14)
Pufferfish_Test wrote:
my only complaint is the cursive font - please consider changing that
agreed - it looks a bit awkward around the normal font

I was experimenting with a lot of fonts before choosing Lobster and I do agree it does look a bit off. I'll try to find a better font.

NFlex23

I looks like ScratchDB is down, so don't worry if your status says " Unexpected token < in JSON at position 0". I'll try to make a better error message for this.

Edit: done.

Last edited by NFlex23 (April 7, 2022 12:20:20)

mbrick2

Suggestion: Studio Status

NFlex23

mbrick2 wrote:
(#18)
Suggestion: Studio Status

How would those work? Do you mean like statuses for studios?

Chiroyce

A bug: even when a status doesn't use ScratchDB or any tags, it throws an error - https://aviateapp.eu.org/api/Chiroyce

Discuss Scratch