Video: https://youtu.be/YVGidL1B8cM
Chat log: https://futuretextlab.info/2023/12/18/chat-18-december-2023/
Quick recap
The team discussed their upcoming meeting plans, sharing experiences on managing programmers and budgets. They agreed to split the meeting into general dialogue and project management discussions, with the first half being general and the latter half dedicated to project management. They also considered having a separate day for more project management discussions. Frode emphasized the importance of finalizing a suitable format for their project book and the challenges of incorporating PDFs into XR. They also discussed the technical aspects of integrating external content, particularly YouTube videos, into a document. The team also discussed the development of a software reader that could interact with Adams’ test environment.
SummaryPlanning, Screens, and Project Management
Frode and Rob discussed their upcoming meeting plans, with Frode planning to stay for three days and Rob emphasizing there was no fixed duration. They shared experiences on managing programmers and budgets, with Rob planning to visit Southampton in May and Frode agreeing to consider a meeting there. Dene brought up an article on the challenges of reading on screens and their comments. The team agreed to split the meeting into general dialogue and project management discussions, with the first half being general and the latter half dedicated to project management. They also considered having a separate day for more project management discussions. Dene emphasized the need to balance theory-based discussions with practical project work, and the team discussed the need for flexibility in attendance based on individual schedules and commitments.
Data Synchronization Strategy Development
The team discussed the development of a data synchronization strategy for a computer to a headset. Frode suggested using HTML as a data store initially, with an option to convert to PDF later, and emphasized the need for offline functionality. Fabien presented a prototype that demonstrates the minimum required functionality and proposed using a URL to access data. They also emphasized the importance of user privacy and suggested using Glitch. The team decided to prioritize project management in the first hour of their meeting and allocated additional time for theoretical discussions. Alan suggested a collaborative approach to understanding the project and emphasized the importance of identifying key areas of interest and potential challenges. The discussion concluded without a clear resolution on the matter.
Interaction, Restructuring, and Project Management
Alan highlighted the importance of immediate interaction, article restructuring, and the ability to access and add material to a library. They also stressed the need for Xr to store user’s last state from the previous session and the potential for Xr to be used even when offline. Dene proposed documenting progress as stories, setting priorities, and setting stretch goals. The team discussed the importance of timely delivery for the grant and the potential for adding to it once ahead of schedule. They also discussed project management tools, storage of project details, and the possibility of a registered domain name for the project. Frode raised concerns about using proprietary systems and emphasized the importance of commitment.
Format, Blog, and User Story System
Frode discussed the importance of finalizing a suitable format for their project book and the challenges of incorporating PDFs into XR. They proposed starting a blog using RSS feeds and HTML for threading, emphasizing the benefits of an accessible and open format. Frode also suggested a new system for storing and sharing user stories and feature sets separate from Google Docs or Slack. The team agreed to reach a consensus on the final decision, discussing the potential use of HTML and XR in their projects. The conversation concluded without a final decision on the format.
Data Management and User Interface Evolution
Bob introduced the concept of “Gigum Mapping” developed by the University of Oslo architecture school, suggesting it could be a model for managing important data. Alan shared another beneficial system design, an interactive “tear down explosion diagram” of large language models. The team discussed challenges in transferring information from the chat and the importance of allowing users to have their own academic library. Frode emphasized the need for a structured approach to discussions and agreed on the next steps, including transferring documents and updating user’s library after interactions. The team also discussed the possibility of annotation and sharing capabilities. Brandel discussed the evolution of web-based interface and the challenges of XR, suggesting that some information, such as the exact vantage point of a user’s head, could be encoded and sent back to the server. The team also discussed separating different aspects of their software project and the need for a system to decide what is relevant to include in the library.
Semantics and User Interface Design Discussion
Brandel emphasized the difficulty of distinguishing between significant and insignificant actions in the context of document manipulation, highlighting the importance of understanding semantic actions in user interfaces. Frode proposed allowing users to define their own prompts for documents, while Alan raised a discussion on the assumptions about what a user would find valuable in their product. The team also discussed the role of semantics in relation to documents or the environment and the importance of maintaining an open and positive atmosphere. Brandel suggested being conservative with the scope of the goal to ensure its successful execution.
PDFs in Academic Writing: Pros, Cons, and XR Experiments
Brandel, Frode, Alan, Mark, and Fabien discussed the pros and cons of using PDFs in academic writing. The team acknowledged the limitations of PDFs in terms of quality and semantic information, and the differences in desktop and XR renderings. There was a discussion about the inflection point between viewing documents in a 3D space versus tailoring documents for the experience. Fabien suggested managing a collection of documents with minimal annotation, while Alan proposed focusing on specific pieces of text and their connections to other documents. The team agreed to experiment with a few documents made specifically for XR and to consider ways to connect and display them in a useful way. Dene suggested putting the lab on hiatus for the holidays, with the next meeting scheduled for Tuesday of the following week.
Interactive Reading and Digital Adaptation
Adam discussed the concept of active reading, suggesting ways to make reading more interactive such as pulling quotes out of documents and adding comments. Frode emphasized the importance of experimenting with these ideas, highlighting potential opportunities. Peter proposed the concept of fine-grained control of the Z-plane of text in a PDF, suggesting it could serve as an ambient display based on external data feed. Alan brought up the changing nature of writing and reading in the digital age, emphasizing the need to adapt to new reading habits. Bob discussed the process of extracting and refining information from documents, referring to it as ‘information chunking’. They also touched on the transition from print to digital forms, the potential of using text and annotation, and the need to understand and preserve certain affordances of print. Frode emphasized the importance of addressability in enabling interaction and usability. They concluded the discussion by sharing anecdotes about the importance of visual aids in presentations and the potential of documents in XR environments.
Integrating YouTube Videos Into Documents
The team discussed the technical aspects of integrating external content, particularly YouTube videos, into a document. Frode proposed a method to extract videos from a document link. The team also explored ways to transfer metadata from a computer to a headset, with Adam suggesting the use of a software to extract information from documents and stream them over a websocket to the headset. They also discussed the potential of using websockets in software development and the implications of different platforms, such as iPads not allowing the shipment of their own browser. Brandel and Frode discussed the possibility of running a web-based or native system on different platforms, depending on the scope of ability and obligation. They also touched on the technological implications of different platforms and the potential of taking the connection stream local.
Software Reader Development and Process Revision
The team discussed the development of a software reader that could interact with Adams’ test environment. Frode proposed a collaborative approach, with the team agreeing to define a few core elements and keep the system flexible for future changes. Brandel suggested a simple solution of allowing the author to directly output socket data, which could then be connected to the VR web page. There were concerns raised by Frode about potential issues, but the team agreed on the simplicity of the proposed solution. Frode proposed a plan for the team to get together and define a new process, with the possibility of testing it out. The team also discussed the structure and exchange of data within their system, with Frode and Adam suggesting sending PDFs through a new data pipeline. The team agreed to document the different approaches being proposed. Towards the end of the meeting, Frode suggested a half-hour or hour-long meeting before their next Tuesday to further discuss the changes.
Websocket Infrastructure and Virtual World Expansion
Adam and Frode considered expanding the capabilities of their web projects through socket and simple web server use, highlighting the potential for peer-to-peer connections and further growth. They also explored the possibility of using devices like laptops and phones to create a virtual world. Brandel confirmed the potential of the Visionpro to run multiple software simultaneously. The conversation touched on the use of WebXR, the WebKit browser engine, and a simulator for checking web, Rtc functionality. No firm decisions or action items were identified. Frode announced a plan to visit Rob in California and set a deadline for basic web test functionality by then. Brandel proposed an experienced programmer could get the websocket infrastructure up and running in a few hours. They decided to meet the following Tuesday to discuss system movement. Frode requested assistance for their inexperienced programmer regarding Mac-specific tasks, which Adam and Brandel admitted they lacked experience in.