Hacker News new | ask | show | jobs
by dylukes 1018 days ago
Some good news for you... Pad++ and Dynapad are in a decently runnable state again! Myself, Jim Hollan, and Tom Gillespie have been on and off working on refurbishing it.

Currently, there's still a good amount of rough edging from the mzscheme -> Racket rewriting, and support is primarily for MacOS and Linux.

Going forward, there's a lot of modernization to be done. In particular, Racket-on-Chez no longer affords escheme.h, so there's a lot of inversion of control to be done. I'm also working on and off on an updated multi-platform rendering layer to largely replace Pad++'a X Windows drawing, with the goal being to move more of Pad++'a logic up into the Dynapad layer in Racket.

https://github.com/Dynapad/Dynapad/

1 comments

Oh that's exciting! And an interesting group of collaborators.

When you're ready for some publicity be sure to put some description and images on the GitHub project. Right now it doesn't really say anything about what Dynapad is.

For sure. The repo was actually just private until a moment before I commented above. The long term goal is to refactor to a point where installation can proceed with a minimal/straightforward CMake/Racket build, without any archaic dependency versions of weird hoops.

For the time being the REAMDE.macOS is likely to be the shortest path to getting things running. That said, it's mostly Intel specific. Running on M1 Macs presents its own set of tooling issues (to do with Racket no longer using GNU Lightning).

I still need to fully document that (unstable) process.

Also to give a brief overview: Dynapad was/is a scheme based wrapper/GUI layer/scripting interface for building applications on top of the Pad++ primitives.

Sadly the version of scheme used is very long defunct. But the goal is to get everything modernized to the point this can be something you can work with (with minimal setup and work) using the whole modern Racket ecosystem!

Hi Nelson,

Long time since New Mexico! We are also putting together some documentation.

Best, Jim