[ZDP] ZDP-Tools: Views

Maik.Röder roeder@berg.net
Tue, 25 Jan 2000 19:24:26 +0100


Hi !

Tom:
> I don't know, I think this be too much clicking...

You can make a view for the Book where you list all chapters
and subchapters. Next to the chapter is a link which takes 
you to the respective DraftSubmissionFolder. 

You may want to call this view WriterView in Book or
possibly in DraftSubmissionFolder.

Kamon:
> I agree with you Tom on "too much clicking problem".

It is just a View problem.

> We only want to reduce the steps to go to the latest update/draft. ie. When
> go as reader to a certain chapter, he/she must immediatelly see the latest
> update/draft.

Add a Reader_View_of_Latest_Drafts_Collector to the Chapter.

> And only has to click on the comments link to add comments.

You can also add a Local_Reader_Add_Comment_View behind each Draft
if it has a comment Folder.

> If the user wants to see previous drafts, he has to click on drafts to get
> into the drafts menu.
> 
> Thus we need to find a way to display the latest update/draft and the
> accompanied comments.
> 
> What do you all think?

Perhaps only the latest Draft should be shown fully and all other Drafts
that do not have NeedsReaders property set can be shown in the Earlier_Drafts_View.

kamon:
> Our ideas are some applications of the newly arrived Zope Portal Toolkit, I
> think. It would be interesting that someone who already looked at the PTK
> try a parallele/convergence between the PTK and the way ZDP works. This may
> also bring our project further in understanding Zope possibilities.

True. ZPTK is a real killer app.

Tom:
> mmm, I don't know anything about the PTK. Only what is been said a few
> months back. Yes, perhaps we can benefit of a merge. However until then -
> and this can be still a long time - we need to go further with what we have.
> We have already very good tools, made by Maik. They all do what we want and
> we only need to get that last thing done with ZBook. That is displaying the
> latest draft. If we can do this, we can publish our drafts and make an
> announcement of the rebirth of ZDP.

BTW: Displaying the latest Draft can also be copied from Latest_News.

> Then, while doing, members can look at PTK and maybe merge ZDP-Tools and
> PTK together. But at this moment I think it will only slow down ZDP once more.

We can use the ZPTK services once they are available. After all it is 
a _ToolKit_ and using it should be easy. 
 
kamon.ayeva@bureauveritas.com schrieb:
> document_status (or status): Needs review, Reviewed, or Accepted

Already there. Each DocumentFolder has NeedsReviewer property, NeedsWriter
and so on.
 
> draft_status: Previous, Current
> 
> When adding a draft, draft_status="Current".
> If there was an existing draft for the same chapter, this one is changed to
> draft_status="Previous".

The latest is the current and this should be it for the moment.
Anyway, we could also say that when NeedsReaders property is
off then this is an old draft.

> Not yet thought about displaying the comments related to the draft.

Comments can be shown like News ! Just look at ZDP-Tools News !
 
Tom:
> Hi Kamo,
> 
> I think this status isn't even needed. We can just look at the object with
> type draft and then look at its creation date... The latest draft is the
> one with the last creation date.

You already say it, Tom :-) 

kamon:
> OK.
> Maybe it's something like:
> 
> <dtml-in "objectValues(['drafts']) sort=creationdate>
> """show last document"""
> </dtml-in>
> 
> Anyway, I hope someone else or Maik will give us the answer today.

In a hurry, but anyway ;-)

Tom:
> Ok, I modified the ShowLists of Book/Part/Chapter, since the nickname is
> used as part/chapter -number indicator we could aswell sort on this and
> show the part/chapters accordingly.

There are going to be problems later if we don't pay attention here. A
subchapter should not have a nickname of I.1.1.1, or to say it differently:
A Program should not rely on this for sorting of subchapters. Ultimately
we need a Subchapter with the nickname 1, and all other chapters names
above it are aquired, which is really cool. :-)
 
> However, I would like to implement the stuff Kamon and I discussed today.
> But, I've some problems. Again, sorry.
> 
> I need to have this scheme
> 
> IF a DRAFT OBJECT exists then
> 
> {
> 
>  Show latest added DRAFT
> 
> }
> 
> ELIF
> 
> {
>   Show Part/chapter names (ie like we have now, thus this is done)
> }
> 
> Can somebody help me here? Maik, is this possible?


<dtml-in "objectValues(['Draft'])" reverse>
                      <dtml-if sequence-start>
                      <font color="Purple"><b>
                      <dtml-var name>
                      </b></font>
                      <P><dtml-var Main>
                      </dtml-if>
                      </dtml-in>
                      </UL>

Kamon:
> I tried to add a draft (in part VII).
> My file is in Structured text, and I set Content type =structured-text
> (also tried stx) instead of html and it does not display correctly.
> What I am doing wrong ?

stx should do.
DocumentFolderClass, Main:

<dtml-if  "'content' in objectIds(['DTML Method'])">
                         <dtml-if "content_type=='html'">
                           <dtml-var content>
                         <dtml-elif "content_type=='stx'">
                           <dtml-var content fmt=structured-text>
                         <dtml-elif "content_type=='txt'">
                           <dtml-var content html_quote newline_to_br>
                         </dtml-if>
                      </dtml-if>

If there is an error, then it should be found above.

I am off the air until tomorrow,

I wish you all the best,

Maik