Re: [PATCH] Add user content APIs for WebKit Xwidgets

[Qiantan Hong <qthong@stanford.edu>]

Currently, I store the ALIST of handlers on xwidget-plist.  If we're
going to have it for groups of related Xwidgets, what is the best
place to store it? On the xwidget-plist of the head xwidget? Then we
have to inspect the xwidget-plist in the C function kill_xwidget and
migrate a specific subset of properties...

Or we should add another slot and provide xwidget-group-plist and
set-xwidget-group-plist, which will only have non-NULL value on the
head xwidget and is migrated automatically?

Best,
Qiantan



> On Oct 23, 2022, at 5:30 PM, Po Lu <luangruo@yahoo.com> wrote:
> 
> Qiantan Hong <qthong@stanford.edu> writes:
> 
>> Applying to all related Xwidgets sound like a good idea. I think we should
>> formalize the "group of related Xwidgets" as some kind of object? Maybe
>> a record type implemented in Lisp, or a pseudo vector (which I don't know
>> much about how to implement). An alternative is to expose content manager
>> as a pseudovector, which will in fact have 1-to-1 correspondence with "related
>> group", but I like related group more because it feels like a nicer abstraction.
> 
> I don't think that is necessary.  There should at most be a function
> that returns a list of all related xwidgets.
> 
> Pseudovector types are a limited resource.  There can only be 64 at any
> given time, so it would be a good idea not to waste them on such
> trivialities.