You’re all doing these amazing things, whether it’s for work, open source, or some personal project, and that’s great and all except for the fact that we can’t see what you are doing!
So what are you working on this week? Maybe are you implementing an exciting feature, fixing mundane bugs (or writing them?), or are you caught in a massive yak shave? Share!
examples with images (evaluated during doc generation)
categorization
auto-generated sections (like list of constants)
math formulas
All based on metadata, codox and markdown.
This is quick and dirty solution based on string manipulation but I think some of the elements could be easily built into codox or cider.
Coding a visualisation for product roadmaps and long-term project planning. I am using ClojureScript and PixiJS (cljsjs/pixi) for that purpose. Goal is to have a highly interactive visualisation where you can move parts of the diagram around. Therefore I decided to go with PixiJS instead of e.g. generating SVG graphics.
So lot’s of macro stuff. ls (deref’d local state) and ls! are both automatically injected. Binding highlighting work in Cursive automatically. :props/will-mount (etc), :key and :init-state all have access to all passed arguments since it’s automatically wrapped in an fn. I get a nice warning when I introduce new map keys into local state (if I accidentally write (ls! update :expadned? not)).
Also playing around with Java Poet since I might write a faster clojure.core/apply with it (basically translating my CLJS apply optimizations to clojure).
I’m working on making a command line time tracker, inspired by ledger-cli. You have to manually add entry to a plain text file about the money you spent/received and then ledger shows you interesting aggregates and balances. It is very useful to track your personal finance.
Similar to ledger, I’m making a utility to track personal time. How much time you sleep everyday, time spend in actual working, routine tasks etc. Currently I got a pomodoro styled timer with OSX desktop notification and logging working.
These logs are compatible with ledger-cli. So you can actually use ledger to see how much time you spent on each task.
Here’e the link: https://github.com/anuragpeshne/ttracker
I am pretty excited about learning Datomic - Spun up a Datomic Cloud solo instance, and have been going through the “Teach yourself Datalog today” tutorials.
I like what you’re doing here! Any thought to making the examples tests? That is, for instance, specifying per-function tests that can take a metadata flag that tells the doc system to export the test as an example? Seems like it might save some work and help make sure that the examples stay in sync with the codebase.
Yes! I have this in mind. Providing expected result enables option to create test as (is (= …)). I’m extracting currently my poc into external library.