Use CCK widgets in Views exposed filters ?

Which module is this from?

This is the field module's responsibility to deal with. Re-assigning to CCK queue (though I'm not 100% sure that's a core CCK field being used, so this might be re-assigned again).

Yeah, looks like a number field.
I'm not sure about the whole thing, though.
The '$' prefix is a CCK widget thing.
The form elements presented in the UI for exposed views filters are in no way expected to be 'cck widgets'.

At best this would be a feature request, and one with conceptual roadblocks :
The widget is a 'field instance' property.
Your field_prop_rent_weekly field can appear in several content types.
It could be setup to use a 'textfield' widget in type1, and a select widget in type2.

We have no way of telling which widget with which settings is to be used for exposed filters UI.

We have no way of telling which widget with which settings is to be used for exposed filters UI.

So how does Views determine which widget to use when a CCK module provides more than one? I've tried change the order of the array in hook_widget and hook_widget_info, but that didn't do it, even after clearing caches.

Views doesn't use CCK widgets, it doesn't know anything about them. CCK would have to do this somehow, but it does not do it now, and it would be hard to do. Views creates it's own form elements for exposed filters, which are either drop-down selectors to choose one from a of a selection of allowed values, otherwise it uses plain textfields.

And I think it's safe to say it won't get done in the D5 version for sure, since we're adding no new features to D5, so it would be a feature request for D6.