4 ms·
> editing a running process in-place with a debugger/IDE, then the process is "saved" as an executable I am currently working on a variant of the Smalltalk ima
by mpweiher 8y ago
> editing a running process in-place with a debugger/IDE, then the process is "saved" as an executable
I am currently working on a variant of the Smalltalk image concept that works this way, based on Objective-Smalltalk[1] You have documents in a live coding environment, and those documents can be saved as executables.
One inspiration is DropScript[2], which was an app that converted Unix scripts into (simple) MacOS X apps. Another is obviously Smalltalk.
> An iPad app that lets people draw dataflow programs with a pencil
Objective-Smalltalk also has pretty good dataflow support. Drawing would be a reasonable addition.
[1] http://objective.st http://objective.st
[2] http://www.wsanchez.net/papers/DropScript/ http://www.wsanchez.net/papers/DropScript/
- cwp 8y agoHi Marcel! I'm thinking of something that would be a lot like Smalltalk, but with strict separation between program and metaprogram. (In the spirit of Alan Kay's notion of fences between metaboundaries). The IDE would run in a separate process from the program, and attach to the program via operating system debugging facilities. I think most of the problems with Smalltalk can be traced back to its origin as an operating system and the mingling of the program and tools for writing the program in the same image. Eg, shrink scripts for deployment.
- mpweiher 8y ago> via operating system debugging facilities. That's an interesting approach, let me know how it works out! In my previous efforts, I just used a small HTTP server inside the target program. You can see it in action here, fine-tuning an iOS target: https://www.youtube.com/watch?v=ArcClqt2vTc https://www.youtube.com/watch?v=ArcClqt2vTc Since it's HTTP, it also works on the device. You can obviously also access those facilities from within the process, at least for a macOS app. Right now, I am focusing on a more image-like user-experience, but with individual (small-ish) documents instead of a huge monolithic image. The difference in trying out UI-oriented idea compared to having to create a separate Xcode project each time is huge, and of course jut doing it live without restarting. My guess is that these documents will evolve to be a lot like .frameworks, so code + resources. Budding an app is then no more than just copying the app shell and filling it with the right frameworks. (See Xcode). Once budded, you might interact via the HTTP route. Or maybe via debugger?