#UI rendering

[buglaur]

the saloon crew 🍻

[paradoxbeta]

unparalleled innocence, tada!

ui is an interesting character to me because they have so little canon characterization, so theres tons of different ways they can be interpreted. what i know for sure is that they have some sort of emotional investment in whats happening to 5p, which opens up a myriad of possibilities for their personality and thought processes. did they know 5p prior? are they morbidly curious and attracted to disaster or concerned on a personal level? why did they find it acceptable to publicize pictures of 5p's rot? i like to lean more in the direction of a shortsighted but well meaning ui, mostly because it fits into rain worlds lack of outright villanistic figures, and puts ui in the same boat as srs of trying to good and having it go very wrong. also, i feel like good-natured ui doesnt get as much representation despite being as equal a possibility as malicious ui. in the end though theres tons of different possibilities for their character that fill their role in the story and i love to see all the interpretations

[searchsystem]

Nuevo.Tokyo™ / Japanese Gradient [For UI] / Gradient / 2024

 Download

[webdiggerxxx]

꧁★꧂

[undertakeruo]

GENSHIN IMPACT | EVERY ARTIFACT ARTIFACT SET (4.4 IN DEPTH) [UI • VFX + PSD]

|DRIVE CONTENT| 3* 4* and 5* Artifact Sets that exists since 1.0 to 4.4 (Feb 6th, 2024)

Adventurer´s • Archaic Petra • Berserk • Blizzard Strayer • Bloodstained Chivalry • Brave Heart • Crimson Witch of Flames • Deepwood Memories • Defender´s Will • Desert Pavilion Chronicles • Echoes of an Offering • Emblem of the Severed Faith • Exile • Flower of Paradise Lost • Gambler´s • Gilded Dreams • Gladiator´s Finale • Golden Troupe • Heart of Depth • Husk of Opulent Dreams • Instructor • Lava Walker • Lucky Dog • Maiden´s Beloved • Marechausee Hunter • Martial Artist • Nighttime Wispers in the Echoing Woods • Noblesse Oblige • Nymph´s Dream • Ocean-Hued Clam • Pale Flame • Prayers for Destiny • Prayers for Illumination • Prayers for Widsom • Prayers for Spring-Time • Resolution of Sojourner • Retracting Bolide • Scholar • Shimenawa´s Reminiscience • Songs of Days Past • Tenacity of the Milleleith • Thundering Fury • Thundershooter • Tiny Miracle • Traveling Doctor • Vermillion Relief • Viridescent Venerer • Vourukasha Glow • Wanderer´s Troupe....Oof!

[underfuckkeryu]

GENSHIN IMPACT™ | ELEMENTS [HQ]

(The Drive contains all sorts of elements in the game: Glowing x Flat Color x Genius Invokation TCG x B&W x Golden)

[yin-shimo]

Introducing “Heatr”

— AKA the only ‘dating’-app you’ll ever need to satisfy the needs of your Heart… and Heat! Our advanced customizations helps you navigate our app and ensure you find the perfect person(s) to share your special “H” with! 😉

Filter out certain demographics like primary gender, secondary gender, age, location, and what you’re looking for!

Want something casual or long-term? We got you! Looking for something open or are polyamorous? We got you! We also feature an option for those looking for something out of the ordinary like a queerplatonic relationship !

At Heatr we ensure our app is inclusive to all by featuring non-binary as a third option, as well as a custom option to use for whatever primary gender label fits you best!

— Love from the Heatr team❤️‍🔥

gloryhole twink finally has a name!!! and he’s a liar!!!!! he is very much an omega !!!🤫🤫🤫

[goldiipond]

yah

[saelrum]

Iterators x Mekakucity Actors songs – part 1

[illdothehotvoice]

I'll complain about it here too actually. If I had one thing bad to say about Brothership so far it's this UI looks so bad fjfjfjfdf. It's not nearly as visually interesting as past games and I really really hate the minimalistic approach studios have been taking towards UI lately like it really just feels like an afterthought.

[molynomials]

hot take i think

with how femc fans took the news of her not being added into reload due to time/money restraints im so glad persona fans arent in the game development industry holy fucking shit

[macleod]

Musing on remaking the browser (and internet) as we know it.

HTML+CSS is by far the best 'component' library there is, but JS really tends to be the main cause of bogging down the entire thing and drowning out the performance gains.

The idea is something along these lines (this ended up being far longer than initially intended):

HTML Viewer, directly from a plain HTML source, I've even considered using a headless browser, taking a 'photo' of the webpage, and then laying out a bitmap onto it, might not be needed, but could be cool and useful.

Once a user, or a function 'clicks' or focuses on a section of the bitmap, then the embedded language uses this is as a target selector to manipulate the data of the HTML viewer source, directly without page loads. Similar to an SPA but, without JS, similar to 'hot-wire', but again without JavaScript.

a separate database built into the 'browser' similar to indexdb, but likely something more similar and powerful such as SQLite with permission guards for applications (think OAuth, running locally).

This would obviously change the dynamic properties of a 'browser', and would make it more akin to an enhanced PDF editor with dynamic input (pop-ups instead of dynamic forms, etc.). But, I am starting to believe the problem and performance issue of the browser is less the sandbox (which this would enhance), but because we've forced a data language into what should be a static component library with targeted source changes.

This is a difficulty that we're seeing the weight of, we only have two major browser types, two engines. There have been so many attempts to recreate them, but they are all attempts at recreating the worst parts of a rendering agent that combines and forces the merger of highly volatile dynamic data into static components.

They have said for years that no one can 'make a new browser rendering engine' because of how many variables and issues and decades of bad choices and changes from the infancy of development.

Gopher, and the similar, are interesting projects, but they lack in several regards: data entry, minimal schematic support for modern HTML and CSS capabilities, and they are attempting to recreate an entire protocol. The protocol we have for file and web transfer is excellent, despite its shortcomings, but it is highly stable, reproducible, and effective.

If we were to remove 'dynamic' capabilities, such as forms, or text boxes, and all that JavaScript entails, the HTML viewer would be minimal for performance. The embedded language on top would hold the data separately from the process—rendering inputs to be sanitized and standardized. If the browser fails, your data would be backed up, you would have a complete revision history of all data ever processed, and you would have. This is likely the path forward for something akin to the Solid Project, where you own your data.

Every 'browser' becomes your own personal data temple or silo, and every web page becomes 'server-side' generated and modified with targeted manipulation or key:values from the integrated (stateful) database by your locally running browser.

When you go to someone else's website, most of which is just static content anyway, you get the HTML source, and the source for a/any(?) scripting language that would use the values from the browser overlay tracker for targeting to rewrite and submit specific HTML components.

The manipulator overlay would be an entirely separate process, with a simple message transfer between the two. This entirely separates your data into a stateful persistent object (no more losing your form data as you type due to a reload, or failure, or anything else, with full history) and your dynamic script, if a site needs it (most don't), would be in its own process. There would be a message transfer queue, likely using the built-in database with @\tagged hooks for event dispatches.

You would be able to have fully sandboxed, extremely performant, websites, while owning your own data. The browser as a server HTML renderer, the webpage as an “image” (sort of), and an 'overlay' selector for an embedded image to submit changes to individual HTML components.

If you were to separate it into three extremely slim, minimal, processes, with an integrated database with OAuth style permission switches. You would have just created a new browser, and a new way for the web to work, using virtually no memory, enhancing security, and with far less complexity. In a way, this would turn the web into a 'native' application.

You also would have quite a bit of backwards compatibility to the pre-NewWeb.

You should own your data, websites should be static, data should be dynamic, and browsers should be performant.

Just some musing on the topic, I'm working on something similar, but not exactly in regard to this—so maybe I'll spend some time and add it to the ever-growing projects list.

[veveisveryuncool]

"oh animating was so much fun i wanna try doing it again" YEAH RIGHT. SHITS HARD I REMEMBER WHY I STOPPED.

[mira0000000-blog]

Touched blender again yey

[witchblade]

i missss frapppsss my beautiful customizable one-key save screenshot program