vpdf ? vpdf!

@xenic
Do you know how can i setup and test via something simple (like notepad) , file.device ? I just trying to set it up in prefs:printer and then just do "print" from notepad with no luck. Trying and to clipboard and to file, and nothing .. (i need this to do tests and found what the problem with that "can't initialize output" ).

@kas1eQuote:

Not quite. OS4 postscript driver requires a postscript printer to be connected and it outputs PS data directly to the printer. It uses postscript install that comes with OS4 to convert the printer output to PS before sending it on to the postscript printer. The setting are set with the PrinterPS preferences.

TurboPrint installs it's own version of ghostscript, installs a gs-handler and assigns a PS: device. When you print to PS: I believe it runs the output through it's own version of ghostscript and converts it to be compatible with t he non postscript printer. You don't have to have TurboPrint running to use the PS: device. Just the device, ghostscript and the gs-handler have to be present. TurboPrint would installed it's own version of ghostscript because the OS4 version of ghostscript would not work with the handler, (maybe OS4 version was an older version or maybe TurboPrint people modified something. Not sure??). Anyway, I'm not sure if the current version of OS4 ghostscript will work with the PS: device and handler or not. I think it might because at one point I think I did update ghostscript to the latest OS4 version of ghostscript but I can't remember for sure now.

Quote:

Hmm...I'm not 100% sure without further investigation but it looks like that code requires turboprint to be started to print. When I tried to do the non-postscript printing I didn't have turboprint started. I'll have to try starting turboprint then try to print with the non-postscript setting. Maybe vpdf only supports turboprint printing and not standard OS4 printing. Can't check now as I'm at work.

Quote:
If it only supports printing via turboprint then setting the OS4 driver to file won't help you.

@ktadd
Quote:
Yep ! Check it plz.

Quote:
I am not about vpdf, just about anything to make tests :) Like from notepad for example.

@kas1e

Just checked the Turboprint developer information and verified the printer code you posted is indeed code that prints using Turboprint so it looks like you can either print via the PS: device or Turboprint. Turboprint will substitute it's own 24bit printer.device for the OS4 one. So, if I enable turboprint and disable postscript printing then it should print properly even though I use the usbprinter.device. We'll see.

It looks like you need the turboprint package to print from vpdf. I can verify this tonight after work.

The PS: printouts look great though.

@kas1e
Use the printtofile.device, not the file.device to print to a file. From the AmigaOSManual:

Quote:

Taken from here:
AmigaOSManual


Edit: fixed quote.

@ktadd
Thanks, will try. Through in prefs:printer there is also "File" printer, which kind of should work too (at least in pure Notepad), never tried that one ?

@kas1e
Just tried printing from vpdf with turboprint enabled. I did get a grim reaper but when I hit ignore it printed fine. I then went to Graphics Publisher, which came with turboprint, and printed via turboprint and it printed fine with no grim reaper. So, vpdf will print via turboprint but it produces a grim reaper which needs to be ingnored. I pirnted several times this way from vpdf and each time after ignoring the reaper it printed fine.

Here is the stack trace:

@kas1e
I was able to print to a file (not with vpdf) by using the printtofile.device, selecting the generic printer in OS4 preferences, then printing from notepad.
If you select a printer instead of generic then it save all the codes sent to the printer as well.

I didn't have any luck getting things to work by selecting "File" as my printer.

@ktadd

Ok so good new is that VPDF works or via PS: in postscript way or directly via turboprint. What mean all is ok, just need to deal with GR. Can you try please that binary (i add debug info there, so we can see stack trace):
http://kas1e.mikendezign.com/aos4/vpdf/debug/vpdf.zip

Quote:
At least it wasn't just me then :)

@kas1e there are my new icons ready to download
http://www.indiego.rocks/file/downloa ... 71aec3a25141358394c672960
here is my new german catalog ready for download
http://www.indiego.rocks/file/downloa ... 9acdb1ad2b07d0f1330a4f024

@kas1e there are some missing strings and broken strings, i can`t translate all

1.Go to button to for zooming in and out(default is 100%, 8,33%,12,5% etc)
I translated "Fit Page" and "Fit width" but there are still in english
2.rmb and choose "Settings"
Titlebar show me "VPDF - Settings"
String is missing
3.Settings/Layout: All strings are missing
4.Settings/Scale: All strings are missing
5. For "Tree" and Thumbnails" are no strings too

Is it possible to add AISS buttons into VPDF and menu?
At moment it looks like buttons are from MorphOS

@tommy
I change nothing in terms of strings/catalog/etc, probably that is how it now. If you can't deal with it, i can skip german catalog from release. Or can use that one which you upload already.

Quote:

Buttons are converted to hex and hardcoded to the code. So, it is possible to replace them, but better don't loose time on that unnecessary and unimportant stuff. As for aiss buttons into menus : maybe it will be easy, just it then will looks strange: menu with aiss, iconf in programm from mos -> there will be need to make all in aiss -> boring crap, not now, maybe someday )


@jabirulo
If you ready with catalog , upload it plz, as i am about to make os4depot upload.

@kas1e
ok i understand, please take my german catalog and add it to VPDF

@kas1e

Sent via email spanish translation.

@all
new version:

-- Thore fix in MUI "close tab" issue. So you should update mui to latest nightly. As a side effect of this, i add check on the MUI version user installed, and if it not decent enough, spawn a warning about needs to update. Sorry, but that the only way we can be sure that no double-bugreports will be done.

-- when we load pdf which support content listing, Three was empty (thanks Kevin for detailed report). That was because of some codepages conversions done differently on morphos. So to support it on os4 we had to use codesets.library (which is now will be part of archive in libs:, and will be taken from that place). Thanks to Thore and Daniel for help

-- fixed title name problems (in some situations it was blank).

-- fixed "search" in pdf, which use morphos's ToUCS4(), which i had to rewrite like it was in Odyssey. Through search functionality have some bug: when you do search for something via "next" and then back "prev" and reach begining, it stop working correctly. Probably can be my own bug, or (but probably not) original bug, which i may try to fix later (if someone have morphos machine by hands, and can check if it indeed the case on morphos too, that will be interesting to know).

-- catalogs: added deutsch (by tommysammy), italian (by samo79) and spanish (by jabirulo)

-- icons from tommysammy

-- as VPDF support printing via TurboPrint (as it seems default mos's printing system?), changed to call turboprint's prefs instead as wellas add some string to the "can't initialize output device" warning window about needs to install TurboPrint. Probably later whole printing stuff should be rewriten to be more os4 friendly. Thanks to Kevin for idea.

-- removed unused and unnecessary directories/files from distrib, as it was there for tests only.

-- fixed some stuff related to constructors/destructors and initialisation of semaphores in : which may (or may not) lead to better stability

-- Daniel rewrite one function which should lead to be able to use copy from pdf to clipboard with saving of "non usuall" characters, like those in german, espaniol and co languages, but plz test it, probably need a bit of more work.

There is:
http://kas1e.mikendezign.com/aos4/vpdf/vpdf_beta_04.lha

@kas1e

Works nicely so far, just it seems i can't be able to open PDF files saved directly from Odyssey, i mean i trying exporting an HTML as PDF but when i try to open it in VPDF i got this error:

Quote:

Then the system will slowing down leading to freeze at some point ..

By the way general GUI might be redesigned a bit, still a bit unlogical in some way and later i might have some suggestions ..

@samo79
Quote:

As usuall lately you probably again have no time, and do tests too fast :) Are you sure that you install it in _fresh_ directory ? Are you sure you didn't use old vpdf.df.fontconfig, while should be generated new , as name of binary now pure vpdf ? Are you sure you delete previous one fully, and install one from scratch in new directory ?

I just tried right now : i run odyssey, go to amigans.net, save it as PDF, and open that PDF in VPDF (press open image in new tab to have it in full size):



But, just in case, upload your PDF which broken, i will check. And, step by step guide how to reproduce. Because as you see i can't reproduce it easy with just way you desribe it.

Quote:

Don't loose your time with it, GUI will stay as it original, as i want to keep it the same as original and for easy porting purposes later, and because moking gui hardly done by original developer kind of bad.

Its better to write new GUI from scratch then (not me).

@samo79

no problems here using beta04 and Odyssey PDFs. SAM460ex
...
Ooops while scrolling Odyssey PDF I got 'Fontconfig error: Cannot load default config file' error.


@kas1e
Try to scroll up/down the Odyssey PDF you get/save and see if you get such error.

@jabirulo
Tried - no error :( Did you install beta4 in new, separate directory without just overwriting binaries with holding old fontcashe file ?

Also how you scroll it, via dragging over scroll bar ?
Can you upload that PDF so i can test ?

@kas1e

Installed beta04 on RAM so no other VPDF installation.
Scrolling using the slider on the right.

http://jabirulo.site90.com/temp/viewtopic.php.pdf

Is the PDF I get when saving this same topic as PDF using Odyssey.

@jabirulo
Yep, can reproduce with your one, thanks. invistigating

edit: strange, i even can't get by snoopy anything which show that there is tries to open any config file from anywhere. Just nothing..