Let me try to compile it in Puppy 4.10 or in Lucid and see what happens. HUG has changed a bit (some calling conventions), as has Bacon, so I think I should use the old HUG (last one that worked), since it did what I expected it to do. I'll experiment. Lucid has bash v. 4.1.5, and bacon compiled fine with that a few days ago, although I didn't experiment with HUG in that setting. Try grabbing the latest bacon.bash and bacon.bac from Peter's site and compile it. Then try compiling Pikona using the bacon binary, once with a new HUG and once with the old. I wonder whether the saving doesn't have something to do with write permissions in the place that Pikona might be installed. Just and idea.

With kind regards,
vovchik

UPDATE: I compiled pikona in Lucid and it saves. I had to use the old hug because the IMAGE command syntax changed and I haven't yet changed my source. But with the old hug it saves to the icn dir. What is important is that you use your IM, because the one in Lucid seems to screw up the alpha channel (renders it black). I suppose that could be fixed by also looking at changes in IM convert syntax.

Try grabbing the latest bacon.bash and bacon.bac from Peter's site and compile it. Then try compiling Pikona using the bacon binary, once with a new HUG and once with the old. I wonder whether the saving doesn't have something to do with write permissions in the place that Pikona might be installed. Just and idea.

well I figured out how to compile the bacon (that sounds funny)
then the pikona with HUG

so I 'll try again compiling this on a clean system
puppy pfix=ram
bbl
Joe_________________debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though

I have thought of several things in order to remove the IM dependencies. MU once posted three little utilities he wrote in c (each of which is about 4k compiled) that would do the job, except that one of them - scale2png - screws up when it comes to the alpha channel at high bit depth. The code is tiny, so I should look at it and try to do a rewrite in BaCon or use the modded c code directly (BaCon allows for that as a USEC). I would just have to get the IMPORT stuff straightened out, since these CLI progs make use of GTK (mainly gdk_pixbuf). I have already written a tiny bit of test code that is CLI but uses the GTK libs, so I think I can manage. What I would really like is totally self-contained code - apart from shared libs that are available on each and every Puppy (X11, GDK, GTK). I will look at netpbm, too. Ideally, the graphic transformations should all take place within Pikona (in RAM). It would make the program much faster and prevent dependency hell.

I have attached Mark's source for the utilities that could, with a bit of reworking, replace IM. They were part of his Scale2pics package and have nice potential.

Hey vovchik
thanks for posting the source .There is one more needed scale2png.c

that wasnt in the source there was only the bin .Here it is the "make" is the same

I'll post it here
Joe

Quote:

MU once posted three little utilities he wrote in c (each of which is about 4k compiled) that would do the job, except that one of them - scale2png - screws up when it comes to the alpha channel at high bit depth.

With the kind assistance of Peter (www.basic-converter.org), I got a first"draft" of picscale working in BaCon. If anybody has suggestions on how to improve the quality of the jpg conversion, please let me know. A binary and source are in the archive.

With kind regards,

PS. I think I am moving towards an ImageMagick-free Pikona. All I now need to do is to figure out how to use gdk_pixbuf to overlay images. Dammit, it looks like I will, at long last, have to consult the documentation.

UPDATE: I updated the archive since I fixed the bad jpg rendering and cleaned up the code a little bit.

UPDATE2: In fixing the jpeg quality stuff, I managed to destroy png transparency. It is now fixed and the archive has been updated. Sorry about that.

Thanks for the nice words. I have ported a few c examples and they are on Peter's site. I also have my original c sources so I can post them here. I will try to annotate my code (IMPORTS mainly), but I got those from studying the gtk/gdk/glade calls, looking at Peter's nearly complete gtk.bac and gdk.bac and glade.bac files and, in a few cases, winging it after looking at the var types needed by the calls. It becomes easier after a few "iterations" and you get a feel for it after few successes. I have an entire directory of c gtk gui samples and forced myself to translate a number of them to BaCon. It was a good exercise and, when I got stuck, I asked Peter, who knows all there is to know about BaCon and GTK (he also wrote GTK-server). If you get stuck, just holler Mechanic (Doyle) is doing a lot of gtk stuff in baCon and can provide some guidance.