In tomorrow’s meeting with Vint, Chris, Gyuri and Shane we will be talking about: Citation copying which are high resolution copies with author information and other meta data by Chris, to be shown on this page. Graphical views of blogs, essential two riffs of what I was working on with Dynamic Views which both Chris and Gyuri have worked on independently and which we will work to integrate. This also touches on the hyperGlossary work and the work the knowledge graph group is working on. Search Own Blog. We will also briefly discuss how themes can help some of the issues of finding ones own work for inclusion in new…
-
-
Thursday 18th of October call
We need to focus more on what we can do with the blue dot menu and what we need to re-code and what effort that will be. I had to leave early which was a shame but Marc-Antoine and Robert joined us. We will also need to design all the functionality we feel should be done: Copy As Citation Shane is using Chris’ code for this. What effort is left? Also, can we simply add to the Copy command so it’s always copied as citation with high resolution addressing?… Dynamic List View Chris would like to build a powerful list view for queries. Frode would like this as well but…
You May Also Like
Meeting with Chris Gutteridge 5th of Sept 2018
Why Blogging Sucks?
Stephanie Couch
-
Blue Dot
We now have a designed blue dot menu here on jrnl.global with a rudimentary Flow function which the guys are going to improve and then put the code into Shane’s repository at https://github.com/swalkergibson/blue-dot
-
9th December, Project Priorities
We have decided that we need to first and foremost implement high resolution addressing into the blue dot menu. We will further work on ViewSpecs and hyperGlossary integration.
-
refined blue dot
We now have this refined blue dot menu, with basic functions only. It’s only live on wordpress.liquid.info so far though.
-
Basic Features, 20 Sep
In order for the jrnl project to reflect Doug Engelbart’s thinking we need to provide high-resolution addressability, ViewSpecs and some level of simple versioning. High resolution addressing will be met to a minimum requirement by having paragraph level addressability and higher resolution if we can incorporate it. High Resolution Addressing Authoring High Resolution Links This means that we will need to provide a means through which we add anchors to the text and we need to decide if it should be by the authoring client or through a server plugin. Using High Resolution Links We further need to make our text selection system ‘see’ the nearest higher anchor and incorporate…
- Blue Dot, Citations, High Resolution Addressability, hyperGlossary, Implicit Linking, Publishing Options, ViewSpecs
Blue Dot Menu Design
Guys, this is what we are doing with testing so that we have an interaction means to test some of the work we are looking into. Please comment. The blue dot, carried over from http://wordpress.liquid.info (originally the Hyperwords dot) is being tested as an interaction means for the jrnl. The menu is being modified to not have the highlighted character, no sub menu, one menu break and no bottom ‘brand’ section. Menu Items The menu items for first testing should be: Search this site Google Wikipedia Images (google images) – break, to be shown as an empty line, maybe later modified in height or with line – Copy As Citation (copies text and…
-
jrnl High Resolution Addressing Implementation
I think the notion of addressing is key for much of the interactions we should build and I have written on it all over the place, particularly on the site http://symbolspace.info where I discuss connections and addressability as aspects of the same thing. For our jrnl project a high priority is to implement stable way where a reader can cite text in a blog post and have a high expectation that when cited in another blog post or other document, when a subsequent reader chooses to access the citation source, that it will automatically be indicated on the article. An important part of this is the use of the high…
-
Component overview
In response to recent email discussion, I would suggest the following as independent components, or wordpress plugins to develop, but in a way which they plan nice with eacth other. Please feel free to comment and/or copy and do your own list for discussion, I am just throwing this out here. There is a lot to do in the future, as listed on the thefutureoftext.org/jrnl-components-to-build.html page but this seems like our start: Timeline View Search Component. Chris adds: ”a way to refer to WP elements in a standardised way and an API to query those with a very light graph querying system that could be replaced later” View Component with…
-
Rich Text Interaction / Blue Dot
An example interaction to provide server-side specified options for text interactions. Options can include in-blog search, user name recognition and links and more. You can try it live at http://wordpress.liquid.info/a-theoretical-model-for-knowledge-work-symbol-manipulation-4-aug/ It looks like this: This is currently implemented at wordpress.liquid.info under the original name of ‘hyperwords’ in 2006: A Level, B Level & C Level of Activity
