Re: [Hypercontent-users] More functionality - will be help for all

[tom t. <j_l...@ya...>]

Hi Alex,

I think I could cover almost everything of the user
requests, but am waiting on the answers for other
emails which I sent to you,

Only thing which I couldnt address was text compare
tool, that is something we can live with for the time
being.


Any how see my observersations and comments.


> One can make edits and either not save them (which
> leaves them in a  
> persistent "draft" state), or save them and schedule
> the change of  
> edition.  So it is still possible to do edits for a
> future publishing  
> cycle.

If I can remember, you did state in one email that if
we dont save or discard, it might lead to locking
issues, Due to this reason I decided to make use of
the sceduling feature for this, Other posibility is
they can make use of the make current option to get
around with this.


 
> The scheduling script is only for one source file. 
> It schedules the  
> change of the "edition pointer" that governs which
> version of a file  
> is live.  To have it republish immediately after
> updating the  
> pointer, in schedule.xml you could add at line 23
> after the  
> SetCurrentEdition command
> 
> <render path="${path}" destination="/publish/"
> force="false"  
> delete="true"/>
> 
> The schedule script  has two times - a begin and end
> time.  You might  
> want to create a variant on the script to schedule
> just a single  
> change of edition and immediately republish,
> something like this

We got a staging area, hence we dont need a immediate
republish, it is enough that the scheduler change the
edition and we got a master sceduler(discussed later)
that will do a automatic build and publish. So at that
time this edition also will be looked after. Let me
know if this is not the best way to do?
 

> > What if I want all the content content to be
> > pulished/build on each monday. Can the publisher
> > define such a thing using the interfaces?
> 
> You could define a workflow script to do this as
> well (5am every  
> Monday):
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE workflow SYSTEM
> "http://hypercontent.sourceforge.net/dtd/ 
> workflow.dtd">
> <workflow binding="/**/*.*">
> 	<event name="schedule-publish" when="@0 5 2">
> 		<render path="/" destination="/publish/"
> force="false" delete="true"/>
> 	</event>
> </workflow>


Why we need to define another workflow, why cant we do
in the same publish.xml as follows as an event? Is
anything wrong in doing like this?

<event name="schedule-publish" when="@0 5 2">
<copy delete="true" destination="/publish/"
force="false" path="/" source="/build/"/>
</event


thanks,



       
____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/