User talk:Danwe

Hi Danwe -- saw your question in IRC but by the time I saw it you had left. I think this is what you're looking for: http://www.mediawiki.org/wiki/Manual:Tag_extensions#How_do_I_render_wikitext_in_my_extension.3F -- openbip


 * Thank you. But for some reason this won't work always. For example I try to execute a template with it and after adding/removing parameters or perhaps depending on the result it returns a void string instead of the templates value. Exactly the same template call above or after the function call returns the expected value... --Danwe 20:28, 28 January 2010 (UTC)

Subpage Fun feedback
Hi Daniel,

Subpage Fun is a very useful extension as I'm using lots of subpages in part of my wiki. I've been using Extension:SubPageList but its features are quite limited. And DPL is of no use when dealing with subpages. I would like to see some features of Extension:SubPageFunctions in your extension, though, especially a feature to trim path names. Cheers, Frank --Nakohdo 20:02, 26 January 2011 (UTC)


 * You already have half the functionality of that function in Subpage Fun:  will return you the last 4 parts of the path for example. If you want some middle parts you could use #sub and #pos functions of Extension:StringFunctions and then #replace   with  . I don't like overloading the extension with all kind of parser functions for each possible use case. You can do a lot with other parser functions. Also RegexParserFunctions or Extension:ArrayExtension would do the trick very easily. Best you define a template for it. On the other hand, another parameter length and the possibility of a negative offset for   wouldn't harm either. If I have some time I might realize it. --Danwe 02:25, 27 January 2011 (UTC)
 * ^^ no, sorry, this doesn't really work. So I will think of something else, perhaps a  function. On the other hand, ArrayExtension would still do it. You would have to walk trough the array in the end and output it with:   --Danwe 02:44, 27 January 2011 (UTC)


 * Ok, see Extension talk:Subpage Fun for a final solution. --Danwe 03:38, 27 January 2011 (UTC)

Slowness using HashTables
Hi! I'm experiencing slowness using HashTables extension to produce a manual index.

My aim is to use a certain user-editable index page as a base for a navtree, a frontpage and for another template to get to know the pages position in the index. Please see Chapter, Section, Index and NavTree (currently commented out for poor performances).

From my current experience, mediawiki doesn't cache the result of the hash table after the first time I see the result of a certain template, hence each time I visit the index and pages where I have the navtree (which is built using hash tables), the index or the navtree are re-calculated :/

Is there a way to tell the parser to cache the results of templates using this extension?

Can you help me to shed some light on this? Thanks in advance! --Mindrones 20:21, 10 July 2011 (UTC)


 * Template results are normally getting cached when the template is called without any params like  but as soon as you have one param it won't get cached anymore:   is enough for not getting cached. Actually, it's dangerous to cache a template which uses hashes, arrays or simple variables (Extension:VariablesExtension). This is because all variables are global, so when you change variables outside the template and then call the template again, you wouldn't get the expected output considering you just changed the variable. So be careful. If you don't intend to modify variables from outside the template caching the result would be fine so create a template which doesn't require any parameters and as long as you don't change your wikis default caching behavior it should get cached. --Danwe 23:35, 11 July 2011 (UTC)


 * Many thanks for the reply! Do you have any suggestions to speed up this system I have made? I wasn't expecting that managing that amount of links would have been so slow :( I'm currently experimenting with but it makes my templates overly complicated to maintain. Thanks, Mindrones 11:14, 16 July 2011 (UTC)

SRF and Array Result Format
Since the code of Array Result Format is shipping out now with SRF, maybe you could make a documentation about how to used it and give some examples. If you have trouble getting the documentation updated, contact. --MWJames 17:14, 9 November 2011 (UTC)


 * Actually, I wrote a documentation a while ago. I put a description of the formats on the SRF main page as well. I'll look into putting the documentation on semantic-mediawiki.org as well. --Danwe 16:02, 10 November 2011 (UTC)


 * Heiya, I just moved the documentation over to semantic-mediawiki.org. Thus I would like to invite you over too. I will provide you with the contributor rights as soon as you arrived. Cheers and see you there --&#91;&#91;kgh&#93;&#93; 22:03, 11 November 2011 (UTC)

Extra download packages for your extensions
Hi Daniel, it would perhaps be advisabel to provide an extra download for each version you create like it is done for most of the SMW extensions. The extension distributor is not very good then it comes to strictly versionised software. Users have otherwise no chance to retrieve the exact revision of the software. Cheers --&#91;&#91;kgh&#93;&#93; 15:31, 22 November 2011 (UTC)


 * I've been thinking about this for some time, just haven't had the time to set it up by now. I just wonder whether there will be a better extension distributor after we switch from svn to git? In that case I would probably keep waiting. --Danwe 19:13, 24 November 2011 (UTC)


 * Well, I do not know but I do not really believe it will be better then. Anyway the switch to git will probably take more time than expected so we should not hold our breath until this is done. ;) However, one advantage of an extra download is, that you get a better idea of how often an extension gets downloaded and is used. Cheers --&#91;&#91;kgh&#93;&#93; 19:28, 24 November 2011 (UTC)


 * Alright, I guess I am convinced, I'll look into it soon. --Danwe 19:38, 24 November 2011 (UTC)