Have you seen the video?
Bob Rasmussen
Richard Kreiss
It was informative but you could have explained the whole process.
1. How to combine the 2 files
2. How to open them in the editor
3. Then how to handle the overlay (current movie)
The one thing many of us do with our own software is assume that the person
we are speaking to knows much of what we know. When I write a manual or
help files for my software, I often have my wife read it over. She is not a
computer person and if she understands it, I am sure my users will.
Manuel Sotil
jed
all the neat thing PW can do. So please produce more videos that are
more detailed from start to finish of the process.
How do you save the changes you made to the PCL form and the data
stream so they will line up from now on?
How do you use a PDF file as a overlay form.
How do you use page repeating and job repeating, in order to get the
equivalent of multi-part forms.
I'm going to use PW on a Win Server to handle all the overlay forms
from a application running on Linux. I would like to be able to send
to printer as well as email a PDF output. Any video related to this
would be great.
Bob Rasmussen
testers were familiar with Print Wizard, when in many cases they are
not; and b) the video is an effective method of presentation of
information. Good info, thanks! I'll be producing more videos.
In the meantime, remember that not all of Print Wizard is new, and not
all of the information is in this group site. Be sure to browse the
website (www.anzio.com), read (or at least skip) the manual, and check
out the example files, accessible from the Help menu of PWUI.
>
> - Show quoted text -
Tony Gravagno
enhancements. I will follow-on to Bob's comment though.
Bob, there are at least two kinds of betas:
1) Beta of a new version for those already well versed in the
nuances of the previous versions. These people can provide
valuable feedback on how the product is better or worse and what
new bugs or complications have been introduced.
2) A Beta with people who have never seen the software is
extremely valuable to let you know where you have succeeded or
failed in making a new release easier to initially understand
than prior versions.
Simultaneous betas from both groups are helpful. You don't want
to shift focus away from one group to the other, you really need
to keep focus on both groups just like you're running two betas
for two different products.
The PW manual is quite good in that it includes all options and
serves as a great reference. If you spend time with the manual
you will get a better understanding of this fine product. Like
all reference manuals however, it tends to provide a reference
_back_ for people who are familiar with the product and they're
looking for details. The PW manual helps at this "tier 2" when
you have a grasp of the product and now you're hungering for
those details that make the product great. But it is not quite a
tutorial to get you through that "tier 1" phase where you don't
quite "get it".
I found that spending several hours with the product helped to
get over the initial hump. Though even after playing with it on
my own and having a number of exchanges with the fine people at
Rasmussen Software, I still find myself always on the verge of
not quite being on top of how it all comes together. More
tutorial docs and videos should help to flatten out that initial
curve.
Specifically, PrintWizard allows you "wire up" print jobs to flow
through various bits of software and profiles. It can be
difficult to work out how to do this wireup to achieve desired
results. Along the way, the document itself can contain markup
that affects how it will be processed. This can be in the form
of PWML or !Bang commands. I have a complete grasp on PWML
because it's just like HTML, but proper usage of !Bang commands
sometimes still eludes me. I think the problem is knowing when
to use !foo and when to setup a profile.
So for newbs using PW, it does take a while to get it but the
investment is quite rewarding. For Bob and others who are trying
to explain how the software works, I think it would be helpful to
have a bunch of mini case studies which present a business
problem and then explain how PW is used to solve the problem.
HTH
See my blog on PW here:
nospamNebula-RnD.com/blog/tech/2008/03/pwtips01.html
and info on PW for Pick/MultiValue users here:
nospamNebula-RnD.com/products/printwizard.htm
Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
Nebula R&D sells mv.NET and other Pick/MultiValue products
worldwide, and provides related development services
remove.pleaseNebula-RnD.com/blog
Visit PickWiki.com! Contribute!
http://Twitter.com/TonyGravagno
> From: Bob Rasmussen
> I can see from these comments that a) I have been assuming beta
> testers were familiar with Print Wizard, when in many cases
they are
> not; and b) the video is an effective method of presentation of
> information. Good info, thanks! I'll be producing more videos.
>
> In the meantime, remember that not all of Print Wizard is new,
and not
> all of the information is in this group site. Be sure to browse
the
> website (www.anzio.com), read (or at least skip) the manual,
and check
> out the example files, accessible from the Help menu of PWUI.
>
jed
preview window here is how I did it. I created a batch file with the /
preview flag as such:
"c:\program files\printwiz4\printwiz.exe" text.txt /profile="C:
\Documents and Settings\jed\Application Data\Print Wizard
4\bol.profile" /preview
The text.txt is my data file. The bol.profile is a profile that has
the "Overlay file to use" under the Print Wizard tab pointing to a PCL
file I created in Adobe InDesign.
The problem that I'm having now is when the file/overlay is printed
all the lines are omitted.