Full Version: Lytrod Software is willing to help with VIPP
We, at Lytrod Software, are willing to help answer your questions about VIPP. We develop a suite of GUI software products that generate VIPP code (Job, Project, Container) and support Dynamic Document Construction. Proform Designer is our enterprise wide solution. Our programmers have in-depth knowledge of VIPP and are willing to share that knowledge in order to promote Xerox' VIPP technology.
Cool, welcome... Looking forward to learning more about Lytrod. I haven't touched Lytrod in about 4 years so I am sure things have changed dramatically.
Thanks for the welcome. Send any questions our way. When you have a moment take a look at the link to our applications page on our website: http://www.lytrod.com/support/applications2005.html
You will find a wide range of VIPP applications built in Lytrod Software. I look forward to answering any questions you may have.
You will find a wide range of VIPP applications built in Lytrod Software. I look forward to answering any questions you may have.
Hello,
I am a programmer interested in writing some simple internal applications to view VIPP files. I am familiar with the VIPP language, but I have not found any sort of API to interface with the VIPP parser or any other tools. Does a VIPP API exist, or possibly the source of the language (I have read that VIPP is an open language).
Thanks!
I am a programmer interested in writing some simple internal applications to view VIPP files. I am familiar with the VIPP language, but I have not found any sort of API to interface with the VIPP parser or any other tools. Does a VIPP API exist, or possibly the source of the language (I have read that VIPP is an open language).
Thanks!
Hmm,
VIPP as an open language, that's an interesting one. I guess its open once you license it from Xerox. THere is the IDE from Xerox for VIPP but it is far from an API.
VIPP is an extension to postscript, so I suggest you look for a postscript interpreter that you can interface with, Adobe distiller can work for that, then the VIPP language is called from the postscript interpreter via a startup command.
As far as I know, there is no API for a postscript interpreter, mainly because of the differences between how postscript executes code to generate printer data, vs a traditional coding language which compiles and executable.
VIPP is very well documented by Xerox in the licensed package as to what all the commands do and how they are used in the different modes.
I suggest you contact Xerox directly if you want more details about VIPP which has now been renamed to be branded as part of the Freeflow solution. They have a group in Lewisville, TX that specializes in VIPP.
VIPP as an open language, that's an interesting one. I guess its open once you license it from Xerox. THere is the IDE from Xerox for VIPP but it is far from an API.
VIPP is an extension to postscript, so I suggest you look for a postscript interpreter that you can interface with, Adobe distiller can work for that, then the VIPP language is called from the postscript interpreter via a startup command.
As far as I know, there is no API for a postscript interpreter, mainly because of the differences between how postscript executes code to generate printer data, vs a traditional coding language which compiles and executable.
VIPP is very well documented by Xerox in the licensed package as to what all the commands do and how they are used in the different modes.
I suggest you contact Xerox directly if you want more details about VIPP which has now been renamed to be branded as part of the Freeflow solution. They have a group in Lewisville, TX that specializes in VIPP.
Well Patrick, you may be right 
As far as VIPP being an "open" language, they do document how to use it very well. My company uses VIPP frequently and I have learned how to write code for it solely through the use of the manuals and samples provided by Xerox.
What seems to be missing is an sort of documentation on how VIPP works in the background, parsing files, caching data, and sending data to VIPP enabled printers. Although the actual language seems to be "open" (you could look up any vipp command you want at www.vippcomands.com), there doesn't seem to be any available documentation for programmers who wish to work with the VIPP language at a lower level, such as writing applications to parse, view, and create documents. I guess for the large majority of people who work with VIPP, this type of documentation is not important, but hopefully for a select few the information I am looking will be helpful.
The reason I posted this question here is actually because I must assume that Lytrod has some of this information, since they would need it to create their applications! Hopefully Tish from Lytrod Software will have some information, or my Xerox rep will eventually get back to me with the information I am looking for. Assuming I'm not contained to keep the information a secret, I would love to post it here so others can inspect how VIPP works in the background.
As far as VIPP being an "open" language, they do document how to use it very well. My company uses VIPP frequently and I have learned how to write code for it solely through the use of the manuals and samples provided by Xerox.
What seems to be missing is an sort of documentation on how VIPP works in the background, parsing files, caching data, and sending data to VIPP enabled printers. Although the actual language seems to be "open" (you could look up any vipp command you want at www.vippcomands.com), there doesn't seem to be any available documentation for programmers who wish to work with the VIPP language at a lower level, such as writing applications to parse, view, and create documents. I guess for the large majority of people who work with VIPP, this type of documentation is not important, but hopefully for a select few the information I am looking will be helpful.
The reason I posted this question here is actually because I must assume that Lytrod has some of this information, since they would need it to create their applications! Hopefully Tish from Lytrod Software will have some information, or my Xerox rep will eventually get back to me with the information I am looking for. Assuming I'm not contained to keep the information a secret, I would love to post it here so others can inspect how VIPP works in the background.
Yeah, I guess it all depends on what you define as open. I can't think of a language in which the owner/creator of the language doesn't share the words or commands of the language. But then again, open means different things. Open to me means I have the ability to run it on any printer or non-printer not just Xerox Branded solutions.
Also, since VIPP is simply dependent on Adobe Postscript, you might want to look for Adobe postscript API / Development tools. VIPP is simply an extention to postscript, it isn't doing anything inherently different then what postscript is doing. The tools that come with VIPP such as IDE and the job submission tools could be interacted with if Xerox felt like opening those, but then again, that's what they do is provide those solutions for a fee vs allowing others to write the solutions themselves.
I am assuming Lytrod is simply using the code structure to output VIPP commands and submit to the printer, They aren't interfacing with the printer in any different way that I know of then just simply using a text editor on the printer. They do have a great gui around the commands as well as a good interface to the backend database, but fundamentally they are a compostion engine that output vipp commands, not compiles vipp to be printed.
I could be wrong, but I would suggest going the route of the Adobe Postscript SDK or work with the DFE/RIP vendors, including Xerox to see if they have SDK's for their DFE's to interface with. VIPP is simply a plugin to postscript. Hard to simplify it to that level, but that is what it is.
Also, since VIPP is simply dependent on Adobe Postscript, you might want to look for Adobe postscript API / Development tools. VIPP is simply an extention to postscript, it isn't doing anything inherently different then what postscript is doing. The tools that come with VIPP such as IDE and the job submission tools could be interacted with if Xerox felt like opening those, but then again, that's what they do is provide those solutions for a fee vs allowing others to write the solutions themselves.
I am assuming Lytrod is simply using the code structure to output VIPP commands and submit to the printer, They aren't interfacing with the printer in any different way that I know of then just simply using a text editor on the printer. They do have a great gui around the commands as well as a good interface to the backend database, but fundamentally they are a compostion engine that output vipp commands, not compiles vipp to be printed.
I could be wrong, but I would suggest going the route of the Adobe Postscript SDK or work with the DFE/RIP vendors, including Xerox to see if they have SDK's for their DFE's to interface with. VIPP is simply a plugin to postscript. Hard to simplify it to that level, but that is what it is.
I too would hesitate to call VIPP an open language.
Regarding an API, VIPP is a programming language and devices are interpretors. I don't understand how an API would fit in.
What are you trying to accomplish? For development all you need is a text editor and an interpretor (usually a VIPP enabled rip).
There is an IDE available from Xerox that is pretty good for hand coding true VIPP. Additionally many applications including Lytrod and others are able to through their IDE generate VIPP code from there design interface. From what I have seen, even those tools do not operate as a VIPP interpretter. This could be conclusively tested by opening a VIPP applications through the application and attempting to make code changes.
Regarding an API, VIPP is a programming language and devices are interpretors. I don't understand how an API would fit in.
What are you trying to accomplish? For development all you need is a text editor and an interpretor (usually a VIPP enabled rip).
There is an IDE available from Xerox that is pretty good for hand coding true VIPP. Additionally many applications including Lytrod and others are able to through their IDE generate VIPP code from there design interface. From what I have seen, even those tools do not operate as a VIPP interpretter. This could be conclusively tested by opening a VIPP applications through the application and attempting to make code changes.
I would call VIPP an open language. First, it runs on any PostScript printer. Second, what comes into VIPP is planin ASCII or EBCDIC text - cannot get much less propriatary than that.
As far as an API goes, I think you are asking the wrong question. If you are looking for tools to generate print streatms that take advantage of all things VIPP, then there are pleanty of those around. If you are looking for more indepth knowledge of VIPP, Xerox sells a development Kit and has experts you can engage.
As far as an API goes, I think you are asking the wrong question. If you are looking for tools to generate print streatms that take advantage of all things VIPP, then there are pleanty of those around. If you are looking for more indepth knowledge of VIPP, Xerox sells a development Kit and has experts you can engage.
Sure, VIPP can run on any postscript printer...
How do you get your hands on the interpretor to load it on a cannon, nexpress, etc.
The idea is good and the sales pitch from Xerox is that it is open, but is it really?
Don't get me wrong, I like Xerox and love VIPP, but open, I am not sure.
How do you get your hands on the interpretor to load it on a cannon, nexpress, etc.
The idea is good and the sales pitch from Xerox is that it is open, but is it really?
Don't get me wrong, I like Xerox and love VIPP, but open, I am not sure.
I'm pretty sure we should take the Is VIPP an Open Language topic to the VIPP forum and start that debate there
QUOTE (TLevin10 @ Feb 2 2006, 02:58 PM) 
Well Patrick, you may be right
As far as VIPP being an "open" language, they do document how to use it very well. My company uses VIPP frequently and I have learned how to write code for it solely through the use of the manuals and samples provided by Xerox.
What seems to be missing is an sort of documentation on how VIPP works in the background, parsing files, caching data, and sending data to VIPP enabled printers. Although the actual language seems to be "open" (you could look up any vipp command you want at www.vippcomands.com), there doesn't seem to be any available documentation for programmers who wish to work with the VIPP language at a lower level, such as writing applications to parse, view, and create documents. I guess for the large majority of people who work with VIPP, this type of documentation is not important, but hopefully for a select few the information I am looking will be helpful.
The reason I posted this question here is actually because I must assume that Lytrod has some of this information, since they would need it to create their applications! Hopefully Tish from Lytrod Software will have some information, or my Xerox rep will eventually get back to me with the information I am looking for. Assuming I'm not contained to keep the information a secret, I would love to post it here so others can inspect how VIPP works in the background.
As far as VIPP being an "open" language, they do document how to use it very well. My company uses VIPP frequently and I have learned how to write code for it solely through the use of the manuals and samples provided by Xerox.
What seems to be missing is an sort of documentation on how VIPP works in the background, parsing files, caching data, and sending data to VIPP enabled printers. Although the actual language seems to be "open" (you could look up any vipp command you want at www.vippcomands.com), there doesn't seem to be any available documentation for programmers who wish to work with the VIPP language at a lower level, such as writing applications to parse, view, and create documents. I guess for the large majority of people who work with VIPP, this type of documentation is not important, but hopefully for a select few the information I am looking will be helpful.
The reason I posted this question here is actually because I must assume that Lytrod has some of this information, since they would need it to create their applications! Hopefully Tish from Lytrod Software will have some information, or my Xerox rep will eventually get back to me with the information I am looking for. Assuming I'm not contained to keep the information a secret, I would love to post it here so others can inspect how VIPP works in the background.
VIPP is not a language or even semi language!
It is a group of postscript procedures and dictionaries which simplified the Postscript language!
While adobe invested huge effort and innovative effort to develop the language they produce little documentation and training courses! The red Book - which is free now - is difficult for ordinary users to penetrate and benefits from the language!
That's why you might need great effort to learn merging forms and logo to PS Job!
Xerox facilitates that by building Postscript procedures used by single work and with one or many parameters to do the required function!
Bugt negative points as well ; VIPP tunred some of the simple PS commands into complicated procedure and some are simply replicated without any value! ONLY TO GIVE THE TOUCH OF AN INDEPENDECE AND FORCE THE USER TO USE ONLY VIPP !
Sure they will not release the internal structure of mechanism of VIPP!! It would be easy to break up the VIPP and use those procedures as you like!
Just because the spreading of Xerox engines in; production market VIPP still getting bigger and many vendors try to use those Xerox procedures/dictionaries instead of writing in PS directly.
Regards
Adam
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.