create new tag
, view all tags

LiveLink Skin

Against my TWiki wishes, and the ways of the Wiki:WikiMasters, but here it is...

LiveLink is beginning to proliferate throughout Sun, but my group still requires the features TWiki has to offer. In order to remain in the spirit of TWiki, but be compatible from a user interface standpoint, I'd like to look into what features would need to be added to TWiki to look and feel like LiveLink.


Opening Thoughts:

It's going to suck (the effort, I mean), but it'll be worth it in the end, from a UI training standpoint.

To start with, we'd need...

  • a good skin that looks and feels like LiveLink (a well polished one)
  • we'd need to define a few more variables, Meta data, functions via the Plugin interface
  • scripts for doing LiveLink-ish things, like add/remove/rename/move folders/webs.
  • These features would help to automate the conception of hierarchical webs (folders in this case) feature folks have been talking about.

I've also found that URL names are relatively unimportant to these folks;

  • They just navigate using the UI/Skin, therefore ugly topic names are not an issue.
  • They're probably not going need to edit any topics directly, and probably won't understand (without being hit over the head with it) the concept of WikiName linking.

Discussion forums:

LiveLink provides threaded discussion forums.

LiveLink's discussion forums also allow for free-form topic names:

  • We could probably get around that by using some sort of discussion forum plugin that maps a free-form discussion topic description to a wikiname of our choosing, such as DiscussionTopic98798734 (ugh!), or some slick derivation that still looks like english.

LiveLink's discussion forums allow you to show read v.s. unread topics:

  • I'm sure we could track a user's reading habits via cookies, dbm, etc. It's just a matter
of speedily translating that into a list that shows/hides it's various list items based on that information.


TWiki, with all it's wizzy cool features, skins, and plugins is somewhat slow, believe it or not, compared to LiveLink. Because it is interpreted, opens lots of files, parses lots of files, does lots of data munging,etc. It needs to be faster, and I don't necessarily care what the implementation looks like, as long as we get all the same cool wizzy features we currently have access to. Maybe we need a TWikiSOAPServer!

-- PeterNixon - 08 Nov 2001

For an easy speedup of TWiki, have a look at ModPerl - some comments indicate quite a dramatic improvement, but YMMV of course! No code changes are needed, so it's a lot easier than using SOAP.

-- RichardDonkin - 08 Nov 2001

Would be good to have a way to refresh the caches though, we tested PerlEx and found that we really needed to tell it to refresh its idea of current files.

-- MartinCleaver - 08 Nov 2001

I just found a cool extension for perl that speeds up TWiki immensely (for me), without mod_perl, called SpeedyCGI. I've had no trouble with it so far, so I don't think I'll have to go off and implement a TWikiSOAPServer.

-- PeterNixon - 10 Nov 2001

I've moved on to mod_perl (sigh of relief), now that mod_auth_ldap seems to be working o.k., and written a nice substitute for livelink called MegaTWiki. People seem to be a little more comfortable with it...

-- PeterNixon - 25 Jun 2002

I happened to come across LiveLink the other week and had a look at its description. One feature I noticed was 'Copy'. Don't know what it exactly does with Livelink, but I can think of a use for TWiki:

  • In some zones, err, webs users tend to use the same outline of topics, that is use the same sequence and names of headings.
  • At the moment, they have to go through edit/copy/cancel or view-raw/copy/back for the existing topic (in the sense of a template) and subsequent create/paste to use the outline.

=What our people would like to have is:

  • go to topic containing the outline
  • choose copy instead of edit; maybe more/copy would be acceptable
  • corresponding oops-topic opens
  • enter new name (maybe choose web, too)
  • page with newly created topic with the chosen outline opens

Even better: skip the oops-topic, have people enter the new name in the Go-box and provide a copy-link/button.

-- PatrickHansmeier - 20 Jan 2004

The KoalaSkin has a copy feature, please try it and see if this is what you expected: go to http://wikix.ilog.fr/wiki/bin/view/Test/WebHome and hit "new".

"New" will offer you to use the current topic (or another one) as the source for the copy.

This is done only from the skin, so it should be easy to add this to TWiki main distrib.

-- ColasNahaboo - 21 Jan 2004

Thanks! This is an enhanced version of what I had in mind. I will have a look at the templates of Koala and adapt it to suit our needs (and the adapted VoidSkin).

-- PatrickHansmeier - 22 Jan 2004

What about the other way, I have written a Proof of Concept Module for Livelink 9.1 that adds Wiki capabilities to Livelink. Written in Oscript it lets you build a Wiki under any Folder or other container in Livelink, the Wiki then can be searched as any other Livelink object and you can write links in the Wiki to other Livelink Objects.

-- MichaelOliverAZ - 26 Mar 2004

I'd be very interested if anyone's got ideas on how to implement a wiki capability within LiveLink. I've been a big wiki fan for years but my company recently installed a big LiveLink server. I'm trying to figure out ways to make it useful. I recently started thinking about how to make LL do wiki and it really doesn't seem that hard. As it is, the name Open Text Live Link strikes me as a mis-nomer -- the system gives you virtually no capability for actually linking together text documents, nor is it open in anyway. smile

-- RichMills - 20 Dec 2004

Edit | Attach | Watch | Print version | History: r12 < r11 < r10 < r9 < r8 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r12 - 2004-12-23 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.