[Bese-devel] Re: dom-id's in xxx-select-field elements

[Lou Vanek]

Dear Drunken Elephant  :)

I'm kinda new around these here corners of the net, but
allow me to add my thoughts.

The external interface seems to be in flux (the examples
don't even compile any more due to interface changes). So
changing things around to be more consistent seems more than
workable.

I would go ahead and make the changes, create a few patches,
and submit 'em. What's the worst that can happen? You get
a code base that's more to your liking (it's partially YOUR
code), and Marco may decide not to merge your changes. But that
doesn't change the fact that you have changed ucw more to your
liking. Your changes remain intact every time you run darcs
(unless of course the SELECT code is changed in the future, but
then you can simply refuse that patch).

I've been working on several patches myself. I'll probably be
submitting them in the next day or two. I'm trying to get ucw
to play nice with clisp and araneida. Marco's code walker has
my head hurting, but the worst is over.

Lou Vanek
-- 
To sin by silence when they should
protest makes cowards of men.
--Abraham Lincoln

[sorry if this is a double post -- gmane is acting up]


Marijn Haverbeke wrote:

> I'm just replying to myself, don't mind me :P
> 
> On 6/7/06, *Marijn Haverbeke* <marijnh at gmail.com 
> <mailto: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
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> bese-devel mailing list
> bese-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel