Comments on: Opinionated Input Builders – Part 9 override the default Date Time picker

By: Maarten Balliauw

Maarten Balliauw — Thu, 02 Jul 2009 09:34:02 +0000

Also checkout http://haineault.com/media/jquery/ui-timepickr/page/, which is a jQuery time picker I find quite nice and fancy.

By: erichexter

erichexter — Tue, 30 Jun 2009 17:46:19 +0000

@jimmy… by easier to test you suggest that the string based methods are tested and that you correctly setup the ViewContext for the Html Helpers. I would rather change this implementation so that rather than taking a DateTime I would make a type that contains all the date needed so that the ViewModel for this input is cleaner. At the end of the day I think this would be pretty easy to test with QUnit.. and given the amount of javascript I think it would be necessary.

@David, I am not sure that this jquery could use class selectors, at least not without it being turned into a plugin. This has to work in a way where multiple inputs of the same type could exist on the same page and they need to work independently of each other. But that being said, I will update the source code and would love to see how it could be done with class selectors alone. I imagine it would have to include some knowledge of the sibling controls.

By: David Alpert

David Alpert — Tue, 30 Jun 2009 15:54:21 +0000

You could factor that jQuery out of your control and into an external script file by using CSS classes instead of ID’s to identify your HTML elements. The script can then use class selectors to wire up your client-side event handling.

This gives you lighter pages, cacheable javascript, and better overall seperation of concerns on the front-end.

By: bogardj

bogardj — Tue, 30 Jun 2009 13:50:38 +0000

Man – master pages are HTML inheritance. It’s basically the same thing, right? Derived classes, template method, overriding methods to change behavior. I still prefer code, though, as it’s a lot easier to test and debug. Doing F11 through partials is not the easiest thing in the world.