Open kdpsingh opened 1 year ago
The AOG/CairoMakie deps will be a very appreciable increase in TTFX. I think it makes sense to follow the metapackage format. A separate org would be useful for organization and democratization, which would have a lot of value to the growing number of contributors.
I like the idea of Tidier.jl reexporting TidyData.jl and TidyPlots.jl (and whatever else). Notably, it makes more sense to me, linguistically, for the sub-packages to be Tidy_.jl and not Tidier.jl. My rationale is that tidydata and tidyplots would make your workflow tidier. And yes, I'd offer to make the logos for those ☺️
Thanks @pdimens. My rationale for TidierData instead of TidyData was that if we set up a Tidier org, then it makes more sense to me for the connected packages to have a Tidier prefix.
I was curious to see how Julia 1.9 will impact TTFX for plotting. I know including plotting packages will increase install time by quite a bit, but I'm hopeful that TTFX may be okay with Julia 1.9 since I think Makie uses SnoopPrecompile.
And yes, absolutely would love your magic touch on logos 🤩!
As a side note, the name "Tidier" is already taken as a GitHub organization. Considering "TidierOrg" as an alternative or "TidierJulia". Or may reach out to the current "Tidier" org to see if they are willing to give up the name.
Just a note - Usually Julia orgs on github have Julia as the prefix. Not that you have to do that too, but JuliaTidier sounds better to my ear than TidierJulia.
Thanks @ViralBShah. Appreciate the note! I was only thinking TidierJulia bc "tidier" is an adjective (as compared to JuliaData or JuliaPlots).
Am leaning towards just Tidier (if I can get permission from existing owner) or TidierOrg (similar to MakieOrg).
If this repo is transferred to an org, is there anything special I need to do when I register it?
No urgency and happy to cross that bridge when we get there.
Github will forward the old URL - but we should change the URL in the General registry after the transition.
@kdpsingh I should have time this week to draft up some icons for the new packages (Dates, Cats, Strings). The big question is, would you like the background color of the icons to follow the same blue, or are you interested in different colors?
Thanks @pdimens! My thinking was that since TidierPlots already has the same shade of blue, we should just keep the same blue for all the logos so that they are instantly recognizable as being part of Tidier. I'm open to different colors as well. What do you think?
Also, 2 other things would be really helpful if you have the bandwidth.
Can we create a new TidierData.jl logo that is identical to the current Tidier.jl logo except with the text reading as TidierData.jl?
Since Tidier.jl will be transformed into a meta-package that will include plotting, we can add scatterplot points to the Tidier.jl logo so that it combines data analysis and plotting? (Kind of like the TidierOrg logo)
Appreciate your creativity and time, and totally open to your ideas!
Feel free to make it colorful if you'd like! As long as the main Tidier.jl one stays as the same blue.
It may be cool if we end up making stickers to have different-colored ones. Totally up to you!
Some drafts I slapped together today
Love it! Only suggestion would be to make the background colors more different from one another so that it produces a more rainbow-like effect. Right now the pink and purple are kind of close to one another, as are the two greenish ones.
Also tagging @drizk1 to take a look.
@pdimens these logos look great thank you! I do agree with Karandeep that a little more contrast (perhaps shifting to a navy for one ?) between them might be nice to help them really pop when they're in print one day. Thanks for the great work tho!
Also, last thought: feel free to change the color on the TidierPlots logo too. The only one that should remain the same color is Tidier.jl. Thank you so, so much! So excited.
How about these:
Looks great to me! Only thing I'd consider is making TidierPlots background darker so that the white lettering is more readable. The grey background is actually kind of funny since it's the default background theme in ggplot.
@drizk1 and @rdboyes what do you think? If everyone agrees, feel free to tweak and share files with me or add to PRs.
Looking at it again, I can definitely read TidierPlots so free to leave as-is or just darken the outer portion slightly. I trust your judgment!
The grey background was a whimsical nod to ggplots default theme, yeah. Haha. I'll make it a bit darker
These look great! The softness of the colors is really nice.
Here are 3 variants. My favorite is number 2
I like number 1, but they all look good!
I like number 3 but I'm also good with number 2. @rdboyes, thoughts?
Lol fight amongst yourselves.
This package is @rdboyes's baby so I would go with number 1.
aiight. PRs incoming
Yay, awesome. Question: Can we also update the Tidier.jl logo to include plotted dots (to indicate that it’s a meta-package that will enable data analysis and plotting?) It’s essentially going to re-export all of the other Tidier* packages.
@kdpsingh like dis?
Purrrrerfect (as the TidierCats would say). Let's do it!
Not part of the tidyverse, but the '"rio" package from R is quite nice. Does Julia have something like that? if not, do you guys think an implementation would be good?
It does!
FileIO already handles multiple different formats with a single function for reading and another for writing.
Here are all the supported formats: https://juliaio.github.io/FileIO.jl/stable/registry/#Registry-table
Hi!
I am building with some tables in Julia and was thinking about you all... Is a TidierTables.jl
part of the roadmap? Was thinking along the lines of of the gt package in R.
There's a package PrettyTables.jl that is currently undergoing a remake inspired by the {gt} R package: https://discourse.julialang.org/t/current-state-and-the-future-of-prettytables-jl/118455
I would check in on that package.
I thought it would be useful to have a pinned issue that summarizes which function/macros we are working on building out, and which tidyverse (or related) package they comes from. This doesn’t represent the entire set of functions we need to capture but is intended to give a sense of direction for this project.
Note one key difference in function names below between Tidier.jl and tidyverse: Tidier.jl functions relating to data types are named after the Julia types and not after R types. This is because the data types aren't consistent across languages, and Julia allows for more granularity than R. For example, we plan to use
as_string()
in Tidier.jl rather thanas_character()
because strings are collections of characters in Julia.dplyr
@glimpse
- @zhezhaozz@relocate
- @zhezhaozz@drop_na
- @kdpsinghlead
andlag
- @kdpsinghas_integer
,as_float
, andas_string
is_integer
,is_float
, andis_string
tidylog
forcats
We are using the categorical type from CategoricalArrays.jl, so functions will be prefixed with
cat_*
instead offct_*
.categorical
andas_categorical
cat_rev
cat_reorder
cat_infreq
cat_relevel
cat_lump
ggplot2
lubridate
mdy
,dmy
, andymd
functions, along with counterparts that support*_hms
.Developer resources
Strategic decisions to revisit