Archive of Completed Activities

  • 2019-06-09T10:51:00Z: Autocopy for the “Text Position Retriever 1” *
  • 2019-05-25T10:42:00Z: Expand the “Change Tracking Text Editor 1” into a full, standalone text editor *
    • Let the user decide if a new text should be created or an existing one opened
    • Call file_picker_1 for input file and output directory selection
    • For existing files, create a backup and if a text history file, reconstruct the latest version
    • Call change_tracking_text_editor_1
    • 2019-05-14T21:10:00Z: Create and call change_history_concatenator_1
    • 2019-05-18T00:11:00Z: Generate output files (concatenated, optimized + visualizations)
    • 2019-05-20T23:23:00Z: Generate visualization of the unconcatenated, unoptimized output
    • 2019-05-24T22:02:00Z: Check localization strings and code checkin
    • 2019-06-08T22:42:00Z: Testing
    • 2019-05-25T10:42:00Z: Package and publish the new release
    • Fix bug of additional whitespace in output *

Activity Description

Click an activity item marked with an asterisk (*) at its end to view its description.

Descriptions

Allow to automatically copy the current span selection to the clipboard on completion as an option.

A csv2xml converter does already exist in the automated_digital_publishing package, but it’s buggy. Therefore, I probably should write my own with proper parsing techniques based on an implicit call tree instead of trying to fix the current implementation with its state machine strategy. I started an attempt some time ago, but failed, potentially by not recognizing the linebreak as the element of highest priority or some other reason. Unfortunately, I can’t find that code any more and likely have to start anew from scratch again.

70 pages.

140 pages.

209 pages.

279 pages.

348 pages.

Recently, completed top-level activities were removed from the main output file (in order to keep focus on actual activities, not loads of historical entries). Still, there needs to be a way to conveniently view the completed activities separately.

Visual rendering of “waiting”/“paused”/“blocked” (red), “abandoned” (red, crossed out), “rejected”/“cancelled” (black, crossed out) would be nice.

I did a Hyperglossary prototype (code, live) for Doug@50 (50th anniversary of Douglas Engelbart’s Great 1968 Demo, but that’s trapped in the browser (Same-Origin-Policy restricts it to a server) and limited to WordPress as a source, therefore a more generalized Hyperglossary capability is needed, preferably as a standalone program, that can apply any glossary in a compatible format onto any target text that’s in a compatible format.

This would allow to use the same input file for both, the glossary input and the base text input, without duplicating the glossary data, therefore enabling the hyperglossarization of existing XHTML webpages that come with an unaugmented glossary.

The last release of the “Change Tracking Text Editor 1” in a practical scenario requires the user to manually copy files around, so a new version should introduce dialogs to select input sources and output targets

When opening a plain text file that ends with a linebreak and immediately leaving/saving, the import adds additional whitespace to the add instruction.

30 entries.

60 entries.

90 entries.

120 entries.

151 entries.

This is a discussion of the quote “the conversation is the work” by David Whyte, often cited by/in conversation communities for a description of what they do.

Only reading it because Gyuri Lajos said that it is important for understanding his approach. As suspected, the book hardly contains anything I didn’t already personally know myself before reading it.

82 pages.

163 pages.

245 pages.

326 pages.

407 pages.

This is a one-time manual process as I’m too lazy to adjust the wordpress_retriever_1 workflow a little to incorporate the publication date in the file name and import the text to a revision history.