TreeSheets : Free Form Data Organizer (see strlen.com/treesheets)
ZLIB License
TreeSheets is a "hierarchical spreadsheet" that is a great replacement for spreadsheets, mind mappers, outliners, PIMs, text editors and small databases.
Suitable for any kind of data organization, such as todo lists, calendars, project management, brainstorming, organizing ideas, planning, requirements gathering, presentation of information, etc.
It's like a spreadsheet, immediately familiar, but much more suitable for complex data because it's hierarchical. It's like a mind mapper, but more organized and compact. It's like an outliner, but in more than one dimension. It's like a text editor, but with structure.
If you like, you are kindly invited to join the Discord channel and the Google group for discussion.
Pre-built binaries are available at the Release section.
Please note that the Linux builds provided are built and only compatible with ubuntu-latest
used by GitHub Actions Runner.
If you use Flatpak, you can install TreeSheets from Flathub.
This repository contains all the files needed to build TreeSheets for various platforms.
TreeSheets has been licensed under the ZLIB license (see ZLIB_LICENSE.txt).
src
contains all source code. The code is dense, terse, and with few comments, typical for a codebase that was never
intended to be used by more than one person (me). On the positive side, you'll find the code very small and simple,
with all functionality easy to find and only in one place (no copy pasting or over-engineering). Enjoy.
TS
is the folder that contains all user-facing files, typically the build process results in an executable to be put
in the root of this folder, and distributing to users is then a matter of giving them this folder.
TODO.txt
is the random notes I kept on ideas of myself and others on what future features could be added.
Note that YOU are responsible to know how to use compilers and C++, the hints below are all the help I will give you:
All Platforms:
git clone --recurse-submodules https://github.com/wxWidgets/wxWidgets.git
.Windows:
wxWidgets
folder sits parallel to the src
folder, that way the TreeSheets project will pick it up without further modificationswxWidgets/build/msw
, open wx_vc17.sln
with Visual Studio 2022._custom_build
) in the solution explorer, and go to properties:
TS_installer.nsi
(requires nsis.sourceforge.net)Linux:
cmake -S . -B _build -DCMAKE_BUILD_TYPE=Release
or similar.
git
installed, the submodules for wxWidgets will be automatically updated and wxWidgets will be compiled as a CMake subproject. TreeSheets will be then statically linked against this wxWidgets build.GIT_WXWIDGETS_SUBMODULES
in the CMake project. In this case:
--enable-unicode
and --disable-shared
to the configure
step./usr/local
) by passing something like -DCMAKE_INSTALL_PREFIX=/usr
.cmake --build _build
.sudo cmake --install _build
.OSX:
mkdir build_osx
cd build_osx
../configure --enable-unicode --disable-shared --disable-sys-libs --without-libtiff --with-osx_cocoa --enable-universal_binary=x86_64,arm64 CXXFLAGS="-stdlib=libc++" LDFLAGS="-stdlib=libc++" OBJCXXFLAGS="-stdlib=libc++" --disable-mediactrl CC=clang CXX=clang++
make -j8
sudo make install
osx/TreeSheets
to build treesheets. put the resultingTS
folder in osx/TreeSheetsBeta
to distribute.I welcome contributions, especially in the form of neatly prepared pull requests. The main thing to keep in mind when contributing is to keep as close as you can to both the format and the spirit of the existing code, even if it goes against the grain of how you program normally. That means not only using the same formatting and naming conventions (which should be easy), but the same non-redundant style of code (no under-engineering, e.g. copy pasting, and no over engineering, e.g. needless abstractions).
Also be economic in terms of features: treesheets tries to accomplish a lot with few features, additional user interface elements (even menu items) have a cost, and features that are only useful for very few people should probably not be in the master branch. Needless to say, performance is important too. When in doubt, ask me :)
Try to keep your pull requests small (don't bundle unrelated changes) and make sure you've done extensive testing before you submit, preferrably on multiple platforms.