[00:43:28] <shokin>	 I want to upgrade SMW to 1.8.0
[00:44:24] <shokin>	 What is best way to fix data records, if I say I am also going to edit almost all of the pages.
[00:45:45] <shokin>	 Should I just php SMW_setup.php --delete, and then install the new SMW 1.8.0?
[03:46:43] <alingae>	 searchlable is not working when limit=-1
[03:47:05] <alingae>	 SMW BUG: searchlable is not working when limit=-1
[15:56:10] <Ulfr>	 Hey all, should I ask a question about semantic forms here or in the vanilla mediawiki channel
[15:58:23] <Frank__>	 It can't hurt to ask, go for it Ulfr
[15:58:55] <Ulfr>	 word, I'm trying to use show on select and it's being very buggy. it works only sometimes, but usually has all the div elements visible
[16:00:27] <Frank__>	 That's the feature where you select a value in one form control and it's supposed to reveal another section of form, right?
[16:00:50] <Ulfr>	 Correct. You specify a div layer's ID and poof
[16:01:00] <Ulfr>	 Works more on Firefox but Chrome hates it
[16:01:25] <Frank__>	 I've never had any success with it myself.
[16:02:23] <Frank__>	 It's probably JavaScript incompatibilities between browsers.
[16:02:25] <Ulfr>	 ;;
[16:04:01] <Frank__>	 Do you know JavaScript, maybe jQuery?  It's pretty easy to script up somethink like this on your own.
[16:05:40] <Ulfr>	 Frank__: Yeah, I've coded most of this application in jQuery, was just hoping to not have to do the input forms
[16:07:53] <Frank__>	 I'd still set up the forms through the wiki.  All you have to do after that is watch the change event on your select and show/hide the divs that go along with it.  Not too crazy, unless you have 200 divs to swap out.
[16:08:26] <Ulfr>	 Frank__: How do you bind events to fields defined in a form?
[16:08:44] <Frank__>	 You might even be able to automate it a little, name the divs in sync with the option values of the select, so you make the changes based on a formula.
[16:09:36] <Frank__>	 The biggest trick to binding the events is that the wiki builds the fields for you, so you get
[16:09:57] <Frank__>	 inputs and selects with ids you don't control.
[16:10:06] <Frank__>	 For instance...
[16:11:36] <Frank__>	 On one of my forms the first select has an id of "input_2".  Not ver descriptive.
[16:12:45] <Ulfr>	 oh, okay. makes sense
[16:12:54] <Ulfr>	 and how do you get the js into the form? i've been using widgets
[16:13:02] <Frank__>	 However, it also gets a name based on the form and field, like FoodSearch[Ingredient]
[16:13:26] <Frank__>	 Selecting for a value with [] is annoying but very doable.
[16:14:36] <Frank__>	 Something like $("select[name='FoodSearch\\[Ingredient\\]']").doSomething();
[16:15:04] <Frank__>	 You have to double esape the brackets.
[16:16:31] <Ulfr>	 Frank__: Thanks a lot man :)
[16:16:35] <Frank__>	 Sure!
[16:16:44] <Frank__>	 I hope that helps.
[16:21:26] <Ulfr>	 Frank__: I'm following the how to bind the events, what I'm still struggling with is where the <script> tag goes
[16:24:29] <Frank__>	 I build it into my skin.  You will want to put some kind of checkpoint into the script so it verifies it's running on the page you want, so it's not messing with a similar form that doesn't need rearranging.
[16:25:12] <Frank__>	 So you might check to see that FoodSearch[Ingredient] exists, then let the body of the script run.
[16:26:35] <Frank__>	 That's one of the pain points of the technique, it's not as simple as you might like to just pop a script into a particular page.
[16:27:31] <Frank__>	 You end up with it pn the whole wiki, but block anywhere you don't want/need it.  It can feel a little inelegant.
[16:32:37] <Ulfr>	 Frank__: Yeah, that sounds messy. Why not just put it in Common.js?
[16:34:05] <Ulfr>	 Actually, widgets seem to work in the forms, do you use them at all?
[16:34:36] <Frank__>	 You could put it in common.js, sure.
[16:35:01] <Frank__>	 I have a bad habit of going directly to the skin for inserting scripts.
[16:35:16] <Frank__>	 I haven't worked with widgets.
[16:36:31] <Ulfr>	 It's an extension that you can call on a page, and the way I'm doing it you just plop the widget call on one line and use a semantic refresh and your js is there
[16:36:51] <Ulfr>	 My actual javascript is located here http://wikidoc.org/index.php/Widget:SandboxNew
[16:37:07] <Ulfr>	 but it's called here: http://wikidoc.org/index.php/Board_Review
[16:41:36] <Frank__>	 Sounds very useful.