RE: auto-preview?

I'd like to move this discussion to the devel list, so I've
included
both lists on this message.

I was also concerned about the response time to the end-user
in cases
where previewing takes a long time.  For that reason, I was
thinking of
doing the dirty-work asynchronously by fork()'ing prior to
the preview
call.

Also, I was already going to add an asset save() hook to
Asset.pm to
allow some bricolage.conf defined code to execute when an
asset is
saved.  The asynchronous call to preview could be tied into
save() that
way.

I'll do some experimenting and post a couple of patches if
I'm able to
get something working.


-----Original Message-----
From: slanninglocalhost.localdomain
[mailto:slanninglocalhost.localdomain] On Behalf Of Scott
Lanning
Sent: Monday, March 05, 2007 9:00 AM
To: userslists.bricolage.cc
Subject: Re: auto-preview?

You can use `bric_soap workflow --to-preview .... publish`
to do bulk previewing,
but there's no functionality in Bricolage that previews when
you save.
(Here at least, that would be hideously slow.)

On Mon, 5 Mar 2007, Matt Rolf wrote:
> The same question has come up in our shop.  In our
situation, we are 
> previewing on a separate server, and for our
programmers doing app 
> development, making that preview is one extra step they
wish to avoid.
>
>> 
>> What's the best way to force a behind-the-scenes
preview of a story
when 
>> changes to a story are saved?
>> 
>> The problem I'm experiencing is that even though my
templates are
blazing 
>> the other dependent stories at preview-time, if a
user saves changes,
but 
>> never previews a story, the files on the preview
server aren't
updated and 
>> if the user happens to navigate to those stories
via another path,
the 
>> content is "stale"...
>> 
>> This isn't a problem with "publish"
because users must actively
publish 
>> stories whereas previewing is optional right?
>> 
>> If you think I'm worrying needlessly and that this
is best handled
through 
>> user training, please let me know as well.

On Mar 5, 2007, at 07:16, Beaudet, David P. wrote:

> I was also concerned about the response time to the
end-user in cases
> where previewing takes a long time.  For that reason, I
was  
> thinking of
> doing the dirty-work asynchronously by fork()'ing prior
to the preview
> call.

That's generally a no-no in a mod_perl environment.

> Also, I was already going to add an asset save() hook
to Asset.pm to
> allow some bricolage.conf defined code to execute when
an asset is
> saved.  The asynchronous call to preview could be tied
into save()  
> that
> way.
>
> I'll do some experimenting and post a couple of patches
if I'm able to
> get something working.

I look forward to it.

Best,

David