<Hilltop - Episode 1>
# two-minute-week
d

Hilltop - Episode 1

👍 3
i
The video is set to "private" — you probably want to set it as "unlisted"
d
Done
e
Its nice to see a proportional font programming system. Fixed pitch is so archaic, however many fonts have too thin punctuation marks so unless you use a custom font it is easier to work with. Not sure that notating literals by using a darker color is going to pan out. Sooner or later you are going to want to use that annotation for some other purpose, and are quotes really so bad?
w
Getting Self vibes. Man, I remember when Verdana was my go to programming font. 🐺
i
Is there a particular kind of app that you intend for Hilltop to be well suited to? Something like hypertext, or CRUD? Also, curious to hear more about what direction your exploration is headed.
d
I don't have a type of app in mind. I'm exploring several things at the same time: • What if we took away the row-and-column aspect of a spreadsheet, and just kept the cells, where a cell is something that holds an object definition? • And what if when you decide to create a new cell/object definition, it’s based on a predefined object type, such as of a number, text, an image, a sound, etc. (as opposed to spreadsheets, where you can't immediately tell whether a number in a cell is numeric or text)? • And what if predefined object types have predefined attributes, such as ‘value’ for primitive object types, X and Y coordinates for object types that can be displayed, etc.? • And what if the programmer provides value definitions to whichever attributes she likes, such as literal values or formulas that reference values of other attributes? • And what if an app is defined as a collection of these cells/object definitions and the value definitions of their attributes, just as in a spreadsheet? • And what if "running" the app simply means instantiating the cells and letting them "do" whatever their object types "do" (e.g., an image-type object "displays" if its X and Y attributes have values; a sound-type object makes a sound if its ‘volume’ attribute is set to some nonzero value which, according to its value definition, happens when the value of some boolean-type attribute of another object changes)? • And what if, as in a spreadsheet, a behind-the-scenes manager propagates value changes to various object attributes when the values of other object attributes change, and this is what manages the app’s behavior? • And what would all this look like as text-based programming (as opposed to visual programming like Scratch)? • And could we eliminate syntax errors using a structure editor, where the keyboard is only used when naming objects, entering literal values, and editing comments? • And what if the structure editor is in the form of context menus? • And what if tapping different types of code elements opens different context menus, each only showing valid programming options based on the tapped code element type? • And would this mean that we could program on our phones and tablets?
i
This feels like a rich vein! I'm excited to see where you go with it. Do you have a working prototype? How's that going?
d
Nope. It's design and mockups only, at least until I find my Wozniak
❤️ 2
i
Put out the call here! According to the survey, there are a lot of folks who are looking for projects to contribute to.
g
this is absolutely great and if you haven’t yet you should absolutely check out self @Dan Swirsky

https://youtu.be/3ka4KY7TMTU

❤️ 1

https://youtu.be/Ox5P7QyL774

it’s pretty much dead now but a huge inspiration
❤️ 1
d
Yup. Saw these a while back.
w
A classic. 😉