FourthWorld wrote: ↑Thu Dec 23, 2021 3:58 pm
"Card" is also a UI element in the Android UI specs, and some web frameworks.
Same spelling, different uses.
xTalks live in a metaphor where they fill the window, with only one card is visible at a time.
Modern usage elsewhere has them as a thing inside the window, letting you spread them out within the window's content region.
Of course xTalks can be used to make such things. But making them in an xTalk would mean using a field or a group, rather than the classic xTalk-native card object.
Though the spelling is the same, and some use cases may overlap, modern card elements as implemented in other systems are a different beast.
One of the few nomenclature differences I liked in Toolbook was using "page" for what we call "card", a choice that turned out almost prescient once the web took over.
Is it really a different usage?
Technically a CARD
IS a content view that gets rendered inside a Window, and with substacks, menustack, etc. it
IS possible to have a Card inside another Card, which is the way that DataGrid works, although I do understand what you're saying about this being more like a <DIV> in HTML, which would make "ActiveCards" more like a GROUP Control than it is like a "Card" in our thing. But "Card" is NOT the same size as a Window, you can have a card that scrolls inside a stack window, you can have card controls in a stack that are outside of the viewable region of a Window. A "Stack" I think has more closely related usage to a window than card does. There is some, albeit limited, Window related syntax separate from the Card/Stack related syntax. Windows have their own ID#. Distilled to very basic terms, however we are talking about Cards that are content views or sub-views, that are made up of text/data, graphics and UI controls, and get rendered inside a window (depending on onscreen or offscreen positions).
My thinking on this encapsulated exchange format is more about abstraction, interoperability, and portability than it is about any direct conversion. If a "Card" becomes a Toolbook "Page", an NSView object, an HTML "<Div>", etc. that's all good with me.