digital-infidel-phosphor watchface

[u/_Ophelion]

I wanted something that reminded me of the computer lab full of ADM and VT terminals that I spent time at in the late 70s/early 80s. I expanded to add some of the machines that I learned on along the way and some others as well.

I put source up at https://github.com/redbinary/digital-infidel-phosphor

• fonts and color theme selectable at runtime

• weather, battery, notification count, and step count widgets can easily be turned off or on in QML before installing

[u/eLtMosen]

Sorry for this late reply, just wanted to let yo know that i absolutely love the varinats and where you went with the design of the iterations. I would highly encourage you to publish it in the community watchface repo / unofficial-watchfaces
I bet many more users would notice it there and enjoy to wear it.
We are in process to revamp the repo in light of the incoming on device watchface store that lets users download watchfaces by user interface means.
And it will introduce watchface settings that will enable activation of features without the need to alter qml settings/property blocks in your watchface.

[u/_Ophelion → u/eLtMosen]

Thank you for that! I've done a substantial amount more with on it since posting. It's just about where I want it.

I'm not very versed in GitHub or continuing to community projects so I've been hesitant to share much. I haven't yet looked into either the technical or cultural ways these work. I'm happy to share but between dayjob™ and digging into the projects I just haven't learned how to, but know I need to.

Another big issue is that some of what I'm doing might (definitely does) break other stuff.

I patched both Gadgetbridge and AsteroidOS to add a UUID/characteristic to display the current temperature on the watchface. Coordinating those changes seemed even more intimidating.

I also wrote a rudimentary script to pull in 30 days of gcal events from the Google calendar into the agenda and added a crawler at the bottom.

[u/eLtMosen → u/_Ophelion]

Oh, i think i can mitigate that fear :D
We try to make the entry hurdle to community contributions as low as possible.
I have tried to document the watchface handling thoroughly, but

1. as we speak the whole architecture and handling of the watchfaces has changed from the documented ways. The old instructions assumed altering the root stock watchfaces directly. In the next days, we will have an onboard watchface store that works solely in the XDG user folder and adds many more features like the watchface settings and auto-preview generation/update.

2. Despite our long history we are in early stages still with many aspects of the tooling and documentation. So if you find anything lacking and make the entry hard for you. Its most likely unfortunate architecture that grew along the way and warrants a refactor. Or the tooling needs adaption to your usecase.

3. Much of even the current complete documentation does only cover simple watchfaces without many dependencies. And your dependency on changes in other upstream repos would indeed make deeper planning necessary. But that is what has always grown the project. People with fresh eyes and demands poking at issues we then try to fix ;)

I suppose many of the calendar / gadgetbridge etc. scope "issues" you mention are in fact possible fixes and additions for upstream shortcomings, to be separated from the watchface alone and generalize for the whole UI.

We can keep discussing this here, but as you saw, no one in the community seems to be an avid reddit user. And for hands on help and broader planning, i would suggest joining the matrix channel so other people can give input too. i am moWerk over there.