I think macOS needs more "bicycles for the mind".īike is small enough to fully understand. This makes it easier to track what’s going on, and it’s fun! Why Bike Outliner? Your ideas flow across the screen instead of jumping from position to position. Outlines are powerful, but can be confusing. Bike is a powerful outlining tool for thinkers and writers. Make lists, take notes, and save your ideas. Unlike a web app, Bike is efficient and at home on your Mac. Update 5:35 PM Pacific: youâll also need mutex.h and mutex.c.Write to think. It would still be a 32-bit app and the to-do list would still be huge â but at least it would work again. So: that would get it back up on Mavericks. Hereâs MacSocketNetEvents.c, which replaces OpenTransportNetEvents.c. If I did, I could get Xcode 3.x and the OS X 10.5 SDK and do a build that would run on Mavericks.īut if youâre a programmer and have such a machine, please feel free. The problem is that I donât have a machine capable of running OS X 10.6. It needs more testing and surely needs some fixes, but it exists and does at least work to the extent that I tested it. The main issue is that Open Transport went away, and the networking layer should be replaced with sockets. There is, however, a shorter path to getting it up-and-running on Mavericks. I described this path in just a few paragraphs, but itâs bigger than it sounds. The database, language, utilities, and other low-level things would remain written in C and shared with Windows. I would structure things this way: the UI would be Cocoa and not shared with the Windows version. I would say repeat until finished, and thatâs partly true, but eventually you get to the UI. Ideally it could compile with its only dependency the database layer. ![]() Same issues apply: it shouldnât use globals, it should be thread-safe, and it should be 64-bit. The next thing to tackle would be the language, the compiler and evaluater. The language uses dot notation to refer to things.) Tables can hold tables, scalars, scripts, and some pre-defined objects. (For those who donât know: the database is a key-value tree structure. Ideally this would be a project itself, one that could also build as a stand-alone library (which was done once in the past). (Though you might allow the exception that databases beyond a certain size canât be opened in 32-bit mode.) Make it compile for 64-bit, and make it so a database file created on a 64-bit Mac can be opened in 32-bit mode. Make it so that it doesnât use globals and does us preemptive instead of cooperative threads. I recommend starting with the database layer. This just adds to the complexity of making any changes.ĭave mentions that itâs organized in layers, and it is. There are some things that should probably be nuked: running as an OSA component, displaying IOA (MacBird) cards, menu-sharing. ![]() (There are some translation verbs, but basically the system expects strings to be MacRoman-encoded strings with single-byte characters.) Text editing uses a third-party library called Paige which should be just nuked in favor of the built-in text editor. Thatâs the only way you can build and debug, so you can understand how itâs supposed to work. Which means you really need a machine running OS X 10.6 and Xcode 3.x with the 10.5 SDK. It uses a bunch of other deprecated APIs: file system, resource manager, etc. Though it was Carbon-ized, it still uses WaitNextEvent rather than Carbon events and timers. It uses cooperative multitasking rather than preemptive. Switching to 64-bit may be a major challenge because of the database format. (Thereâs no Cocoa Foundation in there, and only the most minimal use of CoreFoundation.) Memory is mostly Handles and Pascal strings. Switching to Quartz is not a straightforward change. ![]() There are all kinds things that would have to be fixed before it could be made a modern Mac app. Youâll notice lots of structs and function pointers.) (Itâs written in C, at least, and not C++. Itâs old code, and it doesnât look anything like what a modern Mac programmer would write. The earliest comment I can find is from August 20, 1990, though it appears the project was started before then. Dave Winer wrote about choices for Frontier/Mac users, now that Frontier and the OPML Editor wonât run on Mavericks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |