[00:00:12] Superpig, yeah the mediawiki feature submission is apparently their bug report system. Kind of confusing. [00:00:45] ah. I was hoping to find an existing way of implementing it, actually, rather than logging a feature request... but oh well [00:01:04] as far as selecting certain glossaries goes, it would be neater if instead of checkboxes it just used the categories a page was in [00:01:38] i.e. if I could get a glossary for the 'Graphics Programming' category, that was a glossary page produced from all pages that define the [glossary] template that are in Category:Graphics Programming [00:01:40] sort of thing [00:02:43] Superpig, yeah this might be more of an extension than an edit since mediawiki can use extensions [00:02:55] ree hee heeally? [00:04:30] http://www.mediawiki.org/wiki/Extension:Glossary [00:04:31] would be a nice extension to regular wiki links, actually - when you mouse over a link to another wiki page, if that page has a glossary entry attached, it pops up in a little box, saving you from having to click on the link and read a full article [00:04:51] yeah, I'm just looking at that. It does the auto-linking part but not the 'generating a glossary from a sparse set of pages' thing [00:05:14] Superpig, Lupin's popups generate a popup of the first paragraph or so of the page, with various buttons too. [00:05:38] heh [00:05:43] that's close to what we want, I think - we'd just like to use something that is explicitly marked as 'glossary definition' or something similar, rather than just the first paragraph [00:05:44] you could also do it as a template like... [00:05:50] {{glossary|term}} [00:06:01] yep, I figure it would be something like that on each page [00:06:09] which would generate [[term|term]] [00:06:24] poorman's popup [00:06:29] oh - oh, no, that's not really what I mean [00:06:43] but no javascript or ajax required for that [00:07:18] an extension that processes wikilinks in a page to annotate them definitions somehow isn't the hard bit - it's building the glossary data in the first place that's the hard bit [00:07:41] Splarka: I prefer title=pagename&action=something, what can you advice me? [00:07:43] <[Hyarion]> Hi, I was wondering if there is anyway to change which skin is displayed depending on the browser [00:08:22] Gali: well, what would you need it to do? edit the page? just show info about the page? show changable data about the page that wouldn't be stored in the page's text? [00:08:27] being able to put {{glossary|name=AABB|description=Axis-aligned Bounding Box. A rectangle or box with the restriction that its sides or faces are parallel to the axes of the system}} on the page about AABBs [00:09:06] then (1) have that name and description show up in the 'glossary' page, and (2) have that description pop up when I mouse over a link to 'AABB' on other wiki pages [00:09:31] Superpig: well, there is a method that would only need a bit of JS and ParserFunctions, but would not be infinitely scaleable [00:09:47] Splarka: show changable data about the page that wouldn't be stored in the page's text. [00:10:02] can you add like tag events and govern how they are processed? I mean a separate table could be made and managed when they are deleted and stuff but this sounds like just making an extension from scratch. [00:10:22] Splarka: are you thinking of something that catches the page when it's saved and updates the glossary page accordingly, or something? [00:10:32] lemme splain [00:10:34] I was hoping for something more like how the Category system works [00:10:36] in a normal page: {{glossary|term}} [00:10:45] on Project:glossary {{glossary|all}} [00:10:49] and in Template:Glossary: [00:11:26] {{#switch:{{{1}}}|all|RAM=Random access memory}} [00:11:33] {{#switch:{{{1}}}|all|ROM=Read only memory}} [00:11:34] etc [00:11:51] all the definitions would be inside the template, so only one place to edit [00:11:56] hmm, aye [00:12:00] and you'd be able to call one at a time, or all [00:12:06] that's what I'm trying to avoid, unfortunately [00:12:09] yah [00:12:36] I want the term names and definitions to be on the full page about them - i.e. "ROM = Read Only Memory" should be on the page that has the full article about ROM [00:12:39] (and you'd spruce it up to hide the text except on the project page) [00:12:52] well [00:12:57] Splarka: i am working on specific extenion for mediawiki whic allow directly create map for article and data will be stored in SQL , which allows searching articles via map. [00:13:19] Gali: sounds complex, maybe search mediawiki.org for similar extensions [00:13:33] Superpig: hmm, I have an idea.. [00:14:18] Splarka: i am doing it as bachelor work :). So i am pretty sure, that something like i told is not avalaible. [00:15:10] Splarka: there are a lot of extension using maps. but not of them enables searching via maps.. (they stores data in wiki text.. or something like that) [00:16:04] yah, that sounds like something that might be better as a separate database than the mediawiki install even [00:16:50] Splarka: that was adressed to me? [00:18:11] How can I make logins go over https, instead of http? [00:18:15] gali: yes [00:18:19] Splarka: i dont want to do it as separate database.. i want to integrate to wiki sql structure with one key to page_id. [00:18:51] logins over http is pretty much pointless security.. [00:20:07] Splarka: ok , but what hooks should i look at. What do you advice me for that ? [00:21:53] Gali: well, I'd guess it'd be better to use a Special page, and any hook that modifies the portlets should be fine (unless you want to make the button hidden/dynamic certain conditions), but I can't help ya with the db X_X [00:26:26] Splarka: yes, i understand. And with hidding button , I was thinking if is needed to have hidden in special cases. And result is that it could be good. I found some strange situation as when user create new article ( then in this state) no pageid exist.. so i will need to allow working with map only for articles which exist. [00:27:53] Gali: will this be required to work in non-monobook skins? [00:28:04] like cologneblue, nostaliga, etc [00:29:05] i think thats is not important, default template is good and nothing else to consider. [00:32:24] Splarka: in which timezone are you? [00:32:55] PDT [00:34:10] Gali: http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/examples/Content_action.php?view=markup this one might be what you want (an example) [00:34:36] Splarka: seems to be what can help :) [00:36:08] Splarka: i am feeling bad for my english ... thx very much for your support. [00:36:37] np [00:37:22] i am going to sleep, heh 2::37 yet.. bye all. [00:39:22] ciao [00:40:27] *Sasoriza thinks sleep sounds good [00:47:46] 03(NEW) Zh traditional/ simplified conversion for NON rendered HTML too - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=13840 15enhancement; normal; MediaWiki: Internationalization; (jidanni) [01:36:41] 03aaron * r33877 10/trunk/phase3/includes/LogPage.php: -1 is bad too [01:52:19] how you guys think about lmplayer? [03:18:53] hey is anyone here? i have a question regarding the api [03:19:07] how does one workaround the cross-domain restrictions? [03:20:02] the ajax restrictions? [03:20:24] this is for a javascript? [03:21:09] Waldir: you can use the &callback parameter with format=json [03:21:24] and then, instead of an xmlhttprequest, you make it the src of a