ADV: Browser-based development for filePro

[Fairlight]

Simon--er, no...it was Bob Rasmussen--said:
> Most web-front-end environments will run into the challenge of printing. 
> Web browsers are seldom a good option for doing the printing. They're 
> unpredictable and to a degree uncontrollable. They're the wrong tool for 
> the job.
> 
> That is why we designed Web Print Object (WePO). This is an ActiveX (OCX) 
> version of Print Wizard that can be embedded in a web page. When the user 
> clisks the button that says "Print", the object fetches a specified file 
> (typically from an HTTP source), and prints it, renders it to PDF, adds an 
> overlay, etc. See website for details.

I did find out something neat (with Bob's help) a few years back.  I have a
client that at one point was basically emulating clerk, having a page where
you just add records, and iterate the fill-in form after submission.  So
you'd need the page for the browser as the response.  

There was, at some point, a desire to print a receipt or some other form
every time a record was added.

I had figured out a way to actually send BOTH the web page response to
the browser -and- the document to WePO in the same response, so you could
do both things without issue--and without using frames or new windows or
anything.  It was really neat.  Unfortunately, I don't remember the exact
configuration necessary, as all my notes and the proof of concept for
that particular research were kept on my client's machine, and they later
accidentally wiped them out during a cleanup. *dry cough*

But it -is- possible, and quite neat to see in action.

WePO is pretty cool.  My only real complaint with it is that it requires
IE, since it's an ActiveX control.  Which means forget about it on a Mac or
Linux.  It's still usable with Firefox if you have IETab installed and use
the relevant site under an IETab.

If one is -always- going to PDF though, Bob...what is the advantage of WePO
over just using a local server-side PrintWizard and sending back a PDF?
Besides not being able to do the simultaneous response that I detailed
above, what would be the advantages?  I'm drawing a blank, so it might be
good to outline the differences/advantages between them?

Both are good products, though.

mark->
-- 
"I'm not subtle. I'm not pretty, and I'll piss off a lot of people along
the way. But I'll get the job done" --Captain Matthew Gideon, "Crusade"