Hey- Erik Uzureau wrote: > That sounds like a great plan. > > Eventually, I think we'd like to have *all* style information out of > the code and into css classes, and your attack here sounds perfectly > in-line with that. > > The best plan would be to make a ticket with description of the > proposed changes and/or a patch. I think this is a great benefit to > the library. >
Good first steps would be to add addClassName and removeClassName methods (or similarly named) for adding/removing class names one at a time from elements. We currently clobber old class names wherever we change them. In order to really support cascading styles, we want to delicately add and remove class names instead of clobbering old ones. Tim - maybe ours would be named addDisplayClass and removeDisplayClass > E > > On 1/28/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Hi list, >> >> currently the OpenLayers code contains a lot of hard-coded cursors >> (this.map.div.style.cursor = "xxx"), which makes it hard to change its >> default cursor behaviour. I am in need of the ability to change the cursor. >> >> Does anyone have ideas on how to tackle this best? What's the best place: >> Handler or Control? >> >> Ideally it would also be possible to change the cursor on mousedown, like >> Google Maps does for pan. So there would need to be 2 css classes, and the >> code for activate, mousedown and mouseup should change the css class. >> >> Ideas? >> >> Best regards, >> Bart >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://openlayers.org/mailman/listinfo/users >> > _______________________________________________ > Users mailing list > [email protected] > http://openlayers.org/mailman/listinfo/users > > !DSPAM:4033,479deddc167055409313003! > _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
