maybe instead of trying to make a hypercard clone i could focus instead on trying to formulate a “recipe” for a hypercard clone- a format (abstract or concrete) and prose, and a test suite for minimal expectations around how one should behave (modernis...
-
Luci for dyeingreplied to Luci for dyeing last edited by
the essentials of what made hypercard good: it only had 5 things
button
text field
background
card
scriptits entire manual was just 100 pages with pictures
it includes interactive tutorials and loads of ready to reuse premade assets
you vould just draw anywhere
and there isn’t a seperate make vs run mode. you interact with a stack using the same app and tool set as authoring; no wall exists between creators and consumers
-
Riley S. Faelanreplied to Luci for dyeing last edited by
@zens FWIW, I find it's generally useful to think of software solutions not as specific pieces of code, but as the rulesets according to which any number of specific pieces of code doing mostly the same thing can be constructed. Hence, the focus on protocols, data formats, and APIs rather than anything tied to a specific code, or specific piece of hardware.
-
Riley S. Faelanreplied to Luci for dyeing last edited by
@zens There's still one thing that you might want to add in the modern world:
a simple spreadsheet. Something mostly for data. The benefits of allowing formulas in a spreadsheet inside a HyperCard clone are debatable, at best.
Not as a prominent thing, but as an available thing. Unlike mid-1980s, when spreadsheets were new, a lot of people who need to do small programming things without "going deep" have background in spreadsheets to begin with, and can think of a small app most easily in terms of a table or few.
-
Riley S. Faelanreplied to Riley S. Faelan last edited by
@zens As seen on the attached ... er, picture, I happen to have thought about this, and I would be happy to collaborate on working it into a system. Together with a few specific pieces of code, obviously, even if the main output is to be abstract.
-
Luci for dyeingreplied to Riley S. Faelan last edited by
@riley there is a proven way of handling this and it is that a stack is just a way of viewing rows in a database table- one row per card; hypercard let you construct simple databases in precisely this way in which a “background” was actually a clever name for a table schema+form layout
-
Luci for dyeingreplied to Luci for dyeing last edited by
@riley ( i don’t see a picture)
-
Riley S. Faelanreplied to Luci for dyeing last edited by
@zens Ah, nice. I have seen it in some '90s' clones, but I haven't really played with the Very Original HyperCard.
-
Riley S. Faelanreplied to Luci for dyeing last edited by
@zens It's a metaphoric one. :blobcatblush2:
-
Luci for dyeingreplied to Riley S. Faelan last edited by
@riley ah so i see you are talking about a different simple spec for a spreadsheet type of program free of the blowt of something like excel . csv with a little extra
-
Riley S. Faelanreplied to Luci for dyeing last edited by
@zens Not necessarily, and I'd be a wee bit cautious about too aggressively combining spreadsheet-kind of programming with HyperCard kind of programming. My point was, the table integration should be explicit. On one side, it means, you should be able to easily see, and show, and edit the table as such; on the other, that the table be something easily interactable with other tools, like a TSV. (Microsoft ruined CSVs in Europe, by introducing the incompatible version that uses Umlauted Commas ('
;
') for locales where commas are used as decimal points, but refusing to rename it or add any clear indicators about the separators being used in any particular file.)