#Partisipate 0.1.0 (the new desktop Qt client for #Coventry #Apollo) is now out on #codeberg.

This is the dash screen of #partisipate which downloads a roster from the #apollo integration server and registers on the #coventry call server. It also suggests what I am thinking about for the #syndyoceras desktop #mastodon client, where timelines and followed tags would be in a tree view on the left and the current timeline on the right.

With this weekends release, #apollo, #coventry, browser clients, generic sip devices, #babylon automated endpoints, and #partisipate desktop softphones will finally begin being developed and operating as a true cohesive whole, and recently neglected #bordeaux will soon be added for application driven media services.

I will have to move #apollo into gnutelephony as it is a requirement for #partisipate. #Coventry will generate and provide bearer tokens during sip registration, and apollo web services will be used for all those functions that cannot easily be mapped into generic sip, such as rosters, room maps for visualizing lighting, and dialing directories.

I did a very early initial release of #partisipate, the #Qt softphone client for a #Coventry/Apollo/Bordeaux phone system. This only does registration, that's it, and was done mostly just to setup packaging processing. Much that will come into partisipate will eventually come from the older #SipWitchQt client.

Meanwhile the newly introduced #Apollo server will finally make it easy to admin a Coventry phone and automation server from a browser. Finally, there will eventually be a dedicated cross-platform #Partisipate soft-phone client, though any sip application or device should be usable.

Other parts of a coventry phone system have been in development and #foss licensed for awhile, including the coventry call server itself, the #bordeaux media application server, and the #partisipate softphone client. Other parts still pending include a sip to #x10 adapter bridge and a sip #ai driven voice assistant.

#Qt applications, including those made with qt6, integrate application menus fine. So #partisipate integrates fine with hud @tio . Some Qt applications, including #QtCreator choose to use fonts in the ui significantly below the default desktop point size, and that is useless to me. Scaling only oversizes things which already use correct font sizes. Qt needs an env setting to never go below pointsize X if set, or people should stop making apps that use tiny ass fonts for important ui elements.

Now that a #partisipate client is at least started on @Codeberg at least two more things will be needed for 2024; a #troll gateway controller, and a #cardaver integration/collaboration server. Then everyone can be #beswitched with #switchcraft living on a pi-like device, which would kind of bring us back to what I originally had wanted to do with #sipcraft#voip #telephony last decade.

I may end up looking at @tromjaro_wrafzh a lot for working on #partisipate because @tio has done so much work on ui behavior and theming, and that should help me see what's broken in my app. It's also why I decided to have a menubar (that can also be hidden).

As no communication vendor seems to care to work on such things or to do facility automation, I will eventually offer such a platform, including the #partisipate client.

Though it doesn't actually do anything yet, the basic structure for the #Qt #partisipate client does exist, and I could drop that into a public repo. @Codeberg

Dark theme screenshot of login for a dedicated #coventry client to be called #partisipate written in #Qt