OOLOI.ORG
Menu

OOLOI

An Organism Evolved.

OVERVIEW

DOCUMENTATION

NEWSLETTER

Surface Tension

17/2/2026

10 Comments

 
Picture
Ooloi is now a running desktop application on macOS, Windows, and Linux. It opens, it responds, it remembers where you left it. A concrete thing, like any other program.

But that's not enough. The next step is teaching it to talk. Ooloi's frontend and backend have always been separate components communicating through a defined protocol; in standalone mode, they simply appear as one and the user needn't think about it. But this disciplined split personality was designed that way for a reason, and it's now time to act on it.

ADR-0036 lets the two halves run apart — so one Ooloi can connect to another, or to a centralised server. You invite a collaborator; a secure connection opens. They disconnect; the application returns to working alone. No restart, no mode switching.

The separation was always there. Now it becomes visible.
Picture
10 Comments
Magnus Johansson
17/2/2026 11:38:32

This seems to become a great feature of Ooloi, and it will be very interesting to try it out when there is music on the screen. A little thing I am not fond of is that the three dots in the menus follow directly after the last word which in common text signifies an unfinished word, e.g. "unfin...", but this is the norm in graphical user interface menus, I have been told.

Reply
Peter Bengtson
17/2/2026 11:44:54

Thank you, Magnus – and only a few minutes after publication! The ellipsis convention is one of those places where GUI design and typographic tradition genuinely collide. You're absolutely right that in running text it signals truncation, but in menus it dates back to Apple's 1984 Human Interface Guidelines: the three dots promise that a dialog will appear before the action completes. "Save" acts immediately; "Save As..." consults you first. It's a continuation marker: you'll be asked before anything happens. A small courtesy, typographically expressed.

Reply
Magnus Johansson
17/2/2026 11:58:13

You're welcome, Peter. The Apple authors in 1984 should have been a little more learned (like Fridolin) when it came to writing conventions.

Reply
Peter Bengtson
17/2/2026 12:34:37

Well, I think back in 1984 the Apple symbol was still a multicoloured 70s thing someone could have designed at Woodstock whilst high on LSD. They've learnt since, but they did establish a few conventions that still are with us. ;)

Magnus Johansson
17/2/2026 13:46:31

"Well, I think back in 1984 the Apple symbol was still a multicoloured 70s thing someone could have designed at Woodstock whilst high on LSD."

I think they should have stayed graphical but without LSD and chosen e.g. □ for the menus, so "Import MusicXML □".

Reply
Magnus Johansson
18/2/2026 16:48:55

There is only one menu in Ooloi that differs from the menus of Igor Engraver and that is View which is Layouts in Igor Engraver. Will the contents of those two menus be similar?

Reply
Peter Bengtson
18/2/2026 17:11:35

There's no attempt to reconstruct Igor Engraver's menu bar, and these are very early days, so you can expect things to change as the GUI develops. Right now it's the standard plain vanilla menus of any new app.

But I do prefer minimal GUIs that don't get in the way, so there will be as few menus as possible, as a general rule.

Reply
Magnus Johansson
18/2/2026 18:03:54

OK, I see. What about Ooloi having a separate piece window apart from the layout windows like Igor Engraver has?

Reply
Peter Bengtson
18/2/2026 21:43:36

The first version of that window already exists on screen today. ;)

Reply
Peter Bengtson
19/2/2026 09:07:34

In fact, your question is important in another way. There’ll be a blog post on “The Piece Window” and its role — and why re-implementing it isn’t nostalgia, but something the ontology requires. (And yes, I’ll explain what ontology means in this context.) The fact that you’re asking about it is telling. This is structural, and I’ll explain why.

Reply



Leave a Reply.

    Author

    Peter Bengtson –
    Cloud architect, Clojure advocate, concert organist, opera composer. Craft over commodity. Still windsurfing through parentheses.

    Search

    Archives

    February 2026
    January 2026
    December 2025
    November 2025
    October 2025
    September 2025
    August 2025
    July 2025
    June 2025
    April 2025
    March 2025
    September 2024
    August 2024
    July 2024

    Categories

    All
    Accidentals
    Alfred Korzybski
    Architecture
    Benchmarks
    Clojure
    CLOS
    Common Lisp
    DDD
    Death Of Igor Engraver
    Documentation
    Donald E Knuth
    Dorico
    Dynamic Programming
    Finale
    FrankenScore
    Franz Kafka
    Frontend
    Functional Programming
    Generative AI
    GRPC
    Igor Engraver
    Jacques Derrida
    JVM
    License
    LilyPond
    Lisp
    Localisation
    MIDI
    MPL 2.0
    MuseScore
    MusicXML
    Ooloi
    Ortography
    Pitches
    Playback
    Plugins
    Python
    QuickDraw GX
    Rendering
    Rhythm
    Rich Hickey
    Road Map
    Scheme
    Semiotics
    Sibelius
    Site
    Skia
    Sponsorship
    UI
    Umberto Eco
    Vertigo
    VST/AU
    Wednesday Addams

    RSS Feed

Home
​Overview
Documentation
About
Contact
Newsletter
Ooloi is an open-source desktop music notation system for musicians who need stable, precise engraving and the freedom to notate complex music without workarounds. Scores and parts are handled consistently, remain responsive at scale, and support collaborative work without semantic compromise. They are not tied to proprietary formats or licensing.
​
Ooloi is currently under development. No release date has been announced.


  • Home
  • Overview
    • Background and History
    • Project Goals
    • Introduction for Musicians
    • Introduction for Programmers
    • Technical Comparison
  • Documentation
  • About
  • Contact
  • Home
  • Overview
    • Background and History
    • Project Goals
    • Introduction for Musicians
    • Introduction for Programmers
    • Technical Comparison
  • Documentation
  • About
  • Contact