Hedley Roos wrote:
>> Could you explain your use case with more details
so that we can maybe help
>> you ?
>>
>
> I have a form which I automatically save upon data
entry into a field.
> The situation is similar to a calendar popup widget and
a form field
> combo, except my widget does not pop up but renders
inline. As soon as
> the user makes a selection on the selection widget my
input is visually
> updated via KSS and a Python script (say foo.py), but
then I also want
> to fire the change event on the input to persist the
data.
>
> I cannot just call the save code from foo.py since it
is not supposed to
> have knowledge of the application using the widget.
I am not sure I understand this last sentence... do you mean
you are
writing a widget, iow generic code that should not know
which other
widget it collaborates with ?
>
> Any ideas?
--
Godefroid Chapelle (aka __gotcha)- BubbleNet http://bubblenet.be
_______________________________________________
Kss-devel mailing list
Kss-devel codespeak.net
http:
//codespeak.net/mailman/listinfo/kss-devel
|
