<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Gradio auf Nicky Reinert</title><link>https://nickyreinert.de/en/topics/gradio/</link><description>Blog &amp; projects by Nicky Reinert (Institute for Digital Challenges): web development &amp; software development, SEO &amp; analytics, hosting &amp; DevOps, WordPress &amp; Hugo, tools &amp; projects, data protection &amp; digital culture — plus content on AI and autism &amp; society.</description><generator>Hugo 0.148.2</generator><language>en</language><managingEditor/><webMaster/><copyright/><lastBuildDate>Sun, 05 May 2024 12:34:56 +0100</lastBuildDate><atom:link href="https://nickyreinert.de/en/topics/gradio/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Persist User Configuration in a Gradio App with Cookies</title><link>https://nickyreinert.de/en/2024/2024-05-05-gradio-app/</link><pubDate>Sun, 05 May 2024 12:34:56 +0100</pubDate><author/><guid>https://nickyreinert.de/en/2024/2024-05-05-gradio-app/</guid><description>I am currently building some kind of playground for Huggingface’s text-2-image models. This app offers more than a dozen configuration parameters. The problem: Every time the user reloads the page, all parameters are gone. Here’s my solution to cope with that.
Gradio has a gr.Stateobject that allows …</description><category>blog</category><media:content url="https://nickyreinert.de/gradio-cookies.png" type="image/jpeg"><media:title>Gradio App Configuration Persistence</media:title></media:content><dc:subject>Lesezeit: 5 Minuten</dc:subject><dc:type>tutorial</dc:type></item></channel></rss>