3 ms·

Wha... halfway down the second page (second bullet point) there's the note that > *It's MacOS, but certain APIs are no longer supported. [...] They are also dr

• masswerk 5y ago
  This was an OS-wide API. On the surface, it worked somewhat like Smart Objects in Photoshop, but rather than converting a file on embedding, you first "published" it and then the content could be embedded by any "subscriber" that supported/made use of the API. (Editing the file on the publisher side would consequently update any embedded content. Like in PS, any attempt to edit a subscription would open it in the publishing application.) However, I have no idea about any implementation details.
• alphabetter 5y ago
  As a classic MacOS developer back in the day, "publish and subscribe" doesn't mean what you probably think it does. It isn't like "publish and subscribe" in Javascript or similar. In classic MacOs "publish and subscribe" was a kind of real-time clipboard which allowed you to paste contents from one application in to another and have it updated in real-time if you edited the source file. The idea was interesting, but it created odd interactions and corner cases that weren't nice. It was also very slow and buggy in practice. Not many applications supported it, and those that did didn't support it well in my opinion. https://en.wikipedia.org/wiki/Publish_and_Subscribe_(Mac_OS) https://en.wikipedia.org/wiki/Publish_and_Subscribe_(Mac_OS)