cv VS atbswp

I'm working on a new version of my CV (v1: https://cv.git-pull.com)

This time I'm writing it in React, Angular, and Vue (TypeScript across the board). It's in the very early stages, but keep it at https://github.com/tony/cv

While doing it, I've tried to find various ways to share the chart and data code across all 3 versions. The library I found to make it happen with data akita: https://datorama.github.io/akita/

For UX it's not so easy. The truth is, some of the best UI libraries are framework specific. This creates a lot of fragmentation in the frontend community IMO. For instance react has nivo, vicious, and react-vis, but at the end of the day it's svg and canvas underneath the hood. Still though, the efforts are amazing. It makes you wonder what it'd be like if there would be just one agreed upon way to write a widget. (There's web components, custom elements... but those won't even work with typescript out of the box)

In the past few years, that stuff that's been going on with webpack v5's persistent caching, TypeScript (and its tooling), and all 3 of these frameworks getting better is amazing.

Examples of charting software I've tried: https://cv-react-v2.git-pull.com/dev/branch/v2-billboard.js/, https://cv-react-v2.git-pull.com/dev/branch/v2-plotly/, https://cv-react-v2.git-pull.com/dev/branch/v2-carboncharts/

For the first time I've found a UI suite called Carbon: https://www.carbondesignsystem.com/, an IBM thing. I'm most impressed by their chart offering. Even though it's relatively new, they maintain bindings for react, vue and angular.

This book is definitely a good starting point, and if you want a glimpse of what you can achieve with an automation library (pyautogui in the case of the book), do check out atbswp

Using the library of the author pyautogui, I developed a macro recorder atbswp (Yes like the book) which makes it very easy to automate boring tasks, do check it out.

Seems I am late to the party. Anyway, if you like automation, check out atbswp

Shameless plug, you can do the same with this[0] albeit not in the CLI.

0: https://github.com/rmpr/atbswp

Source: I use both in a project of mine atbswp

I just released a new version of atbswp I intend to start working on the v0.3 (or 0.2.1 not sure yet)

Just to add options on top of QT5, there's also wxPython. It's pretty good, and fwiw, I use it for this project not the most convoluted GUI out there but it works. Iirc there's also Pysimplegui but I never used it.

Not necessarily, you can use a CI pipeline to verify that your project can be build with many Python versions. This is the workflow I use here[0]. It makes catching and fixing breaking changes easier. Plus, I'm confident the core team is not likely to introduce a painful breaking change (think Python 2 -> 3) soon[1]

0: https://github.com/rmpr/atbswp

1: https://mobile.twitter.com/gvanrossum/status/130608247244308...