Is swatchtime.online open source/open to contribution? #3
Replies: 4 comments 4 replies
-
|
Hi, thanks for your interest in the swatchtime.online Preact app. I previously did not have the visibility of this one set to public. But, I changed it. I do welcome contributions to the code. Just fork the code to a new branch, make any changes you'd like, and open a Pull Request and I'll check it out and then merge the changes. I appreciate your offer. The public repo is here: |
Beta Was this translation helpful? Give feedback.
-
|
I also released it under the MIT license to make the status more clear. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! First I'd like to share a comparison between https://beats.wiki, this site, and a prototype I've started on.
✅ -supported, ❌ - not supported, 🚧 - needs more work, 📋 - todo * Clicking the header shows an explanation, but it is almost impossible to discover Questions for you:
|
Beta Was this translation helpful? Give feedback.
-
|
I like it. The UI is nice. I haven't used Qwik before but if it uses similar syntax to Vue/React I should be able to figure it out. So, what is the plan for future dev work? Port existing Preact code to Qwik and implement new features to https://github.com/cmbartschat/beats? Do you have a roadmap / spec? Your list above was quite helpful. It seems you have quite a bit already implemented. Maybe come up with a list of features not yet implemented and break them into subtasks? There are some features I like in the settings of my Preact app like -- ability to hide centibeats, ability to switch between 12/24 hr time, ability to show regular time along with beats, ability to change font, color, etc. In the case of your app I'd like the ability to show/hide the background image. Sometimes I like to set up a display with big fonts with high contrast and run it in the background like a clock. Having a plain LED-clock looking interface can be nice. But, I think that users should be able to customize their clocks however they want. That's why I put it all under settings and used checkboxes. I like how you set up the conversion. Reminds me a bit of how this dev does it: https://internet-ti.me/@940. I'll download your repo later and check it out. I might just keep my Preact app as is. I'll try to build your source locally later and set up a dev environment. It's nice though. As you get the code to a more mature state I can offer feedback about UX and features too. But, it's a solid start. The "Reminders" part isn't easy. I went down a rat hole on my app working on that feature. There are a lot of edge cases to consider. I did add permissions for browser notifications. But, I think the better way to do reminders would be to have some sort of calendar / iCal / CalDAV integration and use native notifications or push notifications that the user opts into. The version I came up with only works on certain conditions and if local storage gets dumped it's all gone. But, storing everything in a db and using logins or custom tokens and push notifications would solve a lot of issues. I just never got that far. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I don't see a repository for it. I am interested in supporting the effort.
Beta Was this translation helpful? Give feedback.
All reactions