[Bese-devel] Re: dom-id's in xxx-select-field elements
Marijn Haverbeke
marijnh at gmail.com
Thu Jun 8 20:44:36 UTC 2006
I'm just replying to myself, don't mind me :P
On 6/7/06, Marijn Haverbeke <marijnh at gmail.com> wrote:
>
> Also, is there a way to make select inputs where you can specify both the
> values and text of the options? I thought alist-select-field would do this,
> but it just uses the keys of the alist as tags and ignores the rest of the
> list. I have a field that shows strings that can vary (because of
> internationalization), which represent a limited set of options, so I wanted
> to use a fixed set of values but also specify other option tag texts, if you
> get what I mean.
>
In the meantime I have figured out what alist-select-fields do, but they
work exactly backward from what I would expect. I was expecting I could pass
it an alist of (key . label) pairs, and it would show the labels to the
users and give me back the keys as values. Right now it works rather oddly,
the cars of the pairs are used as labels and the cdrs as keys, but when you
want to pass it a :value (or even :client-value) to use as a default you
have to use the car value (which, in my case, is a string that will be
different for different clients due to translation and is really unsuitable
for that kind of thing).
My question is, is anybody very attached to the way the ...-select-field
classes currently work, or would it be a good idea if I overhauled them to
be a bit more consistent? It's also rather hard to make them support the
multiple attribute (see my other mail) without lots of duplicated code the
way they work now.
How stable should the external interface of ucw be considered? There might
be some other things that I would prefer to be done in another way, but I'd
rather not make myself impossible by raging in here like a drunken elephant
and tell you all how things should be.
Marijn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20060608/6c439f83/attachment.html>
More information about the bese-devel
mailing list