LDD Show Reponses

LDD Show Reponses插件简介

LDD Show Reponses插件描述

This used to be a Greasemonkey script designed to be used with the fums on the Notes.net/LDD/Lotus developerWks site. ( http://www.lotus.com/ldd )

This has since been rewked into a Chrome extension.

If you have no idea what Greasemonkey used to be, start here:

Firefox users (the iginal):
http://greasemonkey.mozdev.g/

IE users (the copy):
http://www.daishar.com/blog/archives/2005/03/greasemonkey_fo.html

Ive only tested this script with Firefox, so I have no idea how well it
does  doesnt wk with IE.

===========================

The problem with the LDD fums is that you cant see the text of any of the
responses associated with a particular message. You get a list of links to the
responses at the bottom of the page, but you can only open a single message at
a time  which is a huge pain if there are me than about 2 responses to a
message.

What this script does (thanks to the magic of Greasemonkey) is to add a little
[+] next to each response link at the bottom of the page. If you click on that
[+], it will open a 
 beneath the link that will get populated with the
message body f that particular response. Click it again,  the response
body disappears.

As of version 1.3 of the script, the [+] is added on any LDD page that has an
?OpenDocument link, not just a message. So the script wks when youre viewing
a message,  the main view of a fum,  even a list of search results.

If none of this makes sense, just go to: http://www10.lotus.com/ldd/nd6fum.nsf
 open a message that has several responses,  then try to read the responses
with  without this script enabled.

===========================

A few efficiencies Ive added to this script:

1. None of the response messages are retrieved until you actually click the [+].
This means when you view a message that has a large number of responses, your
page will still load quickly (i.e.  the browser wont be trying to get all
of the responses when the page opens). The text of the responses is only
retrieved when you click the [+].

2. If you click on a [+] to view a response message  then click it again to
make it disappear, it will remember what the message is. So if you click it
again to exp the response message befe you refresh the page, you wont
have to make another round trip to the server in der to get the message
again  itll just come right up.

3. The responses are retrieved using asynchronous XML HTTP requests, which grab
the response doc, parse the message text,  insert it into a 
 (this
process is nmally referred to as "Ajax" these days).

===========================

ISSUES:

1. I had to hardcode several things in here, because the LDD fums dont really
package up the messages in any kind of easily parsable way (say, with divs).
Some  all of this script could break tomrow if the LDD folks decide to rename
some of their image files.

2. Theres probably a much me elegant way of doing some  all of this using
regular expressions. I dont know how that way might wk,  I dont really care.
This method seems to wk,  its easy to troubleshoot.

3. There may be a few links on the page that get the [+] appended to them that
get an "Err finding beginning of body" message when you try to exp them (like
the FAQ link). This is because the links dont actually point to messages, but other
pages that dont parse like a message will. I thought about adding some code that
explicitly ignes these kinds of links, but all of the exclusions would just
muddy up the code,  Id probably have to keep adding new ones. So rather than
try to account f all the exceptions, Im going to assume that my users are smart
enough not to wry about those sts of things. (UPDATE: in version 1.4 I added the
igneList array to deal with at least some of these s.)

===========================

HISTORY:

version 1.0  April 16, 2005
Initial release.

version 1.1  April 16, 2005
Fixed bug where the  tag I was using to determine the start of the body
block didnt exist when you were logged in, so you wouldnt get message text
if you were logged in.

version 1.2  April 17, 2005
Modified the script to make the display div block style "display: none;" when the
div was hidden, to get rid of the extra whitespace/linefeed that was appearing
 each of the response links.

version 1.3  April 19, 2005
Changed the script to run against any ?OpenDocument link, not just the response
links that were found at the bottom of a message. This way it will wk not only
on message pages, but also on views  search results. Unftunately, this also
puts a [+] next to some links that wont exp properly (like the fum FAQ links
at the right of the page). I thought about filtering those links out manually,
but its probably better to have a few links that dont wk right rather than
hardcoding several exceptions in this code (theres too much hardcoding as it is).

Also made a small change to account f a different separat graphic on the
ND7 fums,  made the [+] change to [] when its "exped".

version 1.4  May 10, 2005
Added the igneList array ( relevant igneList processing), so we wont
process links that we know will not wk. Thanks to Christopher Byrne
(http://controlscaddy.com) f the suggestion  an example of what to igne.

version 1.5  August 14, 2005
Added the endOfBody array ( relevant processing) to account f multiple
possible endings of the body part of the fum message. The fums were slightly
redesigned in late July/early August,  they started using a different graphic
at the end of the body. With the new array, itll be easier to add new endofbody
conditions in the future.

version 1.6  December 3, 2005
LDDMonkey stopped wking when Firefox got upgraded to 1.5. Kurt Higley
(http://www.higs.net) fixed it within a day! His changes included:

* exper.onclick = ... changed to exper.addEventListener(click, ...)
* calls to XMLHttpRequest changed to GM_xmlhttpRequest
* restructure getResponseText() function to split it out a little better

I made a few changes to the URL processing, but otherwise included the changes
asis. Thanks Kurt!

I also added "https://*.lotus.com/ldd*" to the @include list f when youre
logged in to the fum,  made it possible f the script to try to reload
a response message if an earlier attempt never returned anything (which seems
to happen at times).

Tested with Firefox 1.0.7/Greasemonkey 0.5.1  Firefox 1.5/Greasemonkey 0.6.4

version 1.7  July 18, 2006, Peter LaComb
1: At the end of getXMLText, just befe inserting the body into the DIV I added this line:
bodyText = bodyText.replace(/]*>/g,"");
This removes all the annoying blank boxes that show up.

2: Updated so that when used in a view, it will retrieve the response list,
 allow you to exp the responses.

version 1.8  September 16, 2010, Lars BerntropBos
Added 1.7 version histy  fmatted code.  Submitted to Julian f publication on OpenNTF

===========================

This is version 1.8 of the lddresponse.user.js script
by Lars BerntropBos ( http://www.nsftools.com )
June 3, 2014

You can do anything youd like with this script, just dont hold me liable f
anything,  dont pretend like you wrote it yourself.

The latest release should always be available at the OpenNTF site, at:
http://www.OpenNTF.g/projects/pmt.nsf/ProjectLookup/LDDMonkey
                                

LDD Show Reponses插件离线安装方法

1.首先用户点击谷歌浏览器右上角的自定义及控制按钮，在下拉框中选择设置。

2.在打开的谷歌浏览器的扩展管理器最左侧选择扩展程序或直接输入：chrome://extensions/

3.找到自己已经下载好的Chrome离线安装文件xxx.crx，然后将其从资源管理器中拖动到Chrome的扩展管理界面中，这时候用户会发现在扩展管理器的中央部分中会多出一个”拖动以安装“的插件按钮。

4.下载 LDD Show ReponsesChrome插件v2.0版本到本地。

5.勾选开发者模式，点击加载已解压的扩展程序，将文件夹选择即可安装插件。

注意：最新版本的chrome浏览器直接拖放安装时会出现“程序包无效CRX-HEADER-INVALID”的报错信息，参照这篇文章即可解决