Extension talk:Wiklets

Trying to get this to work on my site but I can't get the path right to the .js location. I dropped dragiframe.js in /extensions along with Wiklets.php. I changed permissions to 755 on the .js as well. Also added these lines to localsettings.php

include("$IP/extensions/Wiklets.php"); $wgWikletsLoadJS = "/extensions/dragiframe.js";

Would you mind steering me in the right direction?
 * All your js etc is loaded ok, it seems that currently it can't work with external urls, and has to be a local wiki article - I edited you test page and it's working, but a bit shakey - also you need to set up a minimal css for wiklets - ours is wiklets.css and set that css in $wgWikletsUseCss. This extension hasn't been developed in a year or so and is very experimental currently. --Nad 17:39, 7 September 2007 (NZST)


 * Got it. Thanks for the quick response!
 * Sorry to bother you again, but would I put the call to the .css file in localsettings.php? I added
 * $wgWikletsUseCss = "/skins/monobook/main.css";
 * to test, but it's not being seen...

Sorry, the name of the variable should be $wgWikletsUseCSS (capitals for CSS), you can refer to a file, or create one in-wiki, for example, our LocalSettings line is: $wgWikletsUseCSS = '/wiki/index.php?title=Wiklets.css&action=raw&smaxage=0&ctype=css'; This reads the raw wiki-text version of an article with no caching and sets its MIME type to CSS. I don't think the main CSS is good for wiklets because it may affect layout incorrectly, but I can't quite remember. --Nad 09:30, 8 September 2007 (NZST)


 * Thanks Nad, that did the trick :)
 * Yeah that's looking much better ;-) I think it would work much more smoothly using draggable div's rather than iFrames and my favourite javascript framework, Mootools, has that capability now so I'll look into making some more progress with the wiklets and let you know if any news. --Nad 12:32, 8 September 2007 (NZST)

iframe not movable
Hi Nad...

I'm also trying to get your extension working on my wiki. But unfortunately the iframe isn't movable as soon as I save the article. It's a little bit curious, but in the preview-mode it's possible to move the frame!?! Any idea?
 * You could try loading the javascript unconditionally, it might not be getting loaded under some circumstances. --Nad 21:28, 6 October 2007 (UTC)
 * Thanks for the quick response. Actually I don't really know how to load the js unconditionally. Maybe you can give me a little advice...

Me too
Hi Nad: I have the same problem. My test page is at " http://studwww.nou.edu.tw/~e-live/testwiki/index.php/Wiklets_test". Please tell me the way to solve it. I'v set to watch this page. If you leave any message here, I would know.--Roc michael 13:29, 11 October 2007 (UTC)
 * I think it would be best not t use wiklets unless you're a developer for now because the iFrames way doesn't work very well. It will be much better when changed to draggable div elements, but I won't have time to work on this one for a while as I've got a lot to do on simpleforms, simplesecurity, livelets and treeview. --Nad 20:18, 11 October 2007 (UTC)
 * Nad: thank for your replly and the thing I expect most is the publish of workflow extension. :-) --Roc michael 15:10, 16 October 2007 (UTC)

Unstable?
Hi Nad, could you please tell me, what exactly is unstable with this extension? I am using it at the moment, and it works fine so far!?!

greets --194.76.239.11 14:01, 30 October 2007 (UTC)
 * My plan was to use draggable div elements, but I became too busy with other work and extensions to complete it, so I just added iFrames as a temporary measure to test it. On our wiki the iFrames were very shaky and seem to work perform differently across browsers. I'm glad you're having some success with it :) --Nad 21:02, 30 October 2007 (UTC)


 * Like I told you the extension worked fine on 1.7.1. Now I've tried to make it work on 1.11.0. I use the extension to load some kind of TOC into the iFrame, and if I choose a link the appropriate article should be loaded in the content-area. Now, under 1.11.0 the article is shown directly in the iFrame. Any idea what's the reason?