Re: Metaclass & McCLIM revisited
"Yuri Davidovsky (as work at disclosure dot ie)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
> On 29 Jan 2026, at 22:39, Paul Werkowski (as pw at snoopy dot qozzy dot com) <[email protected]> wrote: > > CLIM is not just graphics. The major thing for me is the presentation system which maps a data object to what appears on screen, a 'presentation' of a 'presented data object'. I think what you are talking about here is the so called model-view approach, that is very commonly used nowadays for building interfaces, where you take an object instance and map its fields to GUI controls on screen. This way you can update a slot value in the model by changing the position of a slider control, for example, and the other way around, by updating a slot in a bound object we can update the state of the GUI control. This is all done by calling specific function callbacks in the background, of course, to announce a change taking place. But I had an impression that it is something that is supported in CAPI too? You just need to create an accessor for an object that updates the GUI control when a field on the object gets updated, and set up a callback on the control that updates the model object slot value when the user interacts with it. Was the purpose of this journey to get some old CLIM code working that you do not care to port to CAPI?