2023-04-20 04:19:58 <veltas      > I've been putting in a lot of extra hours for a deadline, really sucks
2023-04-20 06:54:14 <nature      > Hi all!
2023-04-20 06:54:16 <nature      > 'sup KipIngram ?
2023-04-20 06:54:42 <nature      > How is your graphical forth coming along?
2023-04-20 06:55:39 <nature      > I also wanted to ask here if anyone here had thought/opinions on small circular data stack (8-9 elements)?
2023-04-20 10:30:48 <crc         > nature: that would be too shallow for me
2023-04-20 10:34:24 <nature      > Do you have an example?
2023-04-20 10:52:40 <crc         > Loading and running a mandelbrot viewer pushes me to a max depth of 23 items on the data stack and 78 on the address stack
2023-04-20 10:55:13 <crc         > no single word uses more than 4 elements (most are 2 or less), but on the whole many values are placed on the stack as things run
2023-04-20 10:57:49 <nature      > makes sense
2023-04-20 11:06:59 <veltas      > It's a radically different game with that tiny a stack
2023-04-20 11:07:14 <veltas      > Do it only for fun, for creativity, or to solve some problem I can't imagine
2023-04-20 11:16:43 <KipIngram   > nature: Haven't done a lot with it so far.  I actually haven't done any Forth work since early last year, unfortunately, beyond just pondering some things.
2023-04-20 11:19:26 <KipIngram   > It's still of interest to me - it's a fairly "radical" restructuring of the upper levels of the system, and it's the sort of thing I usually think about a lot before actually starting in on.
2023-04-20 11:20:15 <KipIngram   > The whole idea originated from a discussion here one day in which I complained that EXPECT is hard to implement without using more than a couple of stack items at a time.
2023-04-20 11:20:34 <KipIngram   > Especially if you're trying to support something like command history etc.
2023-04-20 11:20:46 <thrig       > or the spanish inquisition
2023-04-20 11:21:03 <KipIngram   > Someone pointed out that some of the stuff I had on the stack really should have been state variables associated with the console.
2023-04-20 11:21:42 <KipIngram   > In that case that felt to me like just creating variables for the sole purpose of relieving the stack, which I didn't like, but then when I started looking at it from the perspective of the graphical system such state variables naturally appeared.
2023-04-20 11:22:11 <KipIngram   > It feels a little like  "turning some things inside out."
2023-04-20 11:22:30 <KipIngram   > But it also feels like an "interface" much much more compatible with modern practices.
2023-04-20 11:23:03 <KipIngram   > Traditional EXPECT ONLY knows how to respond to keyboard events - if a mouse event or so on comes along, it has no idea what to do with that.
2023-04-20 11:23:27 <KipIngram   > But in a graphical system you'd be responding to those keyboard events as part of a general event handler.
2023-04-20 11:23:50 <KipIngram   > They might go to a text field on screen, depending on focus.
2023-04-20 11:24:13 <KipIngram   > So the stuff actually handling that text field could be a lot simpler - it would only get sent key events that it actually needed to do something with.