pbwidget

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

There are over 30 functions in the Widget Library, and some of them may not work (or even have meaning) under PBwiki 2.0. For example, 'hideFooter' is now irrelevant, because there's no footer to hide. Which functions do you use now, and which ones do you want to see converted to PBwiki 2.0?

Here's a list of the existing functions, for reference:

Buttons
addButton
hideButton
renameButton
redirectButton

Controls
hideFooter
installToggle
renameSidebar
showCrumbs
addPILink

Table of Contents
collapsibleToc
pageToc
quickListPages
siteMap
toggleToc

Header
replaceWikiName
replacePageName
replaceDivider
replaceAllText
replaceWithBanner
shortenLongName
changeHTML

Informational
getPageName
inSB
loggedIn
pageCount

Miscellaneous
autoLogin
includePage
onDocLoad

Tags
cloud
editor
multisearch

ChunkyMonkey · Site Admin Joined: 21 Mar 2008 Posts: 10

We should get onDocLoad working right away, as it's vitally useful as a replacement for onLoad(). Beyond that, I also really want to fix up the ToC function. A lot.

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

Agreed. I was about to reply to a GS post about ToC not being a siteMap, and wondered: does 2.0 implement /links.php?

stephenfleming · Joined: 21 Mar 2008 Posts: 2

I agree that a lot of the more cosmetic parts of the widget library are either redundant or meaningless for 2.0. However, showCrumbs is incredibly useful to my users, isn't implemented in 2.0, and is visually "lightweight" enough to be cleanly integrated into 2.0's look-and-feel.

So -- one vote for showCrumbs!

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

Thanks. I will start with showCrumbs. Very Happy

ChunkyMonkey · Site Admin Joined: 21 Mar 2008 Posts: 10

links.php is present

seanmac · Joined: 25 Mar 2008 Posts: 4

Here is my half-penny's worth. Asteris beside the ones I currently use.

Buttons
*addButton - I'd still like this in 2.0
*hideButton
*renameButton
redirectButton

Controls
hideFooter -redundant
*installToggle - I'd still like this in 2.0
*renameSidebar - I'd still like this in 2.0
*showCrumbs - I'd still like this in 2.0
*addPILink - I'd still like this in 2.0

Table of Contents
*collapsibleToc - I'd still like this in 2.0
pageToc
quickListPages
siteMap
*toggleToc - I'd still like this in 2.0

Header
*replaceWikiName - I'd still like this in 2.0
replacePageName
replaceDivider
replaceAllText
* replaceWithBanner - I'd still like this in 2.0
*shortenLongName - I'd still like this in 2.0
*changeHTML - I'd still like this in 2.0

Informational
*getPageName - I'd still like this in 2.0
inSB
loggedIn
pageCount

Miscellaneous
autoLogin
includePage
*onDocLoad - I'd still like this in 2.0

*Tags
cloud
*editor - Tags are much better managed in 2.0 so this is probably redundant as well
multisearch

Seanmac

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

Thanks, John. That's exactly the kind of feedback we're looking for.

showCrumbs has been implemented; see the Widget2 wiki for an example.

seanmac · Joined: 25 Mar 2008 Posts: 4

Works lovely in FF but not in IE 7 I'm afraid. Good to have you back

Seanmac

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

OK, it works now in IE6, but something is still generating an error. And since IE sucks, I can't figure out what it is. Could you try it in IE7 and see what you get?

seanmac · Joined: 25 Mar 2008 Posts: 4

Works fine in IE 7 now! Excellent

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

It may not for long. They're pretty adamant about shutting Widget down for good.

vangispen · Joined: 26 Mar 2008 Posts: 6

Free workaround to put javascript and CSS code on ur wiki page:
use the Google Gadget or YouTube video plugin to insert ur bits!

On a 2.0 wiki I would like to make different javascript/CSS code work for different groups of users. For example: for readers and writers I would like to hide lots of stuff, for editors less and for administrators nothing.

In the past (1.0) I've used replaceWikiName, replacePageName (sparsely, for FrontPage) & getPageName (frequently) and stole some code to make my own scripts (mainly Button functions).

A question raised: would you mind explaining just how you control the display of items that have no unique ID?
Uh, I can't, except when they have a class, then I can control all of them at once. But what items are you thinking about, anyway?
And oh yeah, I'm looking too how to handle the "module:sidebar" etc. thing ...

BTW: hi all Very Happy

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

Welcome, vangispen! I was hoping you'd show up. Smile

We know about the Google trick, but we didn't want to say too much publicly, lest they decide to try and close the "hole".

I was mistakenly thinking that the folders, et al, didn't have an ID. But, as you point out, they do (module:folders).

I'll start looking into how we can determine what privs a given user has. In 1.0, I would look for page elements which render differently depending on user status. I don't what, if any, page elements render differently in 2.0.

They still haven't officially ruled out in-page JS, but we're working under the assumption that they will, so everything will have to be called from the HEAD (which means JS support will be premium only). I don't like that option, but if we exploit holes like Google gadget, they'll just close them. Turds.

We also use a 1.0 wiki for developing the code; since they are going to eventually force us to upgrade to 2.0, we'll have to switch to some other code base.

mbrutsch · Site Admin Joined: 21 Mar 2008 Posts: 17

Ah, I see you've already let the cat out of the bag about the Google/Youtube plugins. Oh well, we'll see what they do about it now!

My guess is they'll try to filter based on the contents of the <script> tags, but I'm sure we can work around whatever they do.