Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Zope: Web

Re: [Zope] user contributions to Zope.org

 

 

Zope web RSS feed   Index | Next | Previous | View Threaded


klm at digicool

Jun 9, 2000, 5:30 PM

Post #1 of 4 (581 views)
Permalink
Re: [Zope] user contributions to Zope.org

[.As per ethan's request, i'm following up to zope-web, and set the
reply-to to zope-web, so the conversation continues there.]

Graham Chiu wrote:

> This has been mentioned before, but some sites like the main PHP one
> allow visitors to add comments to web pages.
>
> My thought was that this should be relatively easy to implement with the
> Zope.org site. A small form at the bottom of each page, URL0 indexed in
> a SQL table, and when a page is accessed, commentary is returned ordered
> by submission date.
>
> You may wish to allow only members rather visitors to make comments.
>
> Anything wrong with this scenario ( apart from comments not being
> Catalogued ) ?

I think this is a great idea - i think being able to put the right
things in just the right places is critical for scalable
collaboration, and often the right place for comments and dialogues
about a page are attached to the page.

The hard part in achieving this, to me, is arranging for reasonably
organization of the commentary - so it doesn't clutter the original
page, and so the accumulation has some kind of useful internal
relationships. I don't think that's been adequately solved, yet.

Weblogs provide some organizational features - threading, moderation
filters, etc - but they still wind up being way too haphazard for my
tastes. (I, for one, hardly ever find slashdot discussions to be
worth much, despite careful exercise of moderation thresholds.)

I think wikis' easy editing, linkability, etc, along with my nesting
additions, may provide a basis for something better - but there would
need to be some mroe imposition of structuring. Just reediting other
peoples stuff, even with the best of intentions *and* version history
for differencing, is too haphazard.

I just saw something very cool from ka-ping yee (a really smart python
guy) for external annotation of web pages:

http://crit.org/

that may be the kind of thing we'd need. I imagine an addition to
structured text, and dtml, for explicit annotation markup:

- structured text could have stuff like

[+annotation text>content text<+]

- which yields dtml like:

<dtml-note support>annotation text<dtml-content>content text</dtml-note>

which yields markup like:

<a href="annotations/commentx">
<img alt="[support] klm: annotation text"
src="link-l-b.gif"></a
>content text<a href="annotations/commentx"
><img alt="![support] klm: annotation text"
src="link-r-b.gif" width="9">

(where the images are little annotation begin/end arrow glyphs).

The idea is that the alt-text conveys the contents of the comments,
with the glyphs indicating the class - comment, support, concern,
question, etc. The annotations/commentx would be a document in its
own right - wiki-like - where discussion of the annotation - with it's
*own* annotations - could grow.

And for implicit annotation, with annotation separate from the target
text zope text documents (dtml methods and documents, wiki pages,
other derivatives) would all provide annotation features similar to
what the crit.org mediator site does, but without requiring the separate
mediator site...

(I don't know how many of you are familiar with talmudic scholarship,
or marginalia in ancient chinese medicine, eg [...quick google
search...] the yellow emporer's Nei Jing - both texts have layers and
layers of crucial commentary, gradually retained and accumulated
across millenia. The trick, in this modern age, will be in getting
more, um, immediate, self-organization....)

Ken Manheimer
klm [at] digicool


gchiu at compkarori

Jun 9, 2000, 8:12 PM

Post #2 of 4 (532 views)
Permalink
Re: Re: [Zope] user contributions to Zope.org [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <14657.35848.477712.658130 [at] korak>, Ken Manheimer
<klm [at] digicool> writes
>search...] the yellow emporer's Nei Jing - both texts have layers and
>layers of crucial commentary, gradually retained and accumulated
>across millenia. The trick, in this modern age, will be in getting
>more, um, immediate, self-organization....)

Hmm. Can't find my copy of the Nei Jing anywhere, but as you say these
texts are heavily annotated.

How about another alternative - such as in Forth where they used shadow
screens for commentary on source code?

- --
Regards, Graham Chiu
gchiu<at>compkarori.co.nz
http://www.compkarori.co.nz/index.php
Powered by Interbase and Zope

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBOUEXV7TRdIWzaLpMEQLeGgCgsxwucZTBEfBWZHrBmDP0/xCVtOQAnR+9
p/8yvAUeQW3yvGqhwUNyQ65B
=xDEf
-----END PGP SIGNATURE-----


klm at digicool

Jun 10, 2000, 8:03 AM

Post #3 of 4 (547 views)
Permalink
Re: Re: [Zope] user contributions to Zope.org [In reply to]

On Sat, 10 Jun 2000, Graham Chiu wrote:

> How about another alternative - such as in Forth where they used shadow
> screens for commentary on source code?

I've not used forth - can you say more about what's done there?

(It *sounds* like having a separate screen which "projects" annotations
onto the text - which is what ka-ping's mediator architecture does...)

Ken
klm [at] digicool


gchiu at compkarori

Jun 10, 2000, 1:06 PM

Post #4 of 4 (546 views)
Permalink
Re: Re: [Zope] user contributions to Zope.org [In reply to]

In message <Pine.LNX.4.21.0006101101270.14801-100000 [at] korak>
, Ken Manheimer <klm [at] digicool> writes
>On Sat, 10 Jun 2000, Graham Chiu wrote:
>
>> How about another alternative - such as in Forth where they used shadow
>> screens for commentary on source code?
>
>I've not used forth - can you say more about what's done there?
>
>(It *sounds* like having a separate screen which "projects" annotations
>onto the text - which is what ka-ping's mediator architecture does...)
>

Well, my recollection is not that clear but here goes.

In the olden days Forth used 1024 byte pages directly mapped to the
storage medium which were called screens. You then got from that 16
lines of about 64 chars to write your code. Forth words were encouraged
to be small, and fit into one screen. For many reasons, Forth became
very hard to read, and so shadow blocks were invented where each page of
source code was associated with a screen of commentary.

This idea fell into disuse as file mapped source code became more
popular, and Forth's reputation as a write only computer language grew!
Dare I say this shares some parallels with Zope <g>

But I would imagine that one could reserve an extension so that each
HTML page could be mapped to a commentary page.


This is taken from a google search

http://dec.bournemouth.ac.uk/staff/pknaggs/papers/literate.html

4.1. The Forth Block
In Appendix A we see the code as a traditional Forth screen, or block.
The first line is an index line, used to give a general title to the
block. The index line has lead to the practice of collecting together
related definitions into the same block or sequence of blocks. In this
example we have gathered together the definitions relating to the memory
management of the application. Thus making it easy to find and
concentrate on for debugging purposes.
The text on the right of the index line is an indication of last time
the block was modified (10-May-1990) and by whom (PjK). This is placed
on the block automatically by the Forth++ editor and is useful for
maintenance and project management reasons.

One of the drawbacks of using blocks is that the space is limited and
one is tempted to shoehorn the code and not document it. For this reason
the "shadow" block was developed to allow documentation of the code
presented in the associated block (as shown in the example). Normally
the two blocks are printed side by side, thus making it obvious which
code is referred to in the shadow (or "comment") block. The shadow block
provides us with an extremely useful documentation technique, yet it is
suprising how many seasoned Forth programmers do not bother with the
shadow block, thus increasing the difficulty of maintenance.


--
Regards, Graham Chiu

Zope web RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.