Skip to content

Releases: leifeld/texreg

texreg 1.39.4

24 Jul 12:23
Compare
Choose a tag to compare

texreg version 1.39.4, released on CRAN on 24 July 2024. This version has support for remstimate and some other models and fixes a few bugs.

texreg 1.37.5

18 Jun 19:08
Compare
Choose a tag to compare

This is the first stable CRAN release since 2017 and the product of a major package overhaul with the following changes:

  1. A new praise function for submitting praise and feedback about the package to https://www.philipleifeld.com/praise, where it is visible to everyone, including a world map. This is part of our efforts to document the impact of the package, which is instrumental in maintaining funding and institutional support. So please consider using the praise function widely to tell us how the package is helping you, what organization you are working for etc. Particularly non-academic impact matters for funders these days, so if you work in a non-university context, please show your appreciation with this function.
  2. The htmlreg function was updated from HTML4 to HTML5.
  3. A new knitreg function, which automatically selects the right function depending on the output format of the document.
  4. A new matrixreg function, which does the heavy lifting in the background and can also be called by the end user to produce a character matrix of the table contents.
  5. A new huxtablereg function for creating tables for the huxtable package.
  6. A new wordreg function for creating basic MS Word documents.
  7. Updated the plotreg function to ggplot2 and added support for multiple models.
  8. Lots of new model extensions and updated extract methods.
  9. New arguments:
    • tabular (for switching off the tabular environment so users can use texreg with tabularx, tabular* etc.)
    • custom.header (for grouping multiple models under a common heading)
    • siunitx (an alternative to dcolumn for decimal point alignment)
    • threeparttable (for long custom notes under the table)
    • additional arguments in htmlreg to customize the HTML output.
  10. Unit tests using testthat to ensure the package is more robust to the introduction of bugs.
  11. More robust documentation using roxygen2.