After some time of developement i am glad to anounce that ppdf is getting to be a usable application.
The ppdf project is an effort to replace puppypdf with a gtkdialog based new program.

I would like to ask everyone who has some time to test it, and comment on it.,
The program was developed on 4.25 and depends on abiword and ps2pdf (ghostscript).

Big thanks to vovchik and seaside and everyoone on the GTKdialog topic for their help.

CHAGELOG:

=0.1.7==========
- gxmessage replaced with yaf-splash (puppy programs tend to use it)
- the "Converting..." splash is displayed full time durning conversion and closes when conversion is done.
- Handling filenames with spaces fixed
- the program now shows message if it can not create the gtkdialog symlink
- the program now closes after conversion if called from the helper script

I do not experience the abiword launch problem after program close when I run ppdf. However, if I use ppdf-helper, it happens every time - after clicking the close button and after a success pdf print. Strange...

I do not experience the abiword launch problem after program close when I run ppdf. However, if I use ppdf-helper, it happens every time - after clicking the close button and after a success pdf print. Strange...

Version 1.6.1 works just fine, so thanks again. I still think it would be a good idea to check for file types before the conversion to ensure that the files are actually printable. Also, when I right-click in Rox on a doc file that has spaces in the filename (usually sent by M$ users), ppdf does not complain but does NOT print the pdf. I think a check is needed for a filename with spaces (e.g. surrounding the var with quotes - "$xxx") or a routine to rename the offending original file temporarily just for the conversion process and then renaming it back to the original M$ name. Just an idea....

Everything seems to work, so thanks. I notice you replaced gxmessage with yaf-splash. yaf-splash is notoriously ugly and looks out of place with gtk. If you don't like gxmessage, I would suggest the attached workaround for yaf-splash done by forum member Mark Ullrich (MU). SImply rename yaf-spash to yaf-splash-org and place this in the same dir as yaf-splash. make a symplink called yaf-splash that points to yaf-mu. MU's brilliant contribution is only 317 bytes!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum