[02:21:40] <TheWoozle>	 So, how can I access the value of SMWSQLStore3::$di_type_tables?
[02:21:56] <TheWoozle>	 It seems to be kind of critical for iterating through all the different types of relations.
[02:23:42] <TheWoozle>	 The description of SMWSQLStore3::getPropertyTables() makes it sound like what I'm looking for, but the code seems way too complicated...
[02:23:57] <TheWoozle>	 Maybe I'll just try it and see what I get.
[11:40:04] <gerrit-wm>	 New review: Mwjames; "Patch Set 4: Code-Review+2" [mediawiki/extensions/SemanticMediaWiki] (master) C: 2;  - https://gerrit.wikimedia.org/r/48740
[11:40:23] <gerrit-wm>	 Change merged: jenkins-bot; [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/48740
[11:47:39] <gerrit-wm>	 New patchset: Mwjames; "Extends smw.dataItem and smw.dataItem.factory() [DO NOT MERGE]" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/49028
[13:54:05] <gerrit-wm>	 New review: Nischayn22; "Patch Set 2:" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/47707
[16:07:05] <dbolser>	 so...
[16:07:11] <yaron>	 Hello!
[16:07:24] <dbolser>	 basically, I'm trying this diff:
[16:07:32] <yaron>	 (Continuing our discussion from #mediawiki.)
[16:07:50] <dbolser>	 [dbolser@localhost ExternalData]$ git diff
[16:07:50] <dbolser>	 diff --git a/ED_ParserFunctions.php b/ED_ParserFunctions.php
[16:07:50] <dbolser>	 index 610ddc5..7e211b7 100644
[16:07:50] <dbolser>	 --- a/ED_ParserFunctions.php
[16:07:50] <dbolser>	 +++ b/ED_ParserFunctions.php
[16:07:53] <dbolser>	 @@ -331,7 +331,7 @@ class EDParserFunctions {
[16:07:55] <dbolser>	                         }
[16:07:58] <dbolser>	                         $text .= $cur_expression;
[16:08:00] <dbolser>	                 }
[16:08:03] <dbolser>	 -               return $text;
[16:08:05] <dbolser>	 +               return $parser->internalParse( $text );
[16:08:08] <dbolser>	         }
[16:08:10] <dbolser>	   
[16:08:13] <dbolser>	         /**
[16:08:15] <dbolser>	 sorry for pasting, wouldn't paste much more or in #mw
[16:08:35] <yaron>	 Alright.
[16:08:51] <dbolser>	 seems to work OK, and shouldn't break existing code... I think...
[16:09:48] <dbolser>	 but it's basically the first thing I've come up with, so I don't know if it's a good or stable solution
[16:09:56] <yaron>	 What does it do?
[16:10:20] <dbolser>	 oh, in theory it allows things like "{{#for_external_table: {{template call: {{{Splicing}}} }} }}
[16:10:30] <yaron>	 Ah... cool.
[16:10:48] <dbolser>	 ah, where {{{Splicing}}} is an external variable
[16:10:55] <yaron>	 What do you mean, in theory? Does it work?
[16:11:11] <dbolser>	 mind you.. yeah, I dont' see redlinks to that template, for example
[16:11:40] <yaron>	 I don't understand.
[16:12:06] <dbolser>	 in the above example, I'd expect to see 'red-links' to 'Template:template call'
[16:12:15] <dbolser>	 because I don't have that template in my wiki
[16:12:27] <yaron>	 I see - so, it doesn't work.
[16:12:38] <dbolser>	 There are variables beeing pulled back by {{{Splicing}}}
[16:13:17] <dbolser>	 other This produces output: {{#for_external_table: Hello {{{Splicing}}} {{template call: {{{Splicing}}} }} }}
[16:13:51] <dbolser>	 but not the template call apparently, however, preview says that 'Template Call x' is being used in the page
[16:14:39] <yaron>	 Well, that's probably because you called the parser directly, which caused it to think it was parsing that template, or something like that.
[16:15:00] <dbolser>	 yaron: how should I call it?
[16:15:05] <yaron>	 I don't know.
[16:15:18] <dbolser>	 heh... I'll keep playing, and asking in #mw
[16:15:31] <dbolser>	 but in general, would you be happy with a patch like this for ED?
[16:15:32] <yaron>	 I mean, it's fine to call the parser directly - I'm just saying, that's why it was giving you "mixed messages".
[16:15:36] <yaron>	 Yeah, sure.
[16:15:38] <dbolser>	 ic
[16:15:40] <dbolser>	 cool
[16:15:50] <dbolser>	 it should simplify some of the other code too
[16:16:05] <dbolser>	 because .urlencode and store would not be necessary...
[16:16:31] <yaron>	 Maybe.
[16:16:31] <dbolser>	 but I'm wondering if I should create a new PF
[16:16:36] <dbolser>	 to be safe
[16:16:39] <yaron>	 That might be idea.
[16:16:42] <yaron>	 ideal, rather.
[16:16:52] <dbolser>	 OK
[16:16:59] <dbolser>	 thanks for time :-)
[16:17:10] <dbolser>	 I'll submit a pull request at some point
[16:18:05] <yaron>	 Not just to be safe, but also because the ideal syntax might be different - maybe there should be a #for_external_table_call_template, that takes in a template name and a list of external variable names.
[16:18:15] <yaron>	 ...each of which are passed as parameters to that template.
[16:18:33] <dbolser>	 yaron: that's what I thought first
[16:18:44] <dbolser>	 but it's more generic to just 'parse' the text
[16:19:02] <yaron>	 Yes, it's more generic, but the other way might be "cleaner".
[16:19:12] <dbolser>	 so people can mix parser functions, templates, formatting, whatever
[16:19:31] <dbolser>	 using the above people could make SIO...
[16:19:50] <dbolser>	 i.e. less code to maintain in the extension
[16:20:14] <yaron>	 Well, if it's possible, it'll be interesting to see.
[16:20:34] <dbolser>	 OK, I'll play around a bit more
[16:20:43] <yaron>	 I still thing having a #store_external_table function is a good idea, whether or not it becomes possible to replicate its functionality in wikitext.
[16:20:53] <dbolser>	 OK
[16:21:15] <dbolser>	 yeah, teh template call works fine once the template exists
[16:21:22] <yaron>	 Oh, great.
[16:21:32] <yaron>	 You didn't think to test that before you wrote me? :)
[16:21:53] <yaron>	 Never mind, doesn't matter.
[16:21:57] <dbolser>	 yaron: wanted to ask if it was an OK direction to take the extension, just can't help myself fireing off queries
[16:22:02] <yaron>	 Right.
[16:22:04] <dbolser>	 :-)
[16:22:08] <yaron>	 By the way, what's a pull request?
[16:22:21] <dbolser>	 oh, it's a development pattern on github
[16:22:36] <dbolser>	 perhaps the MW git repo doesn't have this concept
[16:22:44] <yaron>	 Not that I'm aware of.
[16:22:49] <dbolser>	 basically a logged request to apply a patch
[16:22:54] <dbolser>	 so it's super easy to do
[16:22:55] <dbolser>	 nm
[16:23:07] <yaron>	 Then again, there's volumes of stuff on Gerrit that I don't really understand.
[16:23:08] <dbolser>	 cheers
[16:23:13] <dbolser>	 hehe
[16:23:15] <dbolser>	 ty
[16:23:26] <dbolser>	 g2g, time to give a talk ;-P
[16:24:04] <yaron>	 Later.
[18:59:59] <gerrit-wm>	 New patchset: Foxtrott; "parameter "new window" for formlink and queryformlink" [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/48734
[19:01:24] <TheWoozle>	 Dangit... I just want to get the value of an arbitrary SMW_DataItem descendant, but there's no universal "convert to scalar" method other than getSerialization(), which is more than just the value.
[19:08:07] <Saruman>	 hmm that sounds like an interesting incantation...
[19:10:48] <TheWoozle>	 getSortKey() seems to return what I'm looking for, but that's got to be improper usage.
[19:15:00] <yaron>	 TheWoozle: I'm really not sure about this one, but it could be that you first need to convert it into an SMW_DataValue, using getDataValue() or something.
[19:15:12] <yaron>	 It's been a while since I looked into any of that code.
[19:23:20] <TheWoozle>	 Hmm... let me check the class docs and see if that looks promising...
[19:24:18] <TheWoozle>	 Yes. Yes it does.
[19:25:08] <yaron>	 Cool.
[19:25:19] <TheWoozle>	 I'm liking the schema and class API for 1.9 a lot better than those in 1.7, by the way. They make a lot more sense.
[19:27:01] <yaron>	 Well, I wasn't involved in creating them - I only use them - but I agree with you.
[19:30:59] <gerrit-wm>	 New review: Yaron Koren; "Patch Set 2:" [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/48734
[19:44:30] <gerrit-wm>	 New patchset: Foxtrott; "parameter "new window" for formlink and queryformlink" [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/48734
[19:52:14] <gerrit-wm>	 New review: Yaron Koren; "Patch Set 3: Verified+2 Code-Review+2" [mediawiki/extensions/SemanticForms] (master); V: 2 C: 2;  - https://gerrit.wikimedia.org/r/48734
[19:52:15] <gerrit-wm>	 Change merged: Yaron Koren; [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/48734
[20:43:53] <gerrit-wm>	 New patchset: Yaron Koren; "Fixed handling of dollar signs in values in multiple-instance templates" [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/49155
[20:44:26] <gerrit-wm>	 New review: Yaron Koren; "Patch Set 1: Verified+2 Code-Review+2" [mediawiki/extensions/SemanticForms] (master); V: 2 C: 2;  - https://gerrit.wikimedia.org/r/49155
[20:44:27] <gerrit-wm>	 Change merged: Yaron Koren; [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/49155
[21:13:41] <Frank_>	 Has anyone here tried implementing a semantic map (or even just a map in a wiki) with custom tiles?
[21:14:23] <Frank_>	 I have a wiki that will be isolated from the Internet and I was going to try and give it a basic map.
[21:21:28] <zUriel_>	 After upgrading from 1.7 to 1.8, property values containing a "=" character fail to display. Did someone else had this issue ?
[22:27:04] <gerrit-wm>	 New patchset: Yaron Koren; "Added compatibility with new ContentHandler approach in MW 1.21" [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/49176
[22:28:05] <gerrit-wm>	 New review: Yaron Koren; "Patch Set 1: Verified+2 Code-Review+2" [mediawiki/extensions/SemanticForms] (master); V: 2 C: 2;  - https://gerrit.wikimedia.org/r/49176
[22:28:05] <gerrit-wm>	 Change merged: Yaron Koren; [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/49176