[Zope] zope backtalk product - some questioons

David Hassalevris bluepaul@earthlink.net
Sun, 13 Jul 2003 18:49:47 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_001F_01C3496F.88B051C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

So I liked the Zope Book and decided to take a look at the product =
"backtalk" - which implements structured text into a collaborative =
framework.

I am stuck with a few things and wonder if anyone can help.

1) Essentially backtalk provides two new selectable objects into Zope:  =
Backtalk Book and Backtalk Documents.
The backtalk book is folderish.  When backtalk documents are added they =
automatically appear as members of the table of contents.
My idea is to link each table of contents item to a folder. =20

The problem is when I create a new folder within the backtalk book =
object and add a back talk document into that subfolder ... the =
navigational arrows disapper.  Its as if the backtalk book has "lost =
track" of documents in subfolders.
How is this done?

2)  I notice that the backtalk book object sorts it's table of contents =
by title (if no title then by id).  But who wants a table of contents in =
apha order.  There obviously is a work around to this.  I just dont know =
it.
Anyone?

BTW, from what i've seen so far its a very nice product!  I *think* the =
Zopebook was authorized using it.

David

------=_NextPart_000_001F_01C3496F.88B051C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>So I liked the Zope Book and decided to =
take a look=20
at the product "backtalk" - which implements structured text into a=20
collaborative framework.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am stuck with a few things and wonder =
if anyone=20
can help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>1) Essentially backtalk provides =
two&nbsp;new=20
selectable objects into Zope:&nbsp; Backtalk Book and Backtalk=20
Documents.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The backtalk book is =
folderish.&nbsp;&nbsp;When=20
backtalk documents are added they automatically appear as members of the =
table=20
of contents.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>My idea is to link each table of =
contents item to a=20
folder.&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The problem is when I create a new =
folder within=20
the backtalk book object and add a back talk document into that=20
subfolder&nbsp;... the navigational arrows disapper.&nbsp; Its as if the =

backtalk book has "lost track" of documents in subfolders.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>How is this done?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>2)&nbsp; I notice that the backtalk =
book object=20
sorts it's table of contents by title (if no title then by id).&nbsp; =
But who=20
wants a table of contents in apha order.&nbsp; There obviously is a work =
around=20
to this.&nbsp; I just dont know it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Anyone?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>BTW, from what i've seen so far its a =
very nice=20
product!&nbsp; I *think* the Zopebook was authorized using =
it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>David</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_001F_01C3496F.88B051C0--