From: "David A. Desrosiers" <[EMAIL PROTECTED]> > I think you mean JPluck. jPlucker is a slightly different >project, based loosely on the same codebase as JPluck itself.
See - I'm such a newbie at this I don't even know the name! The directory created appears to be jpluck-2.1.6b . > however, when I go to the jplucker web page, I start off with a > strike against me. I don't seem to be able to locate any info on > installing or using it. Given my novice state, I am left perplexed. > Which site are you using? > > http://jpluck.sf.net/ <- this is probably right This one is the one I was trying to use. I finally did notice a "readme.txt" file in the jpluck directory that tells me a little bit. It doesn't, however, talk about what JPluck X vs JPluck C is, and it mentions something called JPluck Palm Buddy as if it were in the distribution, but doesn't seem to be. It mentions the above site's doc directory - but what appears feels, to this poor old set of eyes, like it is written to help someone familar with the tool get on with the task of doing things. Perhaps someone out there has written their own 'Welcome to JPluck!' type doc for a class or something? > No, you have several options: > > 1.) Plucker's standard Python distiller (shipped with Plucker) Hmm - this is where I was trying to start. However, the problem is that I can't quite figure out what I am doing here. The weird thing is that in older versions of plucker, I seemed to have enough pieces to get things installed. However, in the latest release that I've downloaded, I can't find info on how to go about installing the code that's in the tar file. That's when I decided to start looking around - the plucker I had installed isn't working and I can't seem to figure out how to install the new version. > 5.) SiteScooper And I have sitescooper - but it is trying to call plucker-build, which isn't working, so I'm trying to fix things back up... > > Just curious? > The existing will be rewritten where necessary, other pieces > will be thrown away, the project will be renamed, and it will be > relicensed under a license that allows others to continue to develop > against it without the fear of someone taking the code and turning it > proprietary again, orphaning off the existing userbase. > > Does that help? Well, that certainly helps me out with the future of plucking. Thanks so much for taking the time to explain! -- Tcl - The glue of a new generation. <URL: http://wiki.tcl.tk/ > Larry W. Virden <mailto:[EMAIL PROTECTED]> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
