dgp1130 / chatter

Simple chat application built with Flutter Web, NodeJS/TypeScript, Docker, and Kubernetes.

Howdy folks!

I'm Doug Parker, the "devel without a cause". I'm an overly opinionated software developer on the Angular team at Google. Web development is hard, so I build tooling that makes it easier. I love forcing web tools do things they were never supposed to do.

• Check out my blog with lots of crazy ideas, prototypes, and projects.
• Toot at me on Mastodon at https://techhub.social/@develwithoutacause.
• Check out my GitHub profile at dgp1130.
• Email me at [email protected].
• Historical tweet archive for @develwoutacause.
  • This account has been deactivated on Twitter, but all its tweets are archived here.

chatter's Issues

Library-itize showBlockingDialog

In the most recent client commit, I created a utility module called showBlockingDialog which shows/hides a dialog based on an existing Future object. This seems to be pretty useful, and I wasn't able to find any existing standard modules which did this (other third party ones might exist). Could be worth contributing this back as a package to the Flutter ecosystem.

Library-itize Flutter FutureValue

I recently had the idea of FutureValue, a Flutter widget which tracks state of a Future and provides an API to render that Future at all states (pending, completed, error). This feels pretty generically useful when rendering asynchronous operations onto a synchronous paint cycle. Might be worth separating this out into its own library for use by other Flutter projects.

Also need to revisit that name, definitely not reflective of what it really does.

Library-itize Flutter Docker Image

While trying to build the Flutter client in Docker, I ran into a few issues with existing solutions. There is no official Flutter Docker image and the existing ones are not well documented, particularly as a Docker newby like myself.

If I get some time, I might make it a little more extensible and publish it to DockerHub so future Flutter projects can take advantage of it.

Split ingress configs across infrastructures

The Nginx ingress Kubernetes config should be slightly different between Minikube and GKE. Now that we have different environments for the two, this should be split with different implementations of the two.