• Graph API

    This is a first explanation of the Graph API that I’ve added to this blog to allow it to be explored within our Liquid Space interface. To try it out, go to http://liquidspace.global/ and use the [G] icon in the tools menu, and enter this “endpoint” https://jrnl.global/wp-json/graph-api/v1/query This lets you explore this blog as a graph. Currently it’s really inefficient in several ways, but the ways to optimise it are obvious, but not worth worrying about until after our Demo in December. It also has a feature that lets you request a list of types from the blog, and retrieve nodes by type. I think I want to get rid…

  • Fish

    This is a fake glossary entry just to be able to illustrate a link in https://jrnl.global/2018/11/30/post-format-for-hyperglossary/

  • Post Format for hyperGlossary

    In order to allow for the desired  interaction there must be a format for the authoring application, whether WordPress web or Liquid Author to send this to the WordPress post for special viewing like this if the template supports it or as a basic use for non-optimised templates. I suggest: some text and then the term which in this case is fish (⋮ a marine animal that swims https://jrnl.global/2018/11/30/fish/ ⋮) with other text to follow to better show context This means that by default a short definition is shown with a link to the full definition but the plugin or theme can parse this (based on ⋮ by the closing and opening bracket) to…

  • HyperGlossary In-Document

    The design of what happens when a document with glossary terms attached is published to WordPress is difficult since there are so many ways it could be handled and there should be degrees of reveal for the reader without the reader being confused: It should be possible to not have any glossary text visible, to have the short definition visible and to access the full definition and then the full graph connected kahuna. Visual tests There should be a way to indicate that certain text has a glossary term available for reading but which is not opened up (in brackets to show the short definition). See are some tests using…

  • Posting Dialogue with In-Situ short definition

    I was reading Tom’s book for the Economist this morning and there was a normal Economist style sentence which defined a term. It was something like this: “Cap-Gemini, a consulting form,” and it seemed such a great display style of the short definition so let’s have the form be like this, with many of the fields having suggestions for content to help the user:   When the user starts writing the Short Definition though, it appears alongside the title, staying horizontally centered,  to help the user write it in a style which would work as an auto-inserted description after a comma: However, the issue comes up that if the term…

  • Updated after Gyuri ( manual typing of types)

    I have updated the dialog and allowed the user to type in a relationship manually:   Changes: Top Priority There is no longer a drop-down for relationships, simply a field for the user to type freeform, with greyed out text to suggest action (‘was invented by, works with etc…’) which disappears immediately on click/tab. There are also fields for websites to be added, which also has a freeform text field for the user to type a relationship. Add the text bottom left as shown, liking to http://www.liquid.info/flow.html Optional (Do if not Very Time-Consuming) The drop-down now covers the strip of Search, References etc (unless too much work) The title, which was…

  • Things to have relationships with in the glossary

    So, we have this now in Liquid | Flow. Select text, keyboard shortcut for the menu and then simply ‘g’ for Add to Glossary. In this case I’ve added Chris: At the bottom we have this pop-up for relationships which is are so far only relationship terms for concepts. But what about for other types of entries, such as people (in the case of Chris), places, documents, things, projects, companies and so on? How should we organise the types? For example, if the entry is about a person, we should have at least these options for defining the relationship with another entry: Works with Works for Works on Created Created…