In what context do you want to use this form? Do you want to send its information or save it to a tiddler, etc.?
I guess for an implementation of such a control one would... a) define a placeholder for each such control in the respective form by giving it a specific class b) invoke a macro - or simply js code - after the form has been rendered, which... - based on the class information identifies the form element(s) - creates the missing spin controls and initializes their values - assigns the control functions to any of them c) read the value from the input element(s) related to such controls and... - send it - write it to a tiddler field - etc... Sounds like a doable thing, esp. with the code you've provided in your link [1]. But, do you think it's worth the effort, considering the length of the codebits that would accumulate even through the quite straight forward example you've provided? In other words: What's the usecase in which you think this kind of control spins a whole lot better than - say - a dropdown or a mere text input? At least, the one situation where I would actually use such a control instead of using my keyboard is when I wanted to simply increment a value by 1... which could easily be done with a button before the input that reads [-] and one behind it that reads [+]. Cheers, Tobias. [1] http://www.switchonthecode.com/tutorials/javascript-controls-the-spin-control -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
