friendica (DFRN) - Collegamento all'originale
The media in this post is not displayed to visitors. To view it, please log in.

L'#accessibilità della #pubblicaamministrazione

comune.cadorago.co.it/novita/a…

la pagina: "Avviso! la carta di identà di cartà non sarà più valida! Vedi Allegato!"
l'allegato: jpg

questo: comune.cadorago.co.it/halley//…

dovrebbero smettere di metter li gente che sa solo mandare meme su uassap nel gruppo "buongiornissimo"

Comune di Cadorago - Nuove disposizioni sulla carta di identità - dal 3 agosto 2026 le carte di identità cartacee non saranno più valide (vedi allegat

www.comune.cadorago.co.it
#pubblicaamministrazione #accessibilità

reshared this

in reply to akiran_n

friendica (DFRN) - Collegamento all'originale

Fabio

@akiran_n la grafica è uguale più o meno per tutti perchè segue delle linee guida agid.gov.it/it/linee-guida

Di produttori che vendono soluzioni chiavi in mano ce ne sono diversi. la grafica è più o meno simile, la parte tecnica no.
Da un veloce giro fatto ieri sera ho trovato almeno quattro diverse soluzioni da altrettante società che gestiscono diversi comuni nel circondario.

Il grosso problema, secondo me, è chi poi va a scriverci in questi siti.
Non puoi mettere una news "cose importanti da fare: vedi allegato" e l'allegato è una jpg a fondo azzurro e testo verde che sembra un meme girato via uassàp.

E' l'antitesi di quello che dovrebbe essere quel sito. E' l'opposto del concetto di accessibilità. Quella immagine faccio fatica a leggerla io, che ok che porto gli occhiali da lettura, ma non ho problemi di daltonismo.
Oltre al fatto che vado sul sito, clicco sulla news, clicco sull'immagine e da li devo aprire un'altra finestra del browser per copiarci l'indirizzo che è scritto nell'immagine. Perché non è nel testo? Perché non è cliccabile? Perché c'è gente che ha la competenza informatica di un tasso del miele con il compito di tocchicciare il sito con le manine appiccicose?

@akiran_n

friendica (DFRN) - Collegamento all'originale

Confy 0.9.0

Oh, hey. #confy 0.9.0 has been released!

In this version

  • Automatically update schedule when cache expire. Before it was updated only on open.
  • New and improved page navigation logic
  • Improved handling of shortcuts
  • Fixed the sidebar: no more out of order items when opening new conference
  • Added the ability to clean the "recent conference" list
  • Fixed opening event page from "next up" notification

and some more small fixes

you can get it on flathub, your package manager or install from source

#confy

friendica (DFRN) - Collegamento all'originale
The media in this post is not displayed to visitors. To view it, please log in.

working on #confy while attending #guadec2025 :

Until now, schedule data was updated when opening a conference, if the cache was expired and the device was online. This means that if you keep confy opened and schedule changes, you'll never get any update.
Latest code update automatically the current open conference schedule when cache expires (if online)... thinking about it, maybe there could be some sort of "diff" when something changes...

The update process now also should delete removed events from cache, hopefully (like the duplicated talks in that video...)

A small bug introduced recently that prevented to correctly open talk detail page from "next up" notification has been also fixed.

Meanwhile I was thinking that this thing needs a full rewrite on how data is stored. Right now every conferences gets its sqlite db in user's ".cache" folder. The db store schedule data and user stared talks. This means that if you clear cache, you lose you stars.
This data should be saved in another place, be another db in ".local/state" or maybe in dconf... 🤔

#confy #guadec2025

friendica (DFRN) - Collegamento all'originale

Some work in progress in Confy

You know, Confy: the Gnome-based, mobile-friendly Conferences schedule viewer

Some days ago I posted a screenshot about an experiment I was doing with #confy , which atm is on hold.
I'm still looking about the best way to draw a calendar view which can be zoomed in and out fast.

This is using Gtk.Snapshot to draw boxes and Pango.Layout to draw text.
It's still not fast enough with large conferences (mostly because I want to keep the text the same size and just change the boxes...)

Meanwhile I made some other things: some are papercuts, some are to try to have cleaner code, and some are quite big changes:

Actions get enabled/disable correctly per context

"search" action is disabled until an event is opened, and "copy" action is enabled only while a details page is shown.
Small change but prevents some errors.

Update recent list when deleting custom event from menu

Custom event in the "open" window can be removed. Now the entry is also removed from the recent events list.

Navigation sidebar has been updated

Now items does not get out of order after opening an Event with one already opened. Previously, items not needed (eg. 'Traks' where the Event has no tracks) were removed and re-added, which caused them to appear out of order.
Now the items are hidden and shown as needed, thus they do not change order anymore. Plus they are now defined in sidebar widget template. More clear and nice.

Navigation between pages has been revisited.

Originally, every talk details page opened was simply pushed on the stack. This caused some trouble as details page can link to other details pages via overlapping talks, which where pushed on the stack too. But overlapping talks are 'circular' as if Talk A overlaps with Talk B, also Talk B overlaps with Talk A, which can lead to very long stack to navigate back, e.g.:

List -> Talk A -> Talk B -> Talk C -> Talk A -> Talk C

In latest revisions, clicking on an overlapping talk was simply updating the page in place, losing navigation (and a nice transition between pages):
List -> Talk A
  user clicks on overlapping Talk B
List -> Talk B

Now, we are back to pushing pages on the stack, but if an event has ben already pushed to the stack, we pop back to that page:
List -> Talk A
  user clicks on overlapping Talk B
List -> Talk A -> Talk B
  user clicks on overlapping Talk C
List -> Talk A -> Talk B -> Talk C
  user clicks on overlapping Talk A
List -> Talk A

From my esaustive user testing (me while developing) looks like this could be a nice solution. The animation on page push/pop helps the user to keep track on where is going. At least, it helps me. Get used to it. :)

This is also relevant for the new Search page navigation.

Search can be toggled

Search action now is toggleable (is this a word?), the "search" button in the headerbar is now a togglebutton. One click opens the search, another click closes the search (as does ctrl-f).
When search is opened, the search page is pushed on the stack. Closing the search pop the page (and popping the page closes the search).

From the search page, talk details pages follow the same logic as before, but in a separate 'group'. That is, if the search page is opened from a detail page, and from the search page the same talk is clicked, we don't pop back to the already pushed page (which closes the search) but a new detail page is pushed on the stack:

List -> Talk A -> Talk B
  user clicks the "search" button
List -> Talk A -> Talk B -> Search
  user clicks talk C
List -> Talk A -> Talk B -> Search -> Talk C
  user clicks overlapping talk A
List -> Talk A -> Talk B -> Search -> Talk C -> Talk A
  user clicks the "search" button
List -> Talk A -> Talk B

I hope this make sense and it's usable :)

( btw: the search entry still get focused when the search page pops in. I'm quite proud I managed to keep that :) )

Updated Preference dialog

The design has been moved to template, with a simple custom widget to set caches duration.
Option to clear the recent opened events list has been added.

Everything is in git if anyone want to test it, maybe on some mobile devices, maybe during one of the upcoming conferences...

#confy

friendica (DFRN) - Collegamento all'originale

Mh.
last update of #archlinux defaults to #GTK4 #GSK #Vulcan Renderer:


(note: here I'm defining GDK_BACKEND=wayland because the terminal is in VSCode, which runs on XWayland and define GDK_BACKEND=x11. In VSCode because gnome console was a black rectangle too)

Yes, that white rectangle is the window.

I had to set GSK_RENDERER=ngl in .config/environment.d/gtk4.conf

#archlinux #gtk4 #vulcan #gsk

Diego Roversi reshared this.

in reply to Fabio

mastodon - Collegamento all'originale

Alessandro

Mario non sa fare il lavoro, Paolo sí.

Paolo con il macchinario di Mario potrebbe fare il grosso e poi fare gli aggiustamenti di fino che é in grado di fare con l'esperienza.

Io uso da due anni e mi ha velocizzato molte fasi del lavoro noiose senza impattare sul risultato finale, anzi a volte ho visto approci nuovi e interessanti facendo crescere le mie conoscenze di tubarolo.

É il vibe piping che é una 💩

Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.

⇧