Been thinking of getting a Remarkable / Onyx Boox ...
# thinking-together
h
Been thinking of getting a Remarkable / Onyx Boox / general note-taking/drawing tablet, intended as a serious replacement for my mechanical-pencil-and-paper-notebook setup. I'm using it as an opportunity to think about these devices as thinking/coding tools.
c
Remarkable 2 has replaced notepads for me. I love it and I would recommend it but I believe they recently went to some kind of subscription model. I was grandfathered in without paying because I was an early pre-order. I think they are all pretty similar. They all use the same e-ink screen.
k
I have an Onyx Boox Note 2. No longer available but the successors are overall similar. For me it's mostly a reading device which I appreciate enormously because of reduced eye strain compared to standard tablets. I use the stylus mainly for annotating stuff I read, not so much for note taking. It may be very good for that, but I didn't try. Habits...
o
I got for my self Samsung Tab S6 Lite, comes with stylus, still not using it properly as a thinking tool though
n
I've been (slowly) trying to implement a Smalltalk-78 interpreter (enough to run one of the images on the Smalltalk-zoo - https://smalltalkzoo.thechm.org/HOPL-St78.html) for my PineNote, and then I plan to redesign the core UI to work with pen input. It feels like an almost bare-metal Smalltalk (I am just leveraging a minimal linux system to handle the screenbuffer and the basic hardware) will give me a 'small-enough' system to be able to experiment with new 'digital-paper' like interactions
ā¤ļø 1
It feels like a lot of the ideas from Alex Obenauer's Lab notes (https://alexanderobenauer.com/labnotes/000/) provide a design space for building this kind of full-object based personal system
šŸ‘ 1
I love the thinking behind Ink&Switch's crosscut system, but it feels hampered by the fact that experimenting with any new ideas needs the full edit/compile/upload cycle, instead of being able to make changes directly to the system live. One comment from Dan Ingalls that has stuck with me is that while the PARC systems that Alan Kay's LRG group built were slower than software from other groups (like the Bravo editor, which was written directly in BCPL), their turnaround time for experimentation was so quick that it more than made up for the slower system speed. Now with computers as powerful as they are now (even the PineNote boasts a 64 bit 1.8 Ghz quad core chip with 4Gb of memory and a GPU), there is no excuse not to have live editable systems directly on the devices we use.
āž• 1
šŸ’Æ 1
k
The risk of using a live programming system is that once you are used to one, you just don't want to get back to edit-compile-run cycles.
🤣 1
And yes, I'd love to have Smalltalk-on-e-ink with a good touch interface!
šŸ˜Ž 1
b
i work on software for the remarkable tablet, mostly focused on using handwriting as a ui element or input. so far i've released https://github.com/bkirwi/folly, but also have a text editor and other things in various stages of completion
folly is a text adventure / interactive fiction interpreter, so not exactly FoC's bread and butter, but i started it as a way to experiment with some adjacent ideas like the read-eval-print loop, and using handwriting both as a visual element and as a command for the machine.
šŸ‘ 1
personally i find i think differently with a pen+paper metaphor than on a laptop / similar, and i'm curious about better ways to leverage that - most existing software for these tablets uses either a paper metaphor (with no interactivity aside from drawing lines etc.) or a mobile-device metaphor (very interactive, but doesn't take advantage of the text/ink-heavy visuals the hardware is good at)
@Naveen Michaud-Agrawal - i'd be curious how your system differs from existing smalltalk implementations / why one might need a new interpreter for e-ink stuff and not just a new ui
i've thought a bit about the interface side of programming on e-ink (eg. where the syntax doesn't need to be ASCII, but does need to be maximally visually distinct for the handwriting recognizer) but almost not at all about the implementation
n
@Ben Kirwin Folly looks interesting, thanks. The pinenote doesn't quite yet have the level of support for 3rd party applications yet, so i've been prototyping using an interpreter on my desktop.
My approach is less about needing a new interpreter, but more that the Smalltalk-76/78 system feels small enough to be fully approachable (compared to Squeak/Pharo/GT). In addition, those systems all start with a UX system built around keyboard and mouse, and I'd like to explore UI ideas where the pen input is first class
Although I do vacillate between using my own interpreter and trying to get smalltalk-vm running on the quartz64 chip
c
@Ben Kirwin That looks great! Gonna try it out this weekend
šŸ†’ 1
k
@Naveen Michaud-Agrawal You might also check out Cuis Smalltalk, which is more modern that 76/78, but has the explicit goal of remaining small and understandable. https://www.cuis-smalltalk.org/
n
@Konrad Hinsen thanks, I forgot about Cuis. Although I'm looking for non-modern, the current smalltalk vms feel like they are way beyond my comprehension
b
that makes sense! i've never really spent much time with smalltalk; i forget sometimes how deeply intertwined the language and ui are.
k
From the user's point of view, they are, but fundamentally, they are not. You could create a Smalltalk with no UI other than an input text stream. In fact, GNU Smalltalk is almost at that level. Given such a Smalltalk, you could then build different UIs on top of it. It's not fundamentally different from other dynamic languages. The real difference is that the Smalltalk community has since the beginning valued good UIs and development tools.
šŸ‘ 1
b
oh, also related to taking advantage of the medium, if anyone hasn't seen: https://omar.website/posts/against-recognition/ (i don't 100% agree with it, but found it thought-provoking)
n
@Ben Kirwin yes it's a good read. What parts don't you agree with?
b
mostly: i like recognition! it's why i'm using a computer instead of paper. i really agree with a lot of the specific criticisms of the tablet ui, and how it goes too far to make the input legible to the computer at the expense of expressivity etc. but there are other places where i wish the ui did a little bit more recognition... for example, searching for a particular phrase in my notes and i think you really do end up wanting to use the whole spectrum of legible-to-human/legible-to-machine for different tasks / in different contexts
n
Ah agreed
Have you ever seen the Grail demo from Rand Corp? Even the UI was constructed by hand (as a flowchart) -

https://youtu.be/2Cq8S3jzJiQā–¾

I do like Omar's point that the recognition shouldn't erase the original input, instead just annotating with the computer readable information
šŸ’Æ 1
b
i've seen a little bit about the rand tablet, but not a proper demo - thanks for the link!
and yeah, that was definitely an inspiration for how folly does it though really it could take it much farther - eg. letting users take notes and things in the margins, or allow editing old commands in the next version maybe!
c
I actually just tried Folly now so here's some snap reactions; • The general write input, get more text interaction loop is really compelling, it really made the reMarkable feel like a different device. • My handwriting is quite bad and it struggled to understand (3 attempts at "novice mode off"). It would have been helpful to see what it thought I was saying so I could get an idea of what letters I was doing wrong • I feel like there's cool stuff to explore in the UI. For example, how about just circling words in the prompt to interact with those items. How about just drawing an arrow pointing up for "Go north". This is something that you can do that keyboard driven IF can't do
b
hey, thanks for the feedback! in case it's helpful as you mess around: the "folly tutorial" will repeat what it thought you were saying if it wasn't able to make sense of it.
c
Oh right whoops I jumped straight into Bronze šŸ¤¦ā€ā™‚ļø
b
understandable! one thing that's been tricky to balance is that gesture-/handwriting-based ui feels less discoverable, since there's fewer affordances on-screen. right now i'm leaning on the tutorial to fill some of the gaps, but it feels like there should be a better way to integrate that into the app itself...
and yep, definitely agree on the ui opportunities
n
I've always thought it would be interesting to do a "Marauders Map" (Harry Potter reference) type UI for a story game on an ePaper device
Like the device is some sort of magical artifact that you interact with
āž• 1