Same as pdf below but with three archery targets per every item of the grid. Same link too:
This PDF is more fitting PARA type of use where flat "projects" folder has multiple such PDFs per project for example. For that reason to differentiate PDFs this one has option to configure header for all PDF pages and change visual style (especially relevant to PRO device). The grid can be used for a month-long PDF or other things unrelated to time so it still fits the general theme of unconstrained PDFs that can be used in different ways.
Structure is simple:
- "+" page(s) for whatever conception/abstract/main-page type of content (up to 17 consecutive pages)
- "-" page is a numbered 6x6 grid of for whatever decomposition into items/entries
- entry pages are linked from that 6x6 grid (up to 9 consecutive pages per entry)
Configurables:
- header text
- colors and line thickness
- grid entries can be renamed (numbers by default)
Other:
- everything except the grid "-" page has pagination shown by small progress marker at the top (the point is to never really care about pages within the item, otherwise I may just add more pages per item)
- the making PDF web page works offline (hopefully)
NOTE: Content below is from previous iterations so it may need an update
PDFs for RM with experimental features.
Also, PDFs I don't use get removed from the list but stay in older releases downloads.
Experimental hexagons background PDF, full description is on the last page of it or in the corresponding .rb file here around.
Experimental colored PDF, full description is on the last page of it or in the corresponding .rb file here around.
Random abstract PDF. The main page may be the most interesting by itself. Also there are big hexagons on all pages except main as part of the grid for potential interesting uses. Otherwise it simple set of 32 5-item lists with 17 consecutive pages per item.
- main page has a hexagon grid of roundish links, so it can have experimental uses like mind mapping
- inside such links there is a single page of content space and a list of five items with links per item to go down further
- every such item has 17 consecutive pages with pagination marker on top
- turning pages outside those paginated items just moves between those list pages
- link for going back/up is in the top right corner
- must do with such PDFs is to mark or name links before entering them and then to write the same name into the page header after entered the link
Catchall is not part of the PDF, I assume it should be just flat.
This info is also on the last page of the PDF.
Flexible quarter calendar PDF with write-friendly minimalistic UI.
Main pages: Quarter > Month > Week > Day > Hour
Main experimental feature is having extra page per any calendar page - it can be used for plan/review for example. Since those extra/review pages have own parallel navigation between them, they can be seen as parallel second calendar with bigger single area for writing. Second experimental feature is the presence of own hour pages (covering 12 hours per day).
Must know is the use of hidden links, there are two types:
- moving up/back in main calendar is done by the wide link area in the upper-right corner (also exits extra page into corresponding calendar page)
- entering extra page is done by the square link in the bottom-left corner (this corner toggles between extra and main page)
Also on month overview page the last square/day of each column/week will open the week overview.
Also there is best practice to mark used links before entering them.
Also turning pages opens the next month/week/day/hour. From turning pages perspective start of the day is assumed at 7, and end at 6, so if you open 6 and turn to the next page, it gives 7 of the next day (header shows that).
Day pages have predefined background with clock face for hours blocks and the central square can be used as:
- Focus of the day
- Eisenhower matrix in four parts
- Sketch built over the day
- Mix of these
Flat habit grids are not part of the PDF but there is plenty of more hierarchical plan/review type of space.
This info is also on the last page of the PDF.
- Disclaimer^2: since move from Ruby to Rust, code style may be in the odd space and lots of things in the README may be obsolete.
- Disclaimer: creative chaos codebase that serves it's purpose well lies ahead.
Big picture:
- the pdf is defined by a tree structure starting from root page and going down by child page branches that link back to the parent page
- every child page is defined by link position within the parent page
- there are sequential collections of pages that share the parent and only the first page of them is linked from the parent, this adds volume to be used so you don't cram things onto one page but the tradeoff is you loose turning to the next-page also opening the sibling page (from parent perspective) interaction
Order of things in code:
- generally generation ruby file has pdf description text very early in the file
- then data for rendering may be generated beforehand if it is needed that way
- then in separate chunks of code different types of pages are generated (this also makes them appear consequently)
- (then optionally some advanced rendering depending on all pages being in place is done)
- also ui helpers may go to the end of file
- download and extract needed fonts as expected by
bs/fonts.rb.ls fonts => Aoboshi_One/ Noto_Sans_Symbols/ Roboto/ - have ruby installed and run
bundlein the root of the project - run
rake, checkoutput/dir - for development some files generate PDFs by just running
ruby <FileName>.rb
- org-mode early inspiration but that is too open ended by itself so no
- it started as simplistic setup that allows generation of any interactive pdfs to be filled by the user
- then enough patterns crystallized so it became more incremental and modular technically
- then actual PDFs got to be stupid-simple with least complexity introduced by them (PDFs went from being abstract and experimental to asbstract and simplistic. Sadly names got simpler too and there are no more names like "Square BS PDF".)
- (there was funny side effect of the project is having dreams about linked pdf grids)
- then I tried to optimize PDFs for use approaches (Bujo/PARA)
- also Days PDF got clockface and focus area
- merged other simplistic PDFs back into abstract PDF for lists (that can fit Bujo/PARA by itself); it is not abstract in style as early PDFs but there are no arbitrary decisions so it is true to the idea still.
- went back for asbstract for lists, went for plan/review at all scales in calendar (previously Sunday weeks version had that aspect)
- went for more geometry with hexagons
- unification about stuff (areas: There.at + there was some grid stuff), lots of code to remove too
- fuck their coordinates, use top-left as 0,0; also have selection being about centers of cells, corners only play on use; no widths/heights interface, use natural directions
- RM PRO renders those grays?
- split each pdf generation between files Q/{data,ui,all}
- went from Ruby to Rust + WASM to configure PDFs because going more PARA way - folder of PDFs per anything, so pre-generated header on all pages makes sense now