Ever heard of [[networked thought]] or [[zettlekasten]]? Super fascinating and effective ways to keep track of your brilliant ideas! :) Check out our awesome tool for organizing and easily referencing all your most useful thinker thunks. The ones that flutter by, escaping our brain right when we most need them. Locally hosted, open source desktop app built in .cljs, reagent, reframe and datascript. The Gates of Athens are open! Free desktop available to everyone, with additional tiers through OpenCollective. Try the web demo (no changes saved) at https://athensresearch.github.io/athens Desktop download links: - Mac: https://tinyurl.com/athens-mac - Windows: https://tinyurl.com/athens-windows - Linux: https://tinyurl.com/athens-linux
Does Athens support exports?
there is also https://twitter.com/codexeditor
re Athens exports: you can have a db backup, so I guess that counts as export
I think athenresearch is pretty nice and lovely! A good showcase for another thing possible with clojurescript! well done @lorilynjmiller!
Where do I find some intro docs for Athenresearch? E.g. to learn what ((block references))
is? Is there any support for formatting (e.g. markdown)? thanks!
Ok, found the Welcome page in the app π
Athens was recently accepted into Y-Combinator too. It'll be neat to see how they approach open source with commercial success which is a big topic in the zeitgeist
support a subset of markdown right now @holyjak. it's likely we go for full markdown but also many users are non-developers, in which case a WYSIWYG would make more sense for them
One thing I did not get - can I post links to external content, as I would in .md do with [my title](<https://some.place/123>)
?
yes
I had made a visual to help explain zettelkastens more https://clojurians.slack.com/files/U8WFYMFRU/F01N8D0SX5F/zettelkasten.pdf (still a rough draft) and thereβs some other discussion about it in https://clojurians.slack.com/archives/C03RZGPG3/p1613078474271900.
@steve.lombardi I use Notion for my zk but org-roam is another great option for emacs using org-mode.
This is the open source "competitor" to Roam?
One way to put it @seancorfield
I'm curious what warrants the scare quotes.
Because I don't know enough about either project to know whether they are truly competitors or not.
Besides Roam and Athens, are there any other similar solutions out there?
Reading up on this stuff, I'm reminded of Notion. https://www.notion.so/product
Not quite the same problem space but there's definitely overlap.
A few other notables for discussion: β’ https://www.remnote.io/ β’ https://logseq.com/ β’ https://obsidian.md/ β’ https://github.com/foambubble/foam β’ https://dendron.so/
You can also zettelkasen with org-mode https://blog.jethro.dev/posts/zettelkasten_with_org/
Crux 1.15.0 is outΒ πΒ π β’ We've made the Java API for submitting transactions much more IDE-friendly - Java users can now construct transactions programmatically through the new Transaction APIs. β’ Another oft-requested feature: queries can now return maps, using theΒ `:keys`/`:syms`/`:strs`Β syntax β’ Bugfixes - and more details atΒ https://github.com/juxt/crux/releases/tag/21.02-1.15.0 ThanksΒ π Have a scout of the #crux channel for more on this release.
Just create a very simple ECharts lib, welcome to have a try: https://github.com/kimim/re-echarts
deps-infer: Infer mvn deps from sources. https://github.com/borkdude/deps-infer Thanks @hiredman for the idea. For now this is just a POC but I thought it would be cool to share in case anyone wants to contribute.
I'm curious - what might be some of the use cases? I can only think of somehow losing deps.edn
.
@p-himik For babashka scripts this could be useful if you want to port your script to the JVM and you want to compile it with GraalVM for example
Ah, nice, thanks!
This can also be useful when you want to compare the newest deps in your .m2 with the ones you already have. Or when you want to migrate your git libs to mvn ones :)
I imagine it could also be useful if you use clojure.tools.deps.alpha.repl/add-libs
to hot-load dependencies and you want to save your state into a deps.edn
file.
This can also be a useful addition to clojure-lsp. Type (:require [clojure.tools.cli])
and it will be interactively added to deps.edn. cc @ericdallo
Looks valid, not sure what's version would add in deps.edn though
[re-frame "1.2.0"]
a framework for building user interfaces, leveraging React.
Headline: Upgrade to reagent 1.0.0 and React 17.
http://day8.github.io/re-frame/releases/2021/
[re-frame-10x "1.0.0"]
A debugging dashboard for re-frame. X-ray vision as tooling.
Headline: Upgrade to reagent 1.0.0 and React 17.
https://github.com/day8/re-frame-10x
oh got it, that's deps-infer responsibility, really nice
re-frame-template 1.4.0
A lein template for re-frame aka lein new re-frame <app-name>
Headline:
β’ Upgrade to reagent 1.0.0 and React 17
β’ Upgrade to re-frame 1.2.0
β’ Upgrade to re-frame-10x 1.0.0
β’ Upgrade to re-com 2.13.2, and add example of new re-com debugging features.
https://github.com/day8/re-frame-template
I found another nice use case: you want to port a lein project to deps.edn (but don't want to rewrite the project.clj yourself)
or a boot build.boot file (which is arguably harder because of code instead of config)
oh, that I could use on clojure-lsp itself π
Extra use case (and long wanted one!): making implicit dependencies explicit
e.g. maybe I'm actively using math.combinatorics
in my project, but it's in my classpath because it's a transitive dep of some other dep.
Another use case: see which deps you are actually NOT using in your original deps.edn
Although this can give false positives when you wanted to pin a particular transitive dependency to a particular version or include some plugin that some other dependency (or your code) uses dynamically.
if you wanted to pin that version, why not include it explicitly with that version?
yeah, false positives can happen, this is probably why you should manually review the output
> if you wanted to pin that version, why not include it explicitly with that version? That's what I meant. Your project is using lib A@1.0.0 which uses B@1.0.0 You know that B@1.0.0 has a bug that's been fixed in B@1.0.1 that's backwards compatible with B@1.0.0. Naturally, you include the B@1.0.1 in your deps even though your project never uses it directly. Perhaps, deps-infer deals with that already by analyzing not only your code but also the code/dependencies of your dependencies. It's not obvious to me given the README.
@p-himik I see, yeah, in that case I think you should put a big fat comment in your deps.edn saying why you included that dep
You can --analyze
all of your own code + dependencies, but then you will get a list of suggestions for all transitive deps as well
The use case I have is, I know the api for a number of libraries well, so I can sit down and write a clojure program that uses them, and then suddenly I have make a deps.edn to run it, and I have to Google around to find maven coordinates.
Which is really dumb since the information is actually all already on my local ssd
my local m2 is over 2.5 gigs and I must have been copying it forward across 2-3 laptops because it contains artifacts like the fork of clojure we used at work briefly 8 years ago
Oh god, you made me recall how we had ~45GB .m2
dir for a legacy project. And that's on a fresh install. What a nightmare it was to work with.
yeah, so so much of the information about libraries is already there
@hiredman you would just type it without a REPL connection?
yes
I think in theory I could do that but without the REPL I just feel naked in a thorny forest
Pathom Viz 2021.02.24
is out! https://github.com/wilkerlucio/pathom-viz/releases/tag/v2021.2.24
On this release:
- Improved auto-complete
- Set larger minimum side for panels in general, this will avoid sections getting completly collapsed
- Incorporate Tailwind CSS as part of internal designs, this already affects some of the UI and is the initial foundation for more UI standardization for Pathom Viz